What belongs in a design portfolio now that polish is free
By Allan Leone on
The visual quality floor rose sharply and made most portfolios indistinguishable. A beautiful final screen now demonstrates something a model does in a minute. It says almost nothing about the person who made it.
I have been through a lot of portfolios this year. The average visual quality is higher than it was two years ago and the portfolios have become harder to tell apart, which are the same fact stated twice.
The standard structure is a beautiful hero shot, three device mockups at an angle, a colour palette, and a process diagram with four evenly sized boxes. Nowhere in it is any indication of what was difficult.
Why polished outcomes stopped being evidence
A portfolio is a claim about future performance. It works when the artefact is hard to produce without the underlying skill, so the artefact stands in as proof.
That link weakened. A polished screen no longer proves the person can produce polished screens under real constraints, because the same screen can be generated by someone who cannot. The proof has to move to something that did not get cheaper.
What did not get cheaper
- The constraint that made the obvious solution impossible, and what you did about it. Legal, technical, a deadline, an existing system you could not change.
- The version you shipped and then killed. What you saw in the data, how long you left it, what it cost.
- The thing the client asked for that you talked them out of, and the argument that worked.
- What you would do differently, specifically, with a number attached.
All four are records of judgement under pressure. None can be generated, because none of them are visible in the output. They only exist if you were actually there.
The format that carries this
Long case studies with a linear narrative tend not to get read. What works better is one page per project with the constraint stated first, the decision second, the outcome third, and the screens as supporting evidence rather than the headline.
It reads faster and it answers the question the reviewer actually has, which is whether you can be trusted with an ambiguous problem.
Where to start
- Take your strongest project and write the constraint that shaped it in two sentences. If you cannot find one, that project is decoration.
- Add one thing you got wrong to each case study, with what it cost and what you changed. This is the single highest-signal element in a portfolio.
- Move the screens below the reasoning. Let them support the argument instead of being it.
- Start writing decisions down as you make them. Reconstructing them two years later produces a tidy story that is usually false.
Tags: careers, portfolio, design