Lifeline of Medical Supply, Reimagined
Medical supply moves through this warehouse network every day. We updated their old dashboard for better PX & efficiencey.
Healthcare Logistics
UX Design
Highlights
Decades of medical-supply operations, and a dashboard rebuilt from the work people were already doing around it.
Context
Medical supply moves through this warehouse network every day. The old dashboard had accumulated workarounds around the work, so I treated those workarounds as evidence and rebuilt the interface around what the floor actually needed.
I was walking into infrastructure, not a blank page. Hospitals and clinics depend on it. Patients stay supplied because none of it ever stops.
Highlights
“Efficiency in healthcare is not just a matter of economics. It determines life and well-being.” -Joseph Stiglitz
Challenge
The official dashboard no longer represented the work, so staff built private systems around it.
Solution
I translated workarounds into requirements, then rebuilt priority, blockage, and status around operational decisions.
Outcome
The interface began carrying the knowledge that had previously lived in spreadsheets, notes, and verbal checks.
Where It Started
The unofficial system was already showing us what the dashboard had missed.
Patient demand was moving faster than the interface could support. Spreadsheets, notes, handwritten queues, and verbal checks had accumulated because essential decisions were absent from the dashboard. These workarounds proved that the official system no longer represented the work
The Operational System
Every workaround became a requirement.
I rebuilt the hierarchy around what ships next and what is blocking it. Unofficial tools became fields, states, and actions inside the product. Generic statuses were replaced with specific reasons written in the warehouse's own operational language.
Judgment Log
A cleaner dashboard would have preserved the wrong system.
I trusted observed behavior over the apparent completeness of the old interface. Every workaround was treated as a possible requirement, then tested before entering the product. Replacing "pending" with the real blocking reason turned status into an operational instruction.
Outcome & Closing
The interface started teaching the work instead of hiding it.
Shipment flow became easier to coordinate, onboarding became more direct, and staff relied less on private backup systems. The official interface could finally carry knowledge scattered around the warehouse. Nobody throws a party for a spreadsheet's retirement, but its absence was meaningful.
More Works
©2026
FAQ
01
What kind of problem is worth bringing to you?
02
Do you work as a designer, founder, or advisor?
03
What do you need before a first conversation?
Lifeline of Medical Supply, Reimagined
Medical supply moves through this warehouse network every day. We updated their old dashboard for better PX & efficiencey.
Healthcare Logistics
UX Design
Highlights
Decades of medical-supply operations, and a dashboard rebuilt from the work people were already doing around it.
Context
Medical supply moves through this warehouse network every day. The old dashboard had accumulated workarounds around the work, so I treated those workarounds as evidence and rebuilt the interface around what the floor actually needed.
I was walking into infrastructure, not a blank page. Hospitals and clinics depend on it. Patients stay supplied because none of it ever stops.
Highlights
“Efficiency in healthcare is not just a matter of economics. It determines life and well-being.” -Joseph Stiglitz
Challenge
The official dashboard no longer represented the work, so staff built private systems around it.
Solution
I translated workarounds into requirements, then rebuilt priority, blockage, and status around operational decisions.
Outcome
The interface began carrying the knowledge that had previously lived in spreadsheets, notes, and verbal checks.
Where It Started
The unofficial system was already showing us what the dashboard had missed.
Patient demand was moving faster than the interface could support. Spreadsheets, notes, handwritten queues, and verbal checks had accumulated because essential decisions were absent from the dashboard. These workarounds proved that the official system no longer represented the work
The Operational System
Every workaround became a requirement.
I rebuilt the hierarchy around what ships next and what is blocking it. Unofficial tools became fields, states, and actions inside the product. Generic statuses were replaced with specific reasons written in the warehouse's own operational language.
Judgment Log
A cleaner dashboard would have preserved the wrong system.
I trusted observed behavior over the apparent completeness of the old interface. Every workaround was treated as a possible requirement, then tested before entering the product. Replacing "pending" with the real blocking reason turned status into an operational instruction.
Outcome & Closing
The interface started teaching the work instead of hiding it.
Shipment flow became easier to coordinate, onboarding became more direct, and staff relied less on private backup systems. The official interface could finally carry knowledge scattered around the warehouse. Nobody throws a party for a spreadsheet's retirement, but its absence was meaningful.
More Works
©2026
FAQ
01
What kind of problem is worth bringing to you?
02
Do you work as a designer, founder, or advisor?
03
What do you need before a first conversation?
Lifeline of Medical Supply, Reimagined
Medical supply moves through this warehouse network every day. We updated their old dashboard for better PX & efficiencey.
Healthcare Logistics
UX Design
Highlights
Decades of medical-supply operations, and a dashboard rebuilt from the work people were already doing around it.
Context
Medical supply moves through this warehouse network every day. The old dashboard had accumulated workarounds around the work, so I treated those workarounds as evidence and rebuilt the interface around what the floor actually needed.
I was walking into infrastructure, not a blank page. Hospitals and clinics depend on it. Patients stay supplied because none of it ever stops.
Highlights
“Efficiency in healthcare is not just a matter of economics. It determines life and well-being.” -Joseph Stiglitz
Challenge
The official dashboard no longer represented the work, so staff built private systems around it.
Solution
I translated workarounds into requirements, then rebuilt priority, blockage, and status around operational decisions.
Outcome
The interface began carrying the knowledge that had previously lived in spreadsheets, notes, and verbal checks.
Where It Started
The unofficial system was already showing us what the dashboard had missed.
Patient demand was moving faster than the interface could support. Spreadsheets, notes, handwritten queues, and verbal checks had accumulated because essential decisions were absent from the dashboard. These workarounds proved that the official system no longer represented the work
The Operational System
Every workaround became a requirement.
I rebuilt the hierarchy around what ships next and what is blocking it. Unofficial tools became fields, states, and actions inside the product. Generic statuses were replaced with specific reasons written in the warehouse's own operational language.
Judgment Log
A cleaner dashboard would have preserved the wrong system.
I trusted observed behavior over the apparent completeness of the old interface. Every workaround was treated as a possible requirement, then tested before entering the product. Replacing "pending" with the real blocking reason turned status into an operational instruction.
Outcome & Closing
The interface started teaching the work instead of hiding it.
Shipment flow became easier to coordinate, onboarding became more direct, and staff relied less on private backup systems. The official interface could finally carry knowledge scattered around the warehouse. Nobody throws a party for a spreadsheet's retirement, but its absence was meaningful.
More Works
©2026
FAQ
What kind of problem is worth bringing to you?
Do you work as a designer, founder, or advisor?
What do you need before a first conversation?