How to write a UX case study people finish reading
Hiring managers read the first screen and skim the rest. Structure the study so the skim tells the whole story.
Updated 2 November 2026
The short version
Put the outcome and your role at the top. Then the problem, two or three decisions with the evidence behind each, and what happened. If a research artefact did not change a decision, it does not need to be in the study.
Open with a summary
The first screen should answer four questions in four short lines: what the project was, what you did on it, who you worked with, and how it turned out. A reader who stops there should still know why the study is in your portfolio.
The problem, in the user's words
One real quote or observation does more than a paragraph of background. Then name the constraint you were working within — a deadline, an old system, a regulation, a budget. Good design is a response to constraints, and showing them makes your choices make sense.
Show decisions, not deliverables
Personas, journey maps and affinity walls are only interesting if they changed something. Write each decision as a short chain:
- We saw — what the research, data or testing showed.
- So we tried — the change, with the screen.
- And then — what happened, including what did not work.
Two or three of these are enough. A study with one honest dead end reads as more senior than one where every idea worked.
Show the work at a size people can read
Crop screens to the part that matters and make them large. Put a before and an after side by side. A short label on the image — “filters moved above the results” — saves the reader hunting for the difference.
Be honest about results
If you have numbers, give them with their source. If you do not, say what shipped and what you learned. Never estimate a metric and present it as measured; experienced reviewers notice. If the work is under an agreement, describe the problem and approach without confidential details, blur what you must, and ask before you publish anything.
How many, and how long
Two to four studies, each readable in a few minutes. Put your strongest first. Close the portfolio with a short line about the kind of work you want next.
Doing this in XODE
Pick a design portfolio template in the portfolio editor and give each case study a page of its own; picture boxes take your screens at full quality. Before it goes live, the publish dialog points out sample text left in, empty picture boxes and missing contact details.
More guides
- How to build a developer portfolio around your GitHub projects
- A one-page resume for freshers: what to put on it with no experience
- Will a job portal be able to read your resume? A one-minute ATS check
- A small business website: what each page is for
- Choosing and ordering the work in a photography or design portfolio
- All guides
Try it on your own work
Free, in your browser. Start from a template and replace it with your own words.