Every UX portfolio tells the same story. The designer received a brief. They empathized with users. They ran research. They found insights. They sketched, then wireframed, then prototyped, then tested. Iteration happened. The solution emerged, elegant and justified. Results followed. It’s a compelling narrative. It’s also, almost universally, fiction.
Not deliberate fiction — the process happened, the decisions got made, the product shipped. But the clean linear story in the portfolio bears almost no resemblance to what the work actually felt like. The real version had a brief that changed three times. Research that contradicted the direction and got partially ignored. A stakeholder who arrived in week six with a completely different product in their head. Constraints that didn’t exist at the start. Decisions made under time pressure with incomplete information, then reverse-engineered into a rationale that looked like strategy.
Matej Latin, who has reviewed over a thousand design portfolios, puts the observation bluntly: most UX and product design portfolios have two case studies that are the same — it’s just the details that differ slightly. Many case studies read like school homework: the designer knew what the answer and the process were “supposed to be” according to the textbook, so they made up the story to fit [1].
This pattern has a name in performance studies: process theatre. The post-hoc reconstruction of a messy, non-linear reality into a story with a clear beginning, middle, and resolution. The Double Diamond didn’t drive the project — the project drove the project, and the Double Diamond got drawn on the slide afterward because that’s what the format expected.
The problem with process theatre isn’t just dishonesty. It’s that it sets a standard nobody can actually meet — and junior designers in particular spend enormous energy trying to recreate a process that doesn’t exist in practice. If you’re doing a good job, you rarely end up with anything remotely like you anticipated when you started out [1]. That’s not a failure of process. That’s evidence of real work.
Here’s what hiring managers who know what they’re looking at are actually looking for: not the clean version of the work, but evidence that you can think through a problem honestly.
The most interesting thing in a case study isn’t the final design. It’s the moment something went wrong — and what you did about it. The constraint that forced a better solution. The research finding that contradicted the assumption and what changed as a result. The decision you pushed back on and why. The thing you’d do differently.
Those moments don’t fit the template. They’re also the only parts that reveal how a designer actually thinks.
The sanitized portfolio protects you from looking imperfect. It also makes you look like everyone else. And in a hiring environment where the signal-to-noise ratio on portfolios is extremely low, “looks like everyone else” is not a safe position — it’s an invisible one.
The more honest version of a portfolio isn’t a confession. You don’t need to document every chaotic meeting or failed prototype. But you do need to show that real work happened — that decisions were contested, that constraints existed, that something surprised you and you adapted.
That version is harder to write. It requires trusting that an honest account of difficult work is more compelling than a polished account of work that was never difficult.
It almost always is.
References