On the work you do not show

Most portfolios tell a story of arrival. The brief. The process. The final outcome. A clean arc from problem to solution, documented with care and presented with confidence. It looks like competence. It is supposed to.

But the work that actually shapes a designer happens largely off the page.

The directions were explored and abandoned. The version that almost worked but did not, for reasons that were difficult to articulate at the time. The decision was made under pressure that turned out to be right for the wrong reasons or wrong in ways that only became clear months later. The feedback stung because it was accurate.

None of this appears in the portfolio. And yet it is the substance of the practice.

I think about this often when reviewing student work, not just what is being shown, but what the choices reveal about what was considered and set aside. A designer who has only ever moved in straight lines toward a solution is not more capable. They are less tested. The ability to recover from a wrong direction, to recognise one early enough to change course without losing the thread entirely, is one of the most important things a design education can develop.

It does not photograph well. This is not an argument against portfolios. It is an argument for what sits behind them. The most interesting design conversations I have had are never about the finished work. They are about the moment before the decision that produced it, what else was on the table, what was given up, and what the constraint was that nobody put in the brief.

That conversation requires a designer who has thought carefully about their own process. Not just what they made, but how they got there, and what it cost. The work you do not show is where your thinking actually lives. Show it, at least in conversation.