A UX portfolio case study is the document that stands between months of design work and a hiring decision, the artifact every UX, product design, and research role asks for before an interview even happens. It exists because a resume can list responsibilities but only a well-told case study can prove judgment: how you chose the right problem, what you actually decided and why, and what happened as a result. The hard part is that most reviewers spend well under a minute per case study, so the same instinct that makes a good design, ruthless prioritization of what matters, has to be turned inward on your own work. This cheat sheet covers how to structure and frame case studies, tell the story of your process rather than just your outcomes, package and present that work across portfolio platforms and interview formats, and adapt all of it to the specific role you're chasing.
What This Cheat Sheet Covers
This topic spans 13 focused tables and 105 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Case Study Anatomy & Structure
Every strong UX case study is built from the same handful of load-bearing sections, arranged so a reader who only skims still gets the whole arc. Get these in the right order before worrying about visuals or copy polish.
| Section | Example | Description |
|---|---|---|
"Users abandoned checkout at the final step; the redesign goal was to cut the abandoned-cart rate by at least 55%." | Frames the challenge and its stakes before any process is shown; should read as one clear sentence, not a paragraph. | |
"Sole UX designer on an Agile team with 3 developers, a product owner, and a QA engineer." | States what you personally owned versus what teammates contributed; balance "I" with "we." | |
"8 moderated usability interviews plus a competitive audit of 4 checkout flows." | Lists the methods used and the insight each produced, not just a method name. | |
Paper sketch → grayscale wireframe → clickable prototype → final UI, each captioned with what changed and why. | Shows the messy middle: sketches, rejected directions, feedback loops, not only the finished screens. | |
Two or three hero screens of the shipped or final design, shown large. | The polished result; pair with a couple of hero screens rather than a slideshow of every screen. |