Building a Design Case
A portfolio isn't a collection of pretty screens - it's a story about how you think. Before you ever set foot in an interview room, it has already made a case for you, or against you.
Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.
Recruiters spend a few minutes on a portfolio - sometimes less - before deciding whether to talk to you. So it has to communicate fast, clearly, and with a point of view. The strongest portfolios don't just show finished designs; they show the messy middle: the research behind a decision, the directions that didn't survive, the reason the team chose B over A.
You don't need a big-name company on your CV to do this well. You need to show your thinking honestly - including where it got hard. Start with the work you can build this week, publish it, and improve it later. A live portfolio with three honest cases beats a perfect one that doesn't exist yet.
Case Studies That Get Read
Your work can be brilliant and still lose the room if the case study around it is a wall of screens with no story. Reviewers don't read portfolios - they skim them. A case study earns a real read when it's easy to open and tells a story, not when it lists every step you took.
Make It Easy to Open
One format choice matters more than most people realize: a web link beats a PDF every time. Not because it looks more professional, but because the friction is lower - a link opens instantly, while a file needs a click, a permission, and a wait. Lower friction means a higher chance they actually look. Build a website, not a slideshow.
Answer Four Questions Fast
A strong case study answers four questions a reviewer has in the first thirty seconds:
- What was the problem? Not "redesign the app" - the actual user pain.
- What did you do? Briefly: research, ideation, testing, iteration.
- Why did you make these choices? This is where most portfolios go quiet - and where yours can stand out.
- What was the result? Even a qualitative outcome beats silence.
Keep the selection focused. Three deep cases beat ten shallow ones. A reviewer who finishes one case study understanding how you think is worth more than one who scrolled ten finished screens and remembers none of them.
Tell It as a Story
Most portfolios are process theater - the same double-diamond diagrams and sticky-note photos, in the same order, that reviewers now skim straight past. A case study sticks when it reads like a story instead of a checklist, because people remember narratives, not steps. Give it an arc:
- Problem - what was actually broken (the real user pain, not "redesign the app").
- Constraints - what made it hard: time, budget, tech. Constraints are what make a solution impressive. Uber's team frames work this way - not "we made a map" but "we made a map for drivers in low-connectivity areas on five-year-old phones."
- The pivot - what you tried that didn't work. A scrapped direction builds credibility; it proves you tested assumptions instead of guessing. Spotify openly shows features they built and then killed after user testing.
- The fix - what finally worked, and why.
- Outcome - the result, even if it's a qualitative lesson rather than a metric.
Frameworks help too: Intercom writes case studies around the job-to-be-done - what the user was trying to achieve - instead of a list of features.
The difference is librarian vs. storyteller. A librarian says, "I created a user persona named Sarah." A lead says, "We realized our first persona was wrong - here's the data that forced us to pivot, and how it saved the project." Be the second one.
Show the Thinking Behind the Screens
A beautiful portfolio full of polish and no reasoning is a red flag for experienced reviewers. What they're actually looking for is evidence of a thinking process: did you start with a problem? Did you talk to anyone? Did you change direction when you learned something new?
The goal of a case study isn't to prove you know design - it's to give someone a specific reason to talk to you. Every piece should answer: does this show how I think? Does this give a recruiter something to ask me about in an interview?
Pro tip: Once you've drafted a case study, paste it into an AI assistant and ask it to play a skeptical hiring manager - "what's missing, where does it get vague, what would you ask me?" AI drafts the critique; you decide what's worth fixing.
