Case study 02
Product Discovery & Requirements
A comprehensive example of how I translate complex user needs into product requirements, including user journeys, workflows, and acceptance criteria.
- ScenarioA fictional clinic network where results live in three separate systems
- My roleProduct manager for the patient results experience
- UsersPhysicians, nurses and medical assistants
- OutputJourney map, PRD, user stories for the first release
The problem
Results are hard to find
Clinicians in a fictional clinic network check lab, imaging and pathology results in three different systems. A request came in as a solution: "add a results tab." Before writing requirements, I wanted to understand the problem behind it.
- Four log-ins to see one patient's results, on average.
- About three minutes to find a single result during a visit, while the patient waits.
- Preliminary and final results look the same, which creates follow-up calls and risk.
My approach
Research before requirements
- InterviewsTwelve interviews across three roles, asking about the last time they looked for a result, not about features.
- ShadowingFour half-day sessions in clinics to see the real workflow, including the workarounds.
- Journey mapMapped the path from "result is ready" to "patient is informed", with the pain points at each step.
- Problem statement and goalsAgreed with clinical leads what success looks like, and what is out of scope.
- PRD and storiesWrote requirements with engineering and design in the room, then tested a clickable prototype with five clinicians.
Sample artifact
From the PRD
Problem statement
Clinicians cannot see all of a patient's results in one place, so they spend time switching systems and sometimes act on results without knowing whether they are final.
Goals and non-goals
- Goal: one view of lab, imaging and pathology results for a patient.
- Goal: result status (preliminary, final, corrected) visible at a glance.
- Non-goal for release 1: ordering tests or editing results.
User stories
| As a | I want to | Acceptance criteria |
|---|---|---|
| Physician | see all results for my patient in one list | Given a patient with results in all three systems, when I open Patient Results, then I see them in one list, newest first. |
| Physician | filter by result type | When I select Pathology, Radiology or Lab, then only that type is shown, and All Results restores the full list. |
| Nurse | know if a result is final | Each row shows a status label; preliminary results are visually different from final ones. |
| Medical assistant | open the full report | When I select a row, the report and its attachments open without a second log-in. |
Key decisions
Trade-offs I made
Read-only first
Options: include ordering in release 1, or ship viewing first.
Chose read-only. Viewing solved the biggest pain and carried far less clinical risk, so it could ship sooner.
Show preliminary results
Options: hide preliminary results, or show them with a clear label.
Chose to show and label them. Clinicians said hiding them would push them back to the old systems.
Web first, mobile second
Options: build both at once, or start where most of the work happens.
Chose web first. Most result reviews happen at a workstation; mobile followed in the next release.
Outcomes
How success is measured
- 3 min to 30 sTarget time to find a result
- 1Log-in instead of four
- -50%Follow-up calls about result status
- 4.0 / 5Prototype usability score from five clinicians
The targets are illustrative. The point of the example is the chain: research findings lead to the problem statement, the problem statement leads to the stories, and every story can be tested.
Illustrative example. This work sample uses a fictional scenario and synthetic data. It does not contain confidential or proprietary employer information.