01Measured workflow
Four clicks to one
The common messaging task became directly accessible.
Selected product work
1nHealth
Small delays inside a healthcare recruitment platform multiplied across the team’s day. Redesigning the interface and implementation made two frequent workflows markedly faster.
A common task fell from four clicks to one; a key lookup fell from about five seconds to half a second.
Situation and responsibility
What was at stake
Internal teams used the platform repeatedly throughout the day to recruit and communicate with participants.
A common messaging action took four clicks, while an important lookup took roughly five seconds. Each delay was small in isolation but expensive at workflow frequency.
- Client
- 1nHealth
- Users
- Internal recruitment teams
- Focus
- High-frequency workflows
- Responsibility
- Interface and implementation improvements
Diana’s responsibility
- Observed friction in repeated staff tasks
- Reduced steps in the messaging workflow
- Improved the implementation behind a slow lookup
- Treated performance and interaction design as one problem
Important decisions
Judgment made visible
Each response follows from an observed condition. The last column marks the tempting shortcut the work needed to avoid.
| What you notice | What it may mean | A useful response | What to resist |
|---|---|---|---|
| Messaging required four clicks. | Routine work was carrying avoidable interaction cost. | Put the frequent action directly in reach. | Do not optimize rare edge cases first. |
| A key lookup took about five seconds. | Interface polish could not hide implementation delay. | Redesign the visible workflow and the underlying query together. | Do not treat speed as a separate engineering concern. |
Decisions and delivery
How the work moved
- 01
Find repeated friction
Focus on tasks whose cost compounded across each staff member's day.
- 02
Shorten the path
Remove intermediate actions and improve the lookup behind the interface.
- 03
Measure the difference
Compare click count and response time on the same routine workflows.
Working through a similar constraint?
Describe the problem →Visual evidence
The product in view
This project has one approved image in the archive. It is shown at full scale without implying a larger undocumented gallery.
Supported outcomes
What the evidence supports
Quantitative claims appear only where the repository provides them. The remaining outcomes are explicitly qualitative, operational, or statements of responsibility.
02Measured performance
About 5s to 0.5s
A key lookup became roughly ten times faster.
03Operational effect
Less daily friction
The benefit repeated every time internal staff used these tools.
Bring me the version that is hard to explain.
If seconds and clicks are accumulating across your team’s day, show me the workflow.
Describe a similar problem →