A designer spends three months on a project, runs interviews, tests prototypes and ships a redesign that improves task completion. Then she posts it in her portfolio as six screenshots with a one-line caption. Recruiters scroll past in seconds, because nothing shows what the problem was, what she did or why it mattered.

A UX case study turns your work into a story that proves how you think. It is the most important piece of any UX portfolio, and it is also the piece many designers find hardest to write. This guide explains what a case study is, how to structure it, how to write each section, what to avoid and how to review it before you publish.

What Is a UX Case Study?

A UX case study is a written and visual account of a design project. It explains the problem, your process, the decisions you made and the results. Unlike a gallery of final screens, it shows reasoning, collaboration and impact.

What a good case study shows

• Problem-solving ability: you can frame and tackle real challenges.
• User understanding: your decisions are grounded in research.
• Process: you work in a structured, repeatable way.
• Communication: you can explain complex work clearly.
• Impact: you care about outcomes, not only visuals.

Who Reads Case Studies and How

Understanding your readers shapes how you write.

Write so a reader can grasp the project in 30 seconds, then dive deeper if they choose.

Step 1: Pick the Right Project

Not every project deserves a case study. Choose work that shows your abilities.

• A real, meaningful problem: users or a business genuinely needed a solution.
• Visible process: you have artifacts such as research notes, sketches and test results.
• Clear personal contribution: you can explain your role precisely.
• Relevance to your goals: it fits the roles you want.
• Some outcome or learning: results, metrics or honest reflections.

If you lack client work, use self-initiated projects built on real problems, interviews and testing rather than a visual redesign of a popular app.

Step 2: Choose a Structure

A clear structure makes your story easy to follow. Here is a flexible template.

Adapt the structure to the project. A research-heavy project may expand the research section, while a design system project may focus on components and adoption.

Step 3: Write a Strong Summary

Most readers decide in seconds whether to continue. Start with a summary box that answers:

• What was the project?
• Who were the users?
• What was your role and the team?
• How long did it take, and which tools did you use?
• What changed as a result?

A sample summary: “Redesigned the onboarding flow for a savings app used by first-time investors. I led research and design with one PM and two engineers over eight weeks. Usability testing showed task completion rising from 58 percent to 86 percent.”

Only claim numbers you can honestly support, and explain how you measured them.

Step 4: Explain the Problem and Context

Help readers understand why the project mattered.

• Describe the users: who they are and what they need.
• Describe the business context: goals, market and constraints.
• State the problem clearly: use simple language and avoid jargon.
• Include evidence: analytics, support tickets or user quotes that show the problem.

Good problem framing shows that you do not jump straight to solutions. Teams often use a design thinking workshop to align on problems before designing, and describing a similar alignment step in your case study can show strong facilitation skills.

Step 5: Show Your Research

Research is where many case studies become convincing.

What to include

• Methods: interviews, surveys, usability tests, competitive analysis or analytics review.
• Participants: how many and who, without revealing private details.
• Key findings: the most important insights, not every note.
• Synthesis: an affinity map, journey map or persona, explained in a sentence or two.
• How findings shaped direction: link research to decisions explicitly.

Tips

• Be selective: show the artifacts that best explain your thinking.
• Explain visuals: never post a diagram without a caption that says what to notice.
• Be honest about limits: small samples or time constraints are fine if you acknowledge them.

Strong UX research habits make this section far more persuasive, because decisions backed by evidence read as professional and credible.

Step 6: Define the Problem and Priorities

Show how you moved from insights to a clear direction.

• Problem statement: a concise sentence describing what you will solve.
• Design principles or goals: a few guiding ideas for the solution.
• Priorities: what you decided to focus on and what you left out.
• Trade-offs: constraints such as time, budget and technology.

Explaining what you chose not to do often impresses reviewers, because it shows judgment.

Step 7: Show Ideation and Design Decisions

This is the heart of the story.

• Explore options: show sketches, flows or alternatives you considered.
• Explain choices: say why you selected one direction over others.
• Annotate screens: point out key decisions and the reasoning behind them.
• Show system thinking: mention components, patterns and consistency where relevant.
• Address accessibility: note contrast, readability and inclusive choices.
• Collaborate visibly: mention input from engineers, product managers and stakeholders.

Avoid dumping dozens of screens. Pick the few that best demonstrate your decisions.

Step 8: Show Testing and Iteration

Testing proves that your design works, or reveals what did not.

• Describe the method: moderated or unmoderated testing, prototype fidelity and tasks.
• Share findings: what worked, what confused people and what surprised you.
• Show what changed: before and after versions with explanations.
• Admit mistakes: learning from a failed idea shows maturity.

A structured UX audit mindset can help here: review your own design like an evaluator, and explain the issues you found and fixed.

Step 9: Present Outcomes and Reflection

End with results and learning.

Outcomes

• Metrics: task success rates, conversion, time on task, satisfaction scores or error rates, if you have reliable data.
• Qualitative feedback: user quotes or stakeholder comments.
• Business impact: efficiency gains, reduced support requests or increased adoption.
• If you lack data: explain what you learned and how you would measure success next time.

Reflection

• What went well: strengths in process or collaboration.
• What was hard: constraints, disagreements or surprises.
• What you would change: concrete improvements for next time.
• What you learned: skills or insights you carry forward.

Honest reflection builds trust more than perfect-sounding success stories.

Writing Style Tips

• Lead with the point: start sections with the main takeaway.
• Use short paragraphs and clear headings: make it skimmable.
• Prefer plain language: avoid buzzwords and unexplained acronyms.
• Use “I” for your work and “we” for the team: clarify your contribution.
• Show, do not only tell: support claims with visuals and evidence.
• Keep length reasonable: aim for a story that can be skimmed in a couple of minutes and read deeply in ten.
• Edit ruthlessly: remove details that do not support the story.

Visual Tips

Make images accessible with alt text, good contrast and readable sizes, and check how everything looks on mobile.

Case Study Length and Formats

Having both a short and a detailed version of your best projects gives recruiters flexibility.

Common UX Case Study Mistakes

UX Case Study Checklist

• Does the summary explain the problem, your role and the outcome?
• Is the user and business context clear?
• Does the research show methods, findings and how they shaped decisions?
• Are design decisions explained, not just displayed?
• Did you show testing and what changed afterward?
• Are outcomes honest, specific and supported?
• Is your personal contribution unmistakable?
• Is the writing skimmable, clear and free of jargon?
• Are visuals annotated, accessible and mobile-friendly?
• Have you checked confidentiality and permissions?
• Has someone else read it and given feedback?

Getting Started

You do not need to rewrite your whole portfolio at once. Pick your strongest project, write a short summary, add the problem, process and results, then ask someone to read it and tell you what they understood. Revise and repeat. If you want to see how professional teams organize real projects from discovery through delivery, exploring UI/UX design services can offer useful context for how engagements are structured and communicated.

Final Thoughts

A great UX case study tells a clear, honest story about a real problem and how you solved it. Start with a strong summary, show your research and reasoning, explain trade-offs and decisions, and end with results and reflection. Write for skimmers first and deep readers second, and keep editing until every section earns its place. When someone finishes your case study, they should understand not only what you designed but how you think.

FAQs

How long should a UX case study be?

Long enough to show your process and short enough to stay engaging. Many strong case studies can be skimmed in a couple of minutes and read in depth in around ten, with a summary at the top.

What should I include in a UX case study?

A summary, the problem and context, your role, research, insights, design decisions, testing and iteration, outcomes and a reflection on what you learned.

How do I write a UX case study with no real results?

Focus on process, insights and what you learned. Share evidence from usability tests, explain how you would measure success and be honest about the project’s context.

Can I include team projects in my case study?

Yes, but be very clear about your contribution. Explain your role, the decisions you made and how you worked with others.