Healthcare · Product UX + Design systems
Marketplace UX for healthcare procurement
Buyers were assembling orders across four disconnected tools and a spreadsheet. We designed a single procurement surface – and the component system underneath it – for a cautious, compliance-heavy audience.
The situation
Hospital buyers compared quotes, checked compliance documents and tracked approvals manually. The old interface buried documents behind three clicks and had no notion of a purchasing team.
The brief
Design the core procurement flow for teams, not individuals: search, compare, approve, reorder – with compliance states visible at every step.
How we worked
Research
Rounds with buyers, approvers and suppliers; shadowed two approval chains end to end.
Model
Roles, approval states and document lifecycles mapped before any screens.
Design
Search and comparison surfaces, approval states, and a reorder flow; edge cases designed as first-class views.
System
Components and tokens shared with their existing admin tool; accessibility reviewed with clinical staff.
Deliverables
What shipped at the end.
- Role and approval model
- Procurement flow design
- Component library additions
- Accessibility review with staff
- Developer handoff notes
- Instrumentation plan
Artifacts
Material from the engagement.
What we would measure next
The numbers we would watch with the team.
We do not publish outcome claims. These are the measures we handed over with the work.
- time from search to approved order
- quote comparisons started per order
- document access before approval
- reorder share of total orders
Material
More from the engagement.
Related services
Where this work came from.
Related reading
Notes connected to this work.
Positioning before pixels: the research pass most B2B redesigns skip
Most B2B redesigns fail before the first wireframe – because nobody agreed what the company is actually selling. Here is the research pass that fixes it.
Read article
Design tokens are an operations problem, not a CSS problem
Teams rarely fail at token syntax. They fail at naming, ownership and the quiet drift that starts the week after launch.
Read articleEngagement records describe objectives, decisions and deliverables. Client names, logos and outcome figures stay with the client.
Next step
Planning work like this?
Tell us the situation and the constraint you are working inside.