UX Case Study Template
A UX case study is a thinking-out-loud document. Whether it is going in a portfolio or in front of a client, the reader is not buying a metric — they are buying your design judgement. So the structure is different from a sales case study: it centres on research, the problem framing, the decisions you made and why, and the usability evidence that the design actually worked. This template gives you that process-first structure, and keeps your "we improved task success by 22%" claims honest by tying them to the real test data behind them.
Use the UX template for portfolio case studies, design-team write-ups, and agency/consultancy work where the value is the design process and the usability outcome. It suits product designers, UX researchers, and design leads who need to show how they think, not just what they shipped.
The ux case study template, section by section
Each section below is annotated with what to write and the evidence that belongs in it. Copy the structure into a doc, a slide, or paste your customer evidence into the generator and let it fill the sections for you.
- 1
Project overview
Role, timeline, team, and platform in two lines. A hiring manager skims this to understand what you actually did versus what the team did — be honest about your scope.
Evidence to attach: Your role and contribution, stated plainly; the product/platform.
- 2
The problem & users
The user problem and who experiences it, grounded in research rather than assumption. This is where a UX case study earns credibility — show you started from evidence, not from a redesign you wanted to do.
Evidence to attach: User-research findings: interview quotes, survey data, or analytics on the broken flow.
- 3
Research & insights
The methods you used (interviews, usability tests, journey mapping) and the specific insight that reframed the problem. The insight matters more than the method list.
Evidence to attach: A verbatim user quote or a research finding that drove the direction.
- 4
Design decisions & process
The flows, wireframes, and the trade-offs you weighed. Show at least one decision where you chose against the obvious option and explain why — that is the signal of real design thinking.
Evidence to attach: Rationale tied to a research finding, not to taste.
- 5
Usability testing & iteration
What you tested, with whom, and what changed as a result. A loop of test → learn → revise is the strongest evidence that the final design is earned rather than guessed.
Evidence to attach: Task-success, time-on-task, error-rate, or SUS figures from real tests.
- 6
Outcome & impact
The usability and (where available) product metrics after launch: task success, completion time, satisfaction, adoption. Pair the design outcome with any downstream business effect.
Evidence to attach: Before/after usability metrics traced to the test data.
- 7
Reflection
What you learned and what you would do differently — the section that most distinguishes a senior portfolio from a junior one.
Evidence to attach: Honest reflection; no metric needed, but no invented wins either.
How to fill it in
- 1Lead with the user problem and the research that surfaced it, not with the solution — a UX reader is checking that you designed from evidence.
- 2Pick one design decision where you went against the obvious choice and walk through the trade-off; that single passage signals seniority more than a dozen polished screens.
- 3Report usability results as before/after (task success 64% → 86%) and attach the test that produced them — never round a friendly-sounding number up.
- 4Quote real users verbatim. A messy, specific user complaint is far more persuasive than a tidy paraphrase.
- 5Close with an honest reflection; admitting a limitation reads as confidence, not weakness.
Why verification matters for a ux case study
UX case studies are where "I improved usability by 30%" goes to die — reviewers have learned to distrust unsourced percentages in portfolios. A UX case study that ties each usability figure to the actual test result, and each user insight to a verbatim quote, stands out precisely because most don't. CustomerProof keeps every research quote and every task-success number traced to its source with a per-claim receipt, and strips the verified badge from any figure you edit away from the underlying data — so your portfolio claims survive scrutiny from a sharp design lead.
See per-claim receipts in the builder →Interview questions for a ux case study
Ask these to get the specific, quotable evidence this template needs — the answers become the verifiable claims in the finished study.
- What was the user problem, and what research told you it was real?
- Which insight changed how you framed the problem?
- What did you test, with how many users, and what did the results say?
- Where did you choose against the obvious design, and why?
- What did the usability metrics do from before to after?
UX case study template FAQ
What should a UX case study include?
A project overview with your real role, the user problem grounded in research, your research methods and the key insight, the design decisions and trade-offs, usability testing and iteration, the outcome as before/after usability metrics, and an honest reflection. A UX case study is judged on design thinking and evidence, not on a single business metric.
How do I show impact in a UX case study without inflating it?
Report usability metrics — task success rate, time-on-task, error rate, SUS — as before/after figures from real tests, and attach the test that produced each one. State your sample size honestly; a 22% task-success lift from a real five-user test is more credible than a round "doubled conversions" with no source.
How long should a UX portfolio case study be?
Long enough to show your process, usually 800–1,200 words plus visuals, but front-loaded so a hiring manager grasps the problem, your role, and the outcome in the first scroll. Depth in the research and decisions sections is what separates a senior case study from a screenshot gallery.