13 — Case study
All workUser Portal
Where employees book the services their organisation provides, read their reports, and track their health over time. Built before I joined; my work has been new features, finding bugs and getting them fixed.
01
The problem
For the business
What was costing the business money or momentum, stated plainly.
For the people using it
What the people using it were actually struggling to do.
02
Constraints
What limited us
- Constraint that shaped the design
- Another real constraint
What we were aiming at
- Goal one
- Goal two
03
My scope
What I owned
- Feature design on an existing product
- Front-end work on the features I designed, and on the fixes I picked up myself
- Testing and QA across the flows
- Raising bugs and driving them to a fix with the developers who own the code
What I didn’t
- Did not design or build the original portal — it existed before I joined
04
Research
What we found
- A finding that changed your mind
- A finding with a number behind it
Where it hurt
- Pain point
- Pain point
05
Decisions
Decision 01
The specific problem this decision solved
Chosen
What you shipped
Rejected, and why
The alternatives you considered and why each lost
Decision 02
The specific problem this decision solved
Chosen
What you shipped
Rejected, and why
The alternatives you considered and why each lost
06 — The work
06 screens
desktopScreen name — what it does, and the decision it reflects
07
What happened
Measured
- Measured change, with the before and after
Knock-on effects
- What it unlocked for the business or team
08
In hindsight
I’d do differently
- What you would do differently
What it taught me
- What this project taught you
Next — 14