Every UX portfolio tells the same story. Brief, empathy, research, insights, sketches, wireframes, prototype, testing, a bit of iteration, and then a beautiful solution with results attached.
It’s a lovely story. It almost never happened like that.
In the real project, the brief changed a few times and the research contradicted the direction and got half ignored. Someone senior showed up in week six with a different product in their head. Decisions got made under pressure and were explained afterwards as if they’d been strategy all along.
Matej Latin, who has reviewed more than a thousand portfolios, says most case studies read like school homework. The designer knew what the process was supposed to look like and wrote the story to match.
I don’t blame anyone for doing it, because the format practically asks you to. But it causes real damage. Junior designers try to copy a process that doesn’t exist and feel like they’re failing. And everyone ends up looking the same, which, to a hiring manager going through a pile of portfolios, means invisible.
The most interesting part of any case study is the moment something went wrong and what you did about it. So is the decision you pushed back on, and why. Those don’t fit the template, and they’re the only parts that show how a designer actually thinks.
Which line would a hiring manager remember?
The momentThe brief changed halfway through.
Illustrative example
You don’t need to confess every chaotic meeting. You just need to show that real work happened, that people disagreed and something surprised you. My Scaler case study opens with me realising part of the mess was my fault. I’d take that over a tidy process diagram any day.
References