04 — Case study
All workPolicy Creator
Where the rules and services that apply to each client are defined, and every service-related setting is configured. Most flows across the other four portals depend on what is set here, which makes it the heart of the platform.
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
- Had to fit the platform the other four portals were already built on
- Another real constraint
What we were aiming at
- Make client rules and services configurable without an engineer
- Another goal
03
My scope
What I owned
- Designed and built the portal end to end — the only one in the platform I made from nothing
- Defined how rules and services are configured, and how those settings propagate to the other portals
- Presented the portal during a major enterprise onboarding
- Testing, QA and bug fixing on my own code
What I didn’t
- Anything you did not own here — backend, infra, a teammate’s area
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
07 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 — 05