the portfolio problem

i’ve reviewed a lot of design portfolios over the years. hiring for my team, helping people i mentored, occasionally just when someone asked. and there’s a pattern i keep seeing in the ones that don’t land.

they’re full of work. good-looking work, often. but they leave you with no idea of how the person thinks.

you see: a clean figma prototype. a before/after of a redesigned screen. a row of polished mockups. what you don’t see: what problem was actually being solved. what options were considered and why this one was chosen. what the constraints were. what the designer was uncertain about.

a portfolio that’s just output is a portfolio that could have been made by anyone. maybe by AI. the thing that can’t be replicated is the decision-making — what you chose and why, under real conditions, with real constraints.

the designers whose portfolios i remember are the ones who narrated the problem before they showed the solution.

not a long narrative. not a process section with 40 slides of sticky notes. just: here’s what was broken and why, here’s the constraint that made it hard, here’s the call i made and what i was trading off. two paragraphs. then the work.

that context changes everything. suddenly the decisions become visible. you can evaluate them. you can agree or push back. you get a sense of how this person thinks under pressure, not just what they can produce with unlimited time.

the portfolios without that context leave me doing guesswork. which means i’m not evaluating the designer, i’m evaluating the output. and if the output is polished — and most portfolio output is — it’s very hard to tell the difference between thoughtful and lucky.

there’s a specific thing i watch for in portfolio case studies. it’s the moment the designer describes a decision they made that they weren’t sure about.

not failure theatre. not the “we had challenges and learned from them” section that’s clearly been added because someone said it was important. i mean: a moment where the designer says “we went with option B, not because it was obviously better, but because X outweighed Y in this context, and we weren’t sure it would work until we tested it.”

that sentence tells me more than any final mockup. it tells me this person can hold uncertainty, make a call anyway, and articulate their reasoning without inflating it into a clean story.

most portfolios don’t have that sentence because it feels like it undermines confidence. it doesn’t. it signals the opposite — someone who understands their own process well enough to describe it honestly.

the other thing portfolios get wrong is scope.

designers often pick their biggest project. the one that ran for 18 months and involved 12 stakeholders and five rounds of testing. they think scale communicates seniority.

what it usually communicates is complexity. and complexity is hard to narrate in a portfolio. by the time you’ve explained all the context, you’re out of space for the thinking.

a smaller project, narrated with precision, shows more. a two-week design sprint where you made a hard call and it worked — or didn’t work, and here’s what you learned — does more work than a sprawling case study where the decision logic gets lost in the timeline.

pick the one that has a clear argument. the one where you can say: here’s the problem, here’s the decision, here’s why. three paragraphs and three screens beats twenty screens with no narration.

if you’re looking at your portfolio and it feels like it’s not working — not getting responses, getting generic feedback, not landing interviews you think you should — it’s usually not the work. it’s the framing.

the work you’ve made is probably fine. what’s missing is the decision logic that makes it yours.

if you’d like someone to look at your portfolio with that lens — not aesthetic notes, but an analysis of whether the decision-making is legible — i offer structured design critique. $75.