​I grew up with a doctor in my family. I watched long days, shifting between patients while juggling screens and menus that slowed them down. That’s why workflow clarity isn’t abstract to me, it’s real.
WHY THIS PROJECT MATTERED?
THE REAL PROBLEM
​
​
Doctors were navigating fragmented screens and unclear information hierarchy, leading to increased cognitive load and workflow friction. The redesign reorganized patient data, prioritized urgent information, and reduced unnecessary steps in daily tasks.
WORKFLOW MAPPING
​
Start shift
→ Review today’s schedule
→ Open patient file
→ Scan history, labs, medications
→ Document notes
→ Move to next patient
What stood out wasn’t complexity.
It was hierarchy.
Critical information was visually equal to secondary information.
Urgency was not differentiated.
Navigation required unnecessary context switching.
The system was built around modules.
Doctors operate around moments.
That disconnect shaped the redesign.
USERS INSIGHTS
Doctors don’t think in modules.
They think in patient moments.
The system was built around features.
It needed to be rebuilt around flow.
KEY DESIGN DECISIONS
Clean section. Minimal design.
3 strong pillars.
1. Consolidated Patient Overview
Reduced dependency on tab-switching by centralizing critical information.
2. Dense but Structured Layout
Prioritized scanability over minimalism.
3. Consistent Module Architecture
Unified layout patterns to reduce learning curve.
4. Context-Preserving Navigation
Minimized workflow interruption.
Before & After
DASHBOARD
Doctors orient within seconds instead of scanning the entire screen
​
Before: Before, doctors logged in and scanned for context — like waking up without coffee. After, the dashboard orients them instantly — urgent tasks first, today’s schedule second, so they’re ready before they start.
After:
A focused operational control center:
• Today’s patients first
• Urgent alerts highlighted
• Quick actions visible without digging
• Customizable modules
PATIENT RECORDS
Critical information now surfaces immediately.
Secondary data supports — not competes.
​
Before: Hard to scan, no hierarchy
After:
Changes included:
• Structured history sections
• Clear medication hierarchy
• Labs grouped by clinical relevance
• Reduced visual density
• Strong typographic contrast
Why it matters: Critical patient info is accessible instantly — reducing risk and saving time.
SCHEDULE MANAGMENT​
​
Before: Disconnected tools + friction
After: Calendar design with quick actions and conflict alerts
Improvements:
• Faster appointment edits
• Clear conflict indicators
• Reduced menu depth
• Simplified transitions between patients
​
Why it matters: Fewer mis bookings, smoother collaboration, optimized resource use.
REPORTS
​​​
Before: Overwhelming data dumps
After: Charts and summaries with filters
​
Why it matters: Teams can see trends and act, not just stare at tables
Final
Thoughts
DESIGNED IMPACT
Even modest time savings per patient scales across entire clinics.
​
~30–40% fewer steps in high-frequency tasks
Reduced context switching
Lower cognitive load
Improved operational efficiency potential
WHAT I LEARNED
​
This project changed how I think about information architecture entirely: IA isn’t about structure — it’s about trust. When users don’t have to remember where they are, they can focus on what matters.
