
- Role
- Lead product designer
- Engagement
- End-to-end engagement
- Focus
- Healthcare · B2B SaaS · Mobile app
01 / Context
The product and its operating environmentA mobile collaboration app for physicians that streamlines consultation requests, documentation, and OHIP billing.
02 / Challenge
The complexity worth solvingMake complexity feel simple, without removing what matters.
MD2MD had to bring specialist discovery, consultation handling, documentation, and OHIP billing into one mobile workflow without sacrificing the clinical and administrative detail physicians rely on.
03 / Product direction
From evidence to shipped experienceUnderstand
I mapped the physician journey across onboarding, specialist discovery, consultation capture, and billing to understand where complexity accumulated and where users needed the most clarity.
Structure
I organized the experience around the physician’s actual sequence of work, progressively introducing verification, documentation, and billing requirements only when they became relevant.
Deliver
The resulting experience connected account setup, consultations, and billing into one coherent workflow with clearer states, actions, and next steps throughout.
04 / Key decisions
Three decisions that shaped the experienceProgressive onboarding
Verification, profile completion, and billing setup were split into guided steps to reduce cognitive load and make account setup easier to complete.
Faster specialist discovery
Search, availability, specialty, and location were prioritized so physicians could identify the right specialist quickly in time-sensitive situations.
Billing in context
Billing was integrated into the consultation workflow instead of treated as a separate task, improving status visibility and reducing administrative follow-up.
05 / System
A foundation built to scaleDesigned to stay coherent as it grows.
Reusable interaction patterns across forms, records, statuses, navigation, and validation kept the 79-screen experience consistent and made the product easier to implement and extend.
06 / Product screens
Swipe, drag, or use the arrow controls







07 / Outcome
What changedStakeholder-approved flows translated a complex physician workflow into a coherent product experience ready for implementation and launch.
08 / Reflection
What I carried forward“The biggest lesson was that regulated workflows do not need less information, they need better sequencing.”