Principle one
A belief you held the work to. One crisp sentence of what it means in practice.
Case study/002Add category
A one-line promise of the outcome this project delivered.
Overview
Two or three sentences of context: who this was for, what space it lived in, and why it mattered. Keep it tight — the reader should grasp the stakes before the first scroll.
Then a sentence on what you delivered at the highest level.
01 The problem
A sentence that names the core conflict — what users (or the business) needed versus what the current state actually allowed.
What was breaking, for whom, and the cost of it. One sharp paragraph.
A second dimension of the problem — process, scale, clarity, or trust.
The thing that made it hard to solve, not just hard to live with.
Why existing tools or patterns fell short here.
02 The solution
One line on the central design move — the bet that everything else hangs from.
Explain the surface, the interaction, and the why behind it. Tie it back to a problem above.
A second feature or flow, with the reasoning and any trade-off you made.
03 Principles & framework
Three to six principles that guided the calls, plus the process that got you there.
A belief you held the work to. One crisp sentence of what it means in practice.
Another guiding rule and the behaviour it produced.
A third — ideally one that reveals a trade-off you were willing to make.
Keep them specific to this project, not generic design platitudes.
Optional — remove cards to fit your real list.
Optional.
How you learned the problem — research, data, shadowing.
The model or framing that unlocked the rest.
How you turned it into reusable patterns or a system.
How you tested, measured, and refined before ship.
04 The deliverable
Show the final thing in its best light, then the impact.
Replace these with your real results, or remove the block if you can’t share numbers yet.