Healthcare Calculation & Data-Entry Workflow
Context
A healthcare product relied on a dense calculation and data-entry workflow that needed to become easier to complete across responsive web layouts.
Challenge
The interface had to reduce the effort of entering and reviewing information without weakening clarity, accuracy, accessibility, or the underlying business logic.
My Role & Responsibility
I worked across product UX, responsive interaction design, React implementation collaboration, accessibility, and design QA.
The Flow I Had to Understand
The experience required users to move through a calculation and data-entry process, understand the information being requested, complete the required inputs, and review the result with less friction.
Calculation & data-entry journey
Key Decisions
Decision 01 — Break the task into understandable stages
Organise the workflow so users could focus on the information needed at each stage instead of processing the entire calculation experience as one dense block.
Decision 02 — Keep feedback close to the input
Make validation and calculation feedback understandable in the context of the action being completed rather than forcing users to interpret disconnected messages.
Decision 03 — Design responsive behaviour as part of the workflow
Treat smaller layouts as a change in available space and attention—not simply as a scaled-down desktop screen.
Why Those Decisions Mattered
Data-entry friction compounds when users must repeatedly re-orient themselves. Clear grouping, contextual feedback, and responsive behaviour reduced unnecessary cognitive effort while preserving the task itself.
The Improved Experience
The redesigned workflow made the calculation and data-entry process clearer, more responsive, and easier to complete while remaining aligned with implementation constraints.
Constraints & Trade-offs
Balancing dense clinical calculation accuracy with rapid keyboard-first entry across varied screen resolutions.
Collaboration & Implementation
I collaborated directly with engineering on React implementation feasibility, accessible keyboard behaviour, and responsive layout testing.
Outcome
The resulting experience reduced data-entry time by approximately 40%.
Reflection
“The project showed how much time can be recovered when a complex form is treated as a sequence of decisions rather than a collection of fields.”
Confidentiality Note
* This case study has been anonymized to respect client confidentiality. The company identity and original product screenshots are not shown. Flow diagrams are used to explain the actual problem, design decisions, and outcomes. Additional context can be discussed privately during an interview.