A strong portfolio doesn’t just show what you made ~ it reveals how you think.

There’s an unspoken pressure in design circles: keep your portfolio shiny, your Dribbble / Behance feed dripping (I have neither I’m such a millenial), your case studies long and keyword-rich. It makes sense. Portfolios get you jobs. They open doors. But somewhere in that race for polish, a lot of us forgot the one thing that makes design truly human: the story behind the pixels.

This post builds on something I touched in Design Systems Are Not Design Shortcuts ~ where I argued that consistency should support creativity, not mute it. Now, let’s talk about the narrative behind the work. Because the industry isn’t short on portfolios. It’s short on designers who can articulate why they made the decisions they did.

Pretty doesn’t mean purposeful

We’ve all seen them. The hyper-clean case studies with flawless grids, impossible timelines, and a parade of happy stick figures. But design isn’t always neat. It’s political. Emotional. Messy. Sometimes it means pushing back against a stakeholder. Other times, it’s making peace with a compromise.

When portfolios skip that story, they lose the plot. They become design theatre. Nice to look at, but hollow underneath. And here’s the thing: good hiring managers can smell that from a mile away. They’re not just looking for skill. They’re looking for depth, awareness, adaptability. Traits you can’t convey through mockups alone.

Your portfolio is not a gallery. It’s a campfire.

A good case study is a conversation. It’s your chance to walk someone through the choices you made, the things that went wrong, the weird constraints you faced, and how you handled them.

What trade-offs did you make?
Where did you push back, and where did you let go?
What did you learn that surprised you?

If your portfolio doesn’t answer these, it’s missing the point.

This isn’t a call to be unprofessional. It’s a call to be real.

No one’s asking you to post Slack screenshots of a design fight or to expose sensitive client drama. But there’s value in transparency. If your design evolved because of technical limitations, say so. If the product launched but didn’t hit KPIs and you pivoted, that’s gold. If you fought to keep accessibility standards in a rush job, highlight it. Those are the moments that show you’re a thoughtful designer, not just a good decorator.

Make the invisible, visible

A lot of the best UX work never gets seen. It’s in the way you handled conflicting feedback, the questions you asked in discovery, the research you did that no one expected. These stories matter. They’re the difference between “I made this UI“ and “Here’s how I helped real people solve a problem under tight constraints.“

So build the structure. Show the interface. But also tell the story.

A reflection on my own shift

This has been part of my own evolution. I used to treat case studies like visual resumes. Stack enough good-looking images and the rest would follow. But that never really felt satisfying. It wasn’t until I started documenting the thought process ~ the mental load, the back-and-forths, the “almost gave up” moments ~ that my work started to feel whole.

You can see that shift in how I structure recent entries like eyeo ~ rebrand 2022 or Platolea by Karakalpakis Family. Both show visuals, yes, but they also reveal the narrative. Why I pushed for illustrations. How I navigated conflicting expectations. What I learned about leading with simplicity.

In closing: skip the fluff, keep the truth

Portfolios should inspire. But they should also inform. If all your work reads like it came from a template, you might be underselling your best asset: you.

So write with clarity. Share what matters. The tough choices, the honest moments, the lessons burned into your process.

Don’t just show the work. Tell the damn story.