By Quick answer: How do I write a UX case study?
- TL;DR — problem, role, outcome in three lines.
- Problem and constraints — the real situation.
- Research → insights — what you learned that changed the design.
- Options → decisions — trade-offs, explicitly.
- Testing → outcome → reflection — evidence and learning.
Key takeaways
- A case study is a story about decisions, not a list of methods.
- Insights matter more than activities — say what changed your mind.
- Show at least one idea you rejected and why.
- Quantify outcomes honestly; qualitative evidence counts too.
- Write for a two-minute skim and a ten-minute read.
A UX case study is not a project report. It's a story with a clear arc: a real problem, a designer making decisions under constraints, and a result. The best ones are readable in two minutes and rewarding in ten. Here's a template, and a worked example to show how it fits together.
The template
1. TL;DR
Problem · your role · team · timeframe · outcome — in three lines.
2. Context and problem
Who's affected, what's broken, the evidence, and why it mattered to the business.
3. Constraints
Time, technology, business rules, team size, regulations.
4. Research and insights
Methods chosen and why1; the two or three insights that changed the design.
5. Options explored
At least two directions, with sketches or wireframes.
6. Decisions and trade-offs
What you chose, what you gave up, and why.
7. Design
Key screens, annotated; accessibility considerations3.
8. Testing and iteration
What you tested, with whom, what failed, what changed.
9. Outcome
Metrics or qualitative evidence; what shipped.
10. Reflection
What you'd do differently; what you learned.
A worked example (condensed)
TL;DR: Redesigned KYC for a lending app; product designer in a team of five; six weeks; KYC completion rose from 54% to 71% in the first month after launch (illustrative).
Problem: Nearly half of applicants abandoned KYC. Support tickets cited confusing document steps and failed selfie checks.
Constraints: Regulatory steps couldn't be removed; low-end Android devices; many first-time borrowers.
Insight: In interviews, users didn't know why each step was needed and feared their data was unsafe. Failed selfies happened in poor light.
Options: (A) a single long form; (B) a step-by-step flow with progress and reasons; (C) assisted KYC by video call. Chose B, with C as fallback for repeated failures — B was feasible in six weeks; C needed staffing.
Design: Progress bar, one task per screen, plain-language "why we need this", lighting tips before the selfie, Hindi and English.
Testing: Five users per round across two rounds — enough to find most usability issues2. Round one revealed the PAN step's error message was unclear; rewritten for round two.
Reflection: Should have involved the compliance team earlier — two late changes cost a week.
Make it skimmable
- A TL;DR box at the top
- Headings that tell the story on their own
- One idea per paragraph
- Captions on every image
- Before/after comparisons for the key change
- Your role stated clearly
Choose methods that produce real insights — see UX research methods — and assemble two or three case studies into a portfolio that stands out.
Key terms, defined
TL;DR — a short summary for skimmers. Insight — a finding that changes what you design. Trade-off — what you gave up to get what you chose. Iteration — improving a design through testing. Outcome — the measurable result.
Frequently asked questions
How long should a UX case study be?
Long enough to show your thinking, short enough to skim — typically a few minutes to read, with a TL;DR at the top and clear headings so a reviewer can get the gist in under a minute.
What if my project didn't ship?
Show the research, decisions and testing anyway, explain why it didn't ship, and what you learned. Unshipped work with strong thinking is still valuable.
What if I don't have metrics?
Use usability test results, task completion, qualitative quotes, stakeholder adoption, or design quality improvements. State what you'd measure if you could.
Should I include every research method I used?
No. Include the methods that produced insights that shaped the design, and explain how.
How do I show my role in a team project?
State your role at the top and use 'I' for your contributions and 'we' for team decisions. Interviewers will ask, so be precise.
Can I write a case study for a concept project?
Yes, if you're transparent that it's a concept and you include research with real users, realistic constraints and testing.
Sources
- Nielsen Norman Group — When to use which user-experience research methods
- Nielsen Norman Group — Why you only need to test with 5 users
- W3C — Web Content Accessibility Guidelines (WCAG) overview
- Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- UX portfolio patterns that stand out — where your case studies live
- UX research methods: which to use when — choose methods that produce insights
- Career guidesHow to build a UX portfolio that gets you hired in 2027: choosing projects, case study structure, showing decisions, outcomes and presenting itHow to build a UX portfolio that gets hired in 2027: choosing projects, case study structure, showing decisions and outcomes, and presenting your work.
- Career guidesHow to get a product designer job in 2027: problem framing, end-to-end flows, working with PMs and engineers, shipping and measuring outcomesHow to get a product designer job in 2027: problem framing, flows, UI craft, research, working with PMs and engineers, metrics, pay and a plan.
- Product managementPRD template: how to write a product requirements document your team will readA PRD template for product teams: problem, goals, users, solution, requirements, metrics, risks and decisions — plus a one-page version and writing tips.
- UI/UX designUX portfolio examples: 30 patterns that make hiring managers keep readingUX portfolio examples broken into 30 patterns — homepage, case study structure, visuals, writing and proof — that make hiring managers keep reading.
- Templates & toolsFree product roadmap template: the Now–Next–Later format, with examples and how to run itA free product roadmap template in the Now–Next–Later format, with a filled example for an app, how to tie items to outcomes, and mistakes to avoid.
- Product managementWhat is a product roadmap? Types, examples and a free templateWhat a product roadmap is, the main formats (now–next–later, outcome-based, timeline), examples, a free template and how to present one honestly.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
See your product through your users' eyes.
A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.