When a “Simple Notes Feature”
Became a Clinical Safety Decision
Leading design strategy for a disease management platform
When your navigation choices could literally affect patient safety
Design Director | 0 → 1 Product ● Cross-Functional Influence
The Challenge
When “just add a notes page” wasn’t quite that simple
Picture this: Product comes to the table with what seems like a perfectly reasonable proposal. “Let’s add a Notes page to the patient profile where clinicians can document their observations.”
Clean. Scoped. Low-risk. Ship it, right?
Not so fast.
From a delivery standpoint? Sure, it was straightforward.
From a clinical workflow standpoint? We were about to create a problem that could compromise patient safety.
And here I was, having to convince the team that this wasn’t me being a perfectionist about navigation patterns – this was about how clinicians actually think when lives are on the line.
No pressure or anything.
What Was Actually at Stake
Why this wasn’t just another UX debate
Here’s the thing about clinicians that I learned pretty quickly: they don’t think in screens. They think in patient state.
In our disease management platform, a typical workflow looked like this:
- Review vitals trending over the past week
- Cross-reference lab results with therapy administration history
- Document an observation or adjust a care plan
- Check previous notes for context
Now imagine forcing them to navigate away from all that patient data every single time they need to add or reference a note. What happens?
In regulated healthcare, this isn’t just inefficiency – it’s risk.
A clinician toggling between screens to verify a trend before documenting could miss something critical. Or worse, a document based on incomplete recall because they’re trying to remember what they saw two clicks ago.
This wasn’t a UI decision. It was a workflow integrity decision.
And suddenly “just add a notes page” didn’t seem so simple anymore, did it?
My Approach
Because “this feels wrong” isn’t a design argument
So here’s what I did instead:
1. I mapped the clinician’s cognitive journey
I literally sketched out every moment when clinicians would need to reference notes during their patient review:
- While interpreting a vital sign trend
- After reviewing lab results
- Before adjusting a therapy dose
- During handoff preparation
And you know what became crystal clear? In every single scenario, notes functioned as supporting context, not a primary destination.
Plot twist: The notes weren’t the main character of this story.
2. I brought the workflow into the room
In our design review, instead of showing two pretty mockups and asking which one looked better, I walked through the actual sequence of actions a clinician would take:
3. I partnered with engineering early
Here’s where design leadership gets real: instead of presenting this as a blocker or a “my way or the highway” situation, I sat down with the engineering lead, and we figured out together what “lightweight and in-context” could actually mean within our constraints:
- Tight scope boundaries: View and add only, no complex filtering yet
- Performant slide-out panel: Not a modal that hijacks focus
- Reusable pattern: Could be applied to other secondary actions later
This shifted the entire conversation from “whether we should do this” to “how we’re going to build this”.
That’s what good cross-functional collaboration looks like.
The Resolution
When the team actually aligns (it’s beautiful when it happens)
- View and add notes without navigating away from vitals and trends
- Maintain mental continuity while documenting observations
- Treat notes as a parallel layer, not a separate destination
MORE CASE STUDIES
Explore Other Work
Leadership stories and design solutions across regulated industries
