UX Foundations · Step 8 · 6 min read
Case studies and your portfolio
A portfolio is a product for a busy reader, and each case study is a short story about a problem. The structure of a UX case study (problem, role, process, decisions, outcome), how to show your process honestly, how to describe work under NDA without screens, and what hiring managers say they look for.
Good work that nobody can understand doesn't get you hired. Design is invisible once it ships: people see screens, not the problem you solved or the ten ideas you threw away. A case study makes that thinking visible. It tells a short, honest story: what was wrong, what you did, why you chose what you chose, and what changed. Screens help, but the story is what a reader remembers.
What you'll be able to do after reading:
- Structure a UX case study in five parts
- Show your process honestly, including what didn't work
- Describe work under NDA without showing screens
- Build a first portfolio, even as a career changer
1. Who reads your portfolio
Treat your portfolio like any design: start with its users. They are hiring managers, recruiters and other designers, and they are busy. In NN/g's article on design portfolios, Rachel Krause warns that "Very rarely will hiring managers take the time to read your entire portfolio word for word", so it must be scannable (NN/g, Krause, 5 Steps to Creating a UX-Design Portfolio, 2019).
NN/g surveyed 204 UX professionals in charge of hiring for that article. One of them said: "Don't just show me the finished product. I want to see the messy process and all the work and research that was put in to land on that shiny polished design."
2. The shape of a case study
- 1Problem
Who struggled, with what, and why it mattered.
- 2Role
What you did, and with whom.
- 3Process
What you learned and tried, including dead ends.
- 4Decisions
The choices you made and the reasons.
- 5Outcome
What changed for people, and what you learned.
NN/g's list of what a case study should include (same article) maps well onto five parts:
| Part | What to write | Example (fictional) |
|---|---|---|
| Problem | Who struggled, with what, why it mattered | "Customers of a small pharmacy app missed refill reminders, so they ran out of medicine." |
| Role | What you did, and with whom | "Sole designer, with two developers and a product manager, for eight weeks." |
| Process | Research, ideas, tests, dead ends | "Five interviews; three concepts; one was dropped after people found it intrusive." |
| Decisions | The choices and the reasons | "We moved reminders into the home screen because people never opened settings." |
| Outcome | What changed, and what you learned | "In a test with five people, all found the reminder; after launch, missed refills fell. Next time I'd test with older users sooner." |
NN/g recommends choosing 3 to 5 projects as detailed case studies, and says quality beats quantity. If you're short on time, one or two strong ones are better than six thin ones.
3. Show the process honestly
- Show what didn't make it. One hiring manager in the NN/g survey said: "I'm curious to know what isn't in the design and why, just as much as I'd like to know why elements made it in."
- Be clear about your part. "We" hides who did what. Say what you did, and credit the others.
- Be honest about results. If you don't have numbers, say what you observed ("all five testers completed the task"). Never invent a metric.
- Name the constraints. NN/g's researcher-portfolio article suggests acknowledging limits like a small budget or a convenient sample: it shows you can work in real conditions (NN/g, Kane, Portfolios for UX Researchers: Top 10 Recommendations, 2019).
- Label personal projects. The same article says "it's important to clearly note what work was completed as part of a personal project versus professional work." For career changers, a well-told personal or volunteer project is a fine start.
4. Work under NDA
Much real work is covered by a nondisclosure agreement (NDA). NN/g suggests showing process instead of polished screens, blurring identifying information, or recreating the design in a generic style (NN/g, Krause, 2019).
The safest option, and this course's advice, is to describe the work without screens: no client name, no logos, no real data, no screenshots. Tell the problem in general terms ("an internal tool for planning deliveries"), then the process, your decisions and the kind of outcome. Sketches you redraw from scratch, simple diagrams of a flow, and a clear written story can show your thinking without showing anything protected. Check your contract, and ask when in doubt.
5. Common mistakes
- A gallery of final screens with no problem, role or reasons.
- Long walls of text that nobody will read; or the opposite, no text at all.
- Hiding failures and dead ends, so the process looks too perfect to be true.
- Showing client screens, names or data that are under NDA.
- Using the same portfolio for every job, instead of choosing the projects that fit.
6. Vocabulary
| Term | Meaning |
|---|---|
| Portfolio | A small, curated collection of your work |
| Case study | The story of one project: problem, role, process, decisions, outcome |
| NDA | Nondisclosure agreement: a contract that forbids sharing certain information |
| Outcome | What changed for people or the business because of the work |
| Constraint | A limit you worked within: time, budget, technology, data |
7. Try it (no tools needed)
- Pick one project: from work, a course, or a personal redesign (the form you redesigned in this path is a good candidate).
- On one sheet of paper, write the five parts: problem, role, process, decisions, outcome. One or two sentences each.
- Add one thing you tried that didn't work, and why you dropped it.
- Read it to a friend who isn't a designer. Ask them to explain the project back to you in their own words.
Reflection questions: Could someone understand your contribution without seeing a single screen? What would you need to remove if the project were under NDA?
8. If you already practise
- Before writing, decide the top three things a reader should take away about you, as NN/g suggests, and check them again when you finish.
- Keep a project log as you work (photos of sketches, decisions, test notes); it makes case studies much easier to write later.
- Tailor: hide projects that don't match the job, and put the most relevant one first.
- For how AI is changing what portfolios need to show, see Your design career in the AI era.
Checklist
Learn more
- NN/g: 5 Steps to Creating a UX-Design Portfolio (2019, updated 2026) · Portfolios for UX Researchers: Top 10 Recommendations (2019)
Books, courses and videos to go deeper
- Show Your Work!Austin KleonBook · Workman, 2014
Related
Your design career in the AI era · Defining success · Design critique in practice · Problem statements and "How might we" · Redesign a form