UX Case Study Writing

A UX case study walks a reader through your design process from problem to solution. Unlike a portfolio project viewed without context, a case study explains your thinking at each stage. It shows why you made certain decisions and what evidence informed those choices. For designers seeking employment, strong case studies often prove more persuasive than finished designs alone because they demonstrate problem-solving capability rather than just visual output.

design portfolio tips

The challenge in writing case studies is balancing detail with readability. Too much detail becomes tedious. Too little makes the work appear surface-level. A case study should be long enough to explain your approach but short enough to maintain reader interest. Most effective case studies run between 1,500 and 3,000 words, though this varies by complexity and medium.

Begin with the problem statement. Describe what challenge you encountered, why it mattered, and what constraints you worked within. Include relevant context about the product, users, or organisation. This foundation helps readers understand why your subsequent decisions made sense. Next, explain your research and discovery phase. What did you learn from users or data? What gaps did you identify? Then detail your design approach, including iterations and why you moved in particular directions. Finally, share the outcome. What metrics improved? What feedback did you receive? Did the design meet its goals?

Include visuals strategically. Screenshots of prototypes, wireframes, user research findings, and metrics all serve as evidence. Avoid overwhelming the case study with images; each should support a specific point in your narrative. Sketches and process work humanise your thinking. A photo of your notebook or whiteboard sketches helps readers see how ideas developed. Explain your decisions explicitly. Rather than showing a final design and assuming readers understand why you chose it, state your reasoning directly. This teaches readers about your thought process, which matters more than any individual design choice.

guide to making a case study interview-ready

Be honest about results. If a project succeeded beyond expectations, that's excellent to share. If it taught you something through failure or produced modest results, that remains valuable. Readers trust case studies that acknowledge limitations more than those claiming perfect success. If metrics weren't measured, explain why. If a design launched but was later changed, discuss that evolution. Authentic case studies build credibility because they reflect how actual work unfolds, complete with constraints and learning.

Keep language clear and avoid jargon where possible. Readers from different backgrounds should grasp your work. Use active voice and specific examples rather than abstract statements. Reference data and user feedback by name and detail rather than generalisations. A case study that shows one specific user struggle proves more engaging than vague references to "user research findings".