The Case Study Structure That Gets Interviews

Hiring managers spend an average of 3–5 minutes reviewing a portfolio. In that time, they're asking one question: "Can this person solve design problems?"

Your case study's job is to answer that question clearly.

The structure that works

1. The Problem (1–2 paragraphs)

Start with the why. What problem existed, for whom, and how did you discover it?

Don't start with "I was tasked with redesigning the checkout flow." That tells me nothing interesting. Instead:

"45% of users abandoned checkout before completing a purchase. Through session recordings and exit surveys, we found the primary friction point was uncertainty about shipping costs."

Specific. Problem-first. Tells me you can identify what matters.

2. Your Role

Be honest about what you specifically did. "We" is vague and makes reviewers nervous. "I led the research and prototyping while our PM owned stakeholder alignment" is clear.

3. The Process (show your thinking, not every step)

You don't need to show every post-it note. Show the decisions that mattered:

• What did you learn from research that changed your direction?
• What did you try that didn't work?
• Where did you have to make a tradeoff?

4. The Solution

Now show the final design — in context. Don't just show screens. Show the experience. Use annotations to explain why things are designed the way they are.

5. The Outcome

Metrics where you have them. Learning where you don't. Even "we shipped but haven't measured yet, but here's what I'd measure and why" shows maturity.

The one rule above all

Never show work you can't explain. If a reviewer asks "why did you use a bottom tab bar instead of a hamburger menu?" and you can't answer — that case study is hurting you, not helping you.

Only include work you can defend confidently.