Context A specialty prescription passes through more hands than a normal one.
The prescriber, the pharmacy, an approval step, sometimes a nurse, and always the patient waiting to know what happens next. Each handoff was a phone call or a fax, and nobody had the whole picture.
How I found out Research before commitment.
Mapped the journey across patient, prescriber and pharmacy first, to find the steps that only existed because the old process had them. Design decisions were framed as hypotheses and checked in prototype tests with users before anything was committed.
What I did Map the journey first, then cut the steps the old process invented.
Designed the platform end to end: prescription management, patient workflows and provider coordination, across web and mobile. Mapped the journeys first, then removed the steps that only existed because the old process had them.
With the team Hypotheses we could check with users before committing.
Partnered with product and engineering through research, journey mapping, prototyping and usability testing, with design decisions framed as hypotheses rather than opinions.
What changed One place to see where a prescription stands, and to act on it.
A patient can see where each prescription stands, and a provider can act on it from the same place, with far less back and forth in between.
After launch What happened next.
add yoursWhat the months after launch looked like: adoption, what the team kept, what was cut, and the follow-up work it led to. Two or three sentences are enough.
What I’d do differently One thing I got wrong, and what I learned from it.
add yoursReviewers trust a case study more when it admits a misstep. Name one call that did not land, what it cost, and what you do differently now because of it.