How to write a UX case study (and show the screens)
A UX case study is a short story about one project: the problem, your role, what you did and why, the final design and what happened next. Write it in 800 to 1,500 words, lead with the result, and show the screens in context so a reader understands the product before reading the details.
What is a UX case study?
A UX case study is a written walkthrough of one design project that shows how you think, not only what you made. It sits in your portfolio next to the final screens and explains the problem, the constraints, the options you weighed and the outcome.
A gallery of screens shows taste. A case study shows judgment: why this flow, why not the other one, and what you would change. That is the part people cannot get from the pictures.
How do I structure a UX case study?
Use one repeatable order: overview, problem, process, solution, result and what you learned. A reader who skims should still find the answer in each heading.
- Overview: the product, your role, the team, the timeline and the tools, in three or four lines at the top.
- Problem: who the users were and what was not working, in plain words.
- Process: the research, the options you explored and the decision points. Pick two or three moments, not every step.
- Solution: the final design, shown with the key screens and the reason behind each.
- Result: what changed after launch. Use a number only if you have a real one and can name where it came from.
- Reflection: what you would do differently, in two or three sentences.
If the work is under NDA, say so, blur or replace the confidential parts, and focus on your process.
How long should a UX case study be?
Aim for 800 to 1,500 words and five to ten screens or images. That is a rule of thumb, not a rule from any hiring team: the goal is a page that can be read in a few minutes and still has depth.
If it runs long, cut from the middle. Keep the overview and result strong, make each section answer one question, and move extra material, such as full research notes or every wireframe, to a separate page or an appendix.
What do hiring teams look for in a UX case study?
They look for evidence of how you solve problems: that you understood the user, made reasoned decisions, worked with others and can explain the outcome. Exact criteria differ by company, so treat this as a checklist of questions your case study should answer.
- What was the problem, and who had it?
- What was your part, as opposed to the team's?
- Which options did you consider, and why did you choose this one?
- How did you test or check the decision?
- What happened afterward, and what did you learn?
Write in the first person and be specific. "I redesigned the checkout flow after watching five people fail to find the coupon field" says more than "I improved the user experience." If you have never presented a case study live, how to present a design portfolio covers the interview side.
How do I show the screens in context?
Show the cover and the final result on a real device, and show the detail screens flat. Context tells the reader what kind of product it is at a glance; flat screens let them read the interface.
- Cover: one device scene that matches the product, such as a phone for an app or a laptop for a web product.
- Details: flat, full-resolution screens with short captions, because a tilted device hides interface text.
- Flows: a row of three or four screens in order, with a one-line note under each.
- Resolution: export screens at the device's native size, for example 2556 x 1179 px for the iPhone 15 Pro, so the mockup stays sharp.
In the online mockup generator you choose a scene, drop your screen on the device and export an image, with nothing to install. For an app project, start in the iPhone mockups category. If you work in Figma, the mockup plugin for Figma places the scenes inside your file.
Which scenes work as UX case study covers?
Pick a scene with a quiet background and a clear screen area, so your design stays the focus. Six scenes from the ls.graphics library:
- iPhone 17 Pro, scene 6, an upright phone for a mobile app cover
- iPhone 15 Pro, scene 5, a phone on a dark surface for a bolder mood
- iPhone 16, scene 23, a back view for the brand or onboarding slide
- MacBook Air (M2), scene 20, a floating laptop for a web product
- iMac 24-inch, scene 15, a desktop view for a dashboard or admin tool
- iPad Pro, scene 3, a tablet in a clear bag for a tablet layout
FAQ
How many case studies should a portfolio have?
Two to four strong ones are enough for most applications. Choose the projects closest to the job you want and cut the rest.
Do I need a number or a result to write a case study?
No. If you have no metric, describe what changed: the product shipped, a task became shorter, a team adopted your pattern. Never invent a figure.
Can I write a case study for a project I did not ship?
Yes, a concept or a student project works if you are clear about it. Say what was real and what was assumed, and focus on the thinking and the process.
Where should I publish a UX case study?
On your portfolio site, as a page you can link, and as a PDF you can attach. Put the best one first and make sure the cover image shows the product in context.