I got this message last week:

“I have been struggling a lot recently with trying to get my portfolio and resume updated (…) I don't feel like I have the proof to put in my portfolio to show that I know design. I'm just feeling stuck and incredibly unhappy"

It’s not the first time I’m hearing this from a designer whose work doesn’t fit the standard portfolio narrative. But here’s what’s bigger than this one message: the rules of what counts as proof in a design portfolio are changing for everyone. Let me share what I’m seeing, and what to do about it.

Context

For years, the design portfolio formula was simple: show high-quality screens, flows, wireframes, the polish. The artefact was the proof.

That formula is breaking now more clearly than ever before.

Design ops, design leadership, research-heavy roles, requirements work, facilitation, strategy. All of it is design, but none of it produces a hi-fi mockup at the end. Designers in these roles look at the standard portfolio template and find no place to put what they actually do.

Every role can generate a clean-looking screen now, not just designers. PMs are mocking up flows in Figma Make, engineers are spinning up UI in v0, and founders are prototyping in Framer. The artefact alone no longer signals design skill, it can signal access to a tool.

So the question is changing from “what visual work do I have to show?” to “what proves my decisions and how I shaped directions?”

Awareness

If the artefact isn’t the proof, the proof has to come from somewhere else. It comes from the decisions visible in the work, the influence you had on the outcome, and the way you articulate why.

Decisions you made

Influence you had

How you articulate the work

Try this:

Open a blank doc and write what you actually do day to day, without using the words designed, wireframe, mockup, screen, flow, or workshop. What’s left is your real function: deciding, directing, shaping, scoping. That’s your starting point for everything below.

Articulation

Design without making the final pixels.

Once you can see the work for what it is, the next step is putting it on the page. Start with the most underused story frame in design portfolios: the director

Art directors decide what gets made, set the standard, and direct the people who execute. Their portfolio is the work they shaped, not the work they personally drew.

But they also make things like mood boards, sketches, quick prototypes to show what good looks like. The difference is what those artefacts are for.

If you’ve been writing requirements, setting the quality bar on someone else’s work, sketching a rough version to align the team, or killing the wrong direction in a review, that’s direction. That’s the job.

The same goes for early-career designers in startups. You decided what to cut from v1, chose which pattern to copy and which to invent, shipped first because there was no PM to tell you what to do. That’s direction too.

Try this:

List 5 decisions you made in the last year that shaped what got built, even if you didn’t make the final pixels. For each one, write down what you chose, what you rejected, and why. Pick the strongest 2 and turn them into short case studies. Lead each one with the decision, not the deliverable.

Articulation

Solo work is the cleanest proof of judgment because there’s nobody else to credit.

You don’t have to be freelance to claim it, because side projects count, the project nobody scoped, the system you built because someone had to or the pro bono client where you ran the whole thing.

Early-career designers at startups have often been operating solo the whole time. One designer, no design team, no manager who can review the work. Every decision was yours.

If it shipped, you shipped it. If it worked, you made it work. If it didn’t, you learned and adjusted.

Try this:

Make a list of every project where you were the only person responsible for the outcome. Pick the 2 with the clearest before and after. Write a one-paragraph case study for each, focused on the decision, not the deliverable. Include what would have happened if you hadn’t made that call.

Articulation

Call it your one-liner, your intro pitch, your positioning. The line at the top of your portfolio that tells the recruiter who you are and what you do, in one breath.

If your work doesn’t fit the standard portfolio narrative, the worst thing you can do is hide it. Hiring managers will notice anyway. Naming it directly does the opposite. It signals self-awareness, control of your story, and a point of view.

The gap stops being a gap the moment you name it.

Try this:

Draft 3 versions of your one-liner. Each one names your actual function (what you do) and your actual context (where and for whom), in 15 words or less. Pick the one that sounds most like you and put it above the fold.

Every tactic in this issue does 1 of 2 things. It builds your awareness of the work you’ve already done, or it sharpens how you articulate it. Most portfolios get stuck on 1 of those 2, not on the work itself.

If you’ve been doing the upstream version of design (directing, deciding, scoping, killing, choosing), you’ve been building proof the whole time. It just doesn’t look like a Figma file. Your job now is to see it, name it, and put it on the page.

So here’s my question for you this week: what part of your work have you been dismissing because it doesn’t look like a visual design?

Tools I actually use in my workflow. Some links support this newsletter.