- Every result sentence names the measure, the period and the comparison it uses.
- Screens appear after the reasoning that produced them, so a reader can follow the decision.
- Each claim about users traces back to a session, a ticket or a survey you ran or read.
- Confidential product details, client names and internal metrics are removed or cleared for release.
- Images show the screens you designed, with any real customer data replaced by placeholders.
Technical & ProductContent Creator
UX case study: show the reasoning, not only the screens
A UX case study explains one design problem from the user's side: who was affected, what you learned, what you chose and what happened afterward. Reviewers look for your role in each decision, so name what you did and what the team did. Include a result only when you can show how it was measured, and say plainly when it was not.
What people search
UX case study: 480 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
UX case study template: 140 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Example excerpt
Worked example: the decision section
Sample section
Illustrative example. The clinic, the people and the results are fictional. Decision: one question per screen Most people in the first round of sessions stopped on the insurance step and asked whether they had to type the policy number. The first design put eight fields on one screen. We split the form into one question per screen, with a Why do we ask? link beside the two questions people hesitated over most. Trade-off: the new flow takes more taps for someone who already knows every answer. We accepted that cost because the front desk reported that most delays came from incomplete forms, not from slow typing. My role: I ran the sessions, wrote the first flow and tested the wording with the front-desk lead. The engineers built the screens, and the clinic manager approved the copy. Outcome: during the two-week pilot, the front desk recorded how many forms came back with missing information. We had no baseline from the same weeks last year, so we report the pilot count only and make no comparison.
Section outline
Structure for a case study a hiring manager can scan
Context
The product, the users, the business goal and the team you worked with. Keep it to what a reader needs in order to judge the problem.
90 wordsProblem
One sentence that states the user's problem in their own terms, followed by the evidence that it was real, such as session notes or support tickets.
80 wordsYour role
The decisions you owned, the ones you influenced and the ones others made. Use I for your own work and we for the team's, and keep the two distinct.
70 wordsProcess and decisions
Two or three decisions, each with the options you considered, the trade-off you accepted and the evidence that drove the choice.
300 wordsOutcome and limits
What happened after launch, how it was measured, what was not measured, and one thing you would do differently next time.
120 words
Total: 660 words
Quality checklist
Check the case study against its evidence
Mistakes to avoid
Mistakes that weaken a case study
Starting with the final screens
Polished screens at the top show craft but hide the reasoning, which is what a reviewer is judging. Open with the problem and the evidence, and reveal the screens as the answer.
Claiming a result you did not measure
An outcome sentence with no measure reads as invented. If the change was never measured, say what you observed and what you could not verify.
Opening with the company's history
Three paragraphs about the company before the user problem appears lose the reader before the first screen. Keep context to a few sentences and reach the user problem early.
Showing only the chosen design
A case study with one option looks as if there was no choice. Name one option you dropped and the reason, even when the reason was time or cost.
Share the finished page
Where the case study will be read
Public link
Use a public link on your portfolio or in an application. Before you publish, confirm that every client and employer name is cleared for public use, and remove any screenshot that shows real customer data.
Team link
Share a team link with a manager or peer who is a workspace member when they should review the draft first. Ask the reviewer to tell you, after reading it, what your role was. If they cannot answer, the role section needs work.
HTML download
Download the HTML file to attach to an application or to keep as an archive copy. A recruiter may open the file weeks after you sent it, so it should read correctly without any notes from you.
Frequently asked questions
How long should a UX case study be?
Long enough to show one problem, the decisions behind it and the outcome, and no longer. Spend the most words on the decisions, since that is where a reviewer judges your work. Cut any paragraph that repeats a point you have already made.
Is there a UX case study template?
The outline in this guide works as one. Copy the five headings, write the problem in one sentence before anything else, and leave out any heading you cannot fill with evidence rather than inventing content for it.
What should a case study portfolio include besides screens?
The problem, the research behind it, the options you considered, the trade-off you accepted and the result with its measure. Screens matter, but a reviewer uses them to check the claims you made in words.
Does a case study page show how many people read it?
No. A case study page made with Attain OS Content Creator does not report views, visitors or time spent. If you need to know who opened it, send the link to a named person and ask them directly.
Browse by category
More reports in Technical & Product
Reports
Wait-time Dashboard
Visuals
System Architecture Diagram
References
Onboarding Guide
References
Knowledge Base
Pages
Interactive Prototype
Pages
Status Page
How to build it
Follow the eight-step wizard: type, assets and description, images, branding, contact and call to action, Atty Suggestions, blueprint, and generate. Atty generates one HTML page in the background. Review it, then publish and share the page link or download the HTML file.
