A coherent review experience that protects attention for clinical judgment.
An anonymized experience narrative. Demonstrations use reconstructed flows and invented inputs; internal metrics and artifacts are excluded.
01 / THE STORY
A use case worth solving.
RECONSTRUCTED SCENARIO
A pharmacist opens a review task. The information needed to understand it lives across several views. One missing detail interrupts the task; another finding needs follow-up. The product challenge is to make the next responsible action apparent in each situation.
Context
My work on pharmacist verification connected clinical needs with product requirements, interface decisions, and operational adoption. The problem was not simply the age of the software. People needed a clearer way to assemble context, interpret relevant findings, and move through review without losing their place.
What I owned
I led the product work around requirements, launch readiness, scaling, and feedback. Design and engineering partners translated the shared direction into the interface and supporting capabilities. Clinical and operational stakeholders helped define whether the experience actually supported their work.
THE STARTING CHALLENGE
Fragmented context
The operator assembles the case across separate views and holds the connections in memory.
→
THE PRODUCT DIRECTION
Guided decision-making
The experience brings relevant context and findings into a coherent sequence, with explicit follow-up choices.
02 / THE DECISIONS
The reasoning behind the product.
DECISION 01
Organize around the task
A guided review brings patient, prescriber, and prescription context together.
The tradeoff
An isolated screen improvement would leave much of the effort of reconstructing the case with the pharmacist.
DECISION 02
Expose the exception path
Missing information and unresolved questions get a visible next step.
The tradeoff
A simple happy-path walkthrough does not explain how someone recovers when a review cannot proceed.
DECISION 03
Make adoption part of acceptance
Review usability and throughput with the people doing the work.
The tradeoff
A cleaner interface can still add interaction cost. A design needs evidence in the real workflow.
03 / EXPLORE THE FLOW
Follow a use case through the decisions.
The chart below is a reconstructed design artifact. It shows my reasoning through an invented example, rather than an internal workflow specification.
Enable JavaScript to play the synthetic scenarios and inspect the decision flow.
UX DESIGN / TRY THE EXPERIENCE
See the decision in the interface.
Compare the starting-state pattern with a guided workspace. Change the scenario and work through the screens. This independent reconstruction shows interaction design; it is not an internal product screen or a clinical tool.
Enable JavaScript to try the interface prototype.
04 / TEST THE PRODUCT THINKING
What would convince us it works?
A reconstructed evaluation plan showing the questions I would make explicit. These are evaluation criteria, not reported test results.
Use case
Expected behavior
Evidence to inspect
Complete context
The reviewer can find what is needed and understand the next action.
The workflow makes the gap visible and preserves a recoverable state.
Exception handling; ownership; ability to resume.
A question needs follow-up
The reviewer can route or document the next step without an unsupported completion.
Clarity of the handoff; context retained; downstream rework.
05 / OUTCOME & LEARNING
What the work changed.
The delivered work supported a more guided pharmacist verification experience and a foundation for further clinical workflow improvements. Specific operating results and internal artifacts are excluded here. The contribution I can show is how I connected workflow clarity, adoption, and accountable review in the product plan.
WHAT I WOULD CARRY FORWARD
I would keep a decision map alongside the screens throughout a redesign. It gives reviewers a way to challenge what the interface asks a person to decide, not just how it looks.