A portfolio used to be self-evidencing: if the work was on your site, you had made it. That assumption is gone. A hiring manager opening a design process portfolio in 2026 knows that a polished mockup can be generated in a minute and that a grid of final screens proves almost nothing about who did what.
They are right to doubt. The gallery portfolio, twelve hero shots and a contact form, asks the viewer to take it on trust. The process portfolio shows the brief, the dead ends, the decision and the result, and lets the viewer check. It is also the best reply you have to the client who wants a free concept before they sign.
The short answer. Make every case study carry its own evidence: the brief, the constraint, the directions you discarded and why, the decision, the before and after, an honest outcome, and a short provenance line naming tools, collaborators and anything generated. Source the process shots from version history, sketchbooks and annotated iterations, and keep the originals.
Why the gallery portfolio stopped working
The viewer's problem is verification, and a gallery gives them nothing to verify. Hiring managers have seen agency work a candidate touched for a week, and screens from a prompt-to-mockup tool presented as a shipped product. The fake is now cheaper than the real thing and identical at thumbnail size.
Clients have the same doubt. The AIGA position on spec work says the value of design lives in the research, the alternatives considered and the prototypes tested. A gallery hides exactly that part, which is partly why clients ask for a comp: they cannot see your process, so they ask you to perform it free.
| What the viewer wants to know | Gallery portfolio | Process portfolio |
|---|---|---|
| Did this person make the work? | Cannot tell | Dated version states, sketches, a provenance line naming the role |
| Was there a real client and brief? | Assumed | Quoted constraint, redacted brief excerpt, client feedback |
| Can they make decisions, or only renders? | Cannot tell | Discarded directions with reasons, the decision stated plainly |
| What did the work achieve? | A hero shot | Before and after, a sourced number or an honest non-number |
| What was generated? | Silent | Declared per case study, tools and collaborators named |
| What would I get if I hired them? | A guess | The visible working method, which is the thing being bought |
What a design process portfolio shows per case study
A process case study answers six questions, each of which a viewer could check.
The brief and the constraint
One paragraph on what the client asked for, and one on the constraint that made it hard: the budget, the deadline, the legacy system, the founder who wanted purple. Generated case studies tend to have no constraints, because nobody generated a difficult client alongside the mockup.
The discarded directions
Show at least one direction you did not take, and say why. This is the hardest thing to fake, because a rejected direction has to be plausible and wrong at the same time.
The decision and the reason
State both in plain words. "We moved onboarding to after the first task because drop-off at the sign-up wall was high" is a sentence a viewer believes. "We crafted a delightful onboarding experience" is not.
The before and after
Where there was a before, show it, unflattering as it may be. The distance between the two states is your contribution made visible. On a greenfield project, the "before" is the earliest artefact you have.
The outcome, with a number where honest
If you have a number, give it and say where it came from: "checkout tickets fell by a third in the month after launch, per the client's helpdesk report" (a hypothetical, to show the form). If you do not have one, do not invent one; "the client did not ship it", with the reason, is a legitimate outcome.
The provenance line
A short block at the foot of the case study:
Role: lead designer; research and UI mine, illustration by a named collaborator. Tools: Figma, Illustrator, Procreate. Generated material: none in the shipped work; an image generator made two placeholder textures in round one, both replaced before delivery. Dates: brief 4 March, handover 22 May.
Use it on every case study, including the ones where generated material is none. It only carries weight if it is always there.
Where the process shots come from
Most of the material already exists.
- Version history exports. Figma keeps a timestamped record of every save; the help page on viewing a file's version history explains what each plan retains. The piece on version history as the design record covers the Adobe equivalent and the retention traps.
- Sketchbook scans and whiteboard photos. Phone photographs are fine. Date them in the caption. Eight bad thumbnails are worth more to a hiring manager than one polished render.
- Annotated iterations. Take the round-two export, draw on it, and say what changed and why.
- The paper trail. A redacted line from the brief, the client's feedback on round one.
Keep the originals. The portfolio shows the excerpt; the native file, the full history and the correspondence sit in the folder described in how to prove a design is yours.
NDA work and generated work, handled honestly
Work under a non-disclosure agreement can usually show process without showing the product. Describe the brief in category terms ("a regulated lender's onboarding flow"), show the discarded directions with identifying marks removed, show one annotated iteration with the copy replaced, and state the outcome without naming the client. Check the NDA first; some forbid even category descriptions, and then the study stays off the site.
Work made with generative tools follows the same rule as contracts: disclose it, precisely, and do not apologise. If a language model drafted microcopy you then edited, say how much survived. The U.S. Copyright Office's 2023 registration guidance requires applicants to disclose generated material and describe the human contribution, a useful discipline even without a registration. A portfolio that can name what was generated is also evidence that the rest was not. The AI disclosure clause article covers the contract version; the AI and the Designer pillar covers pricing it. Do not quietly drop the generated pieces and present the remainder as the whole.
The process portfolio is the answer to the spec request
When a client asks for a free concept, they are asking for evidence that you can do the job. A process portfolio shows the brief, the alternatives, the decision and the result on a project that was paid for, which is what a comp would show on one that is not. So the reply to "can you put together a couple of directions so we can see your thinking?" is a link:
Glad to. I do not produce new concepts before a project is agreed, but the case study at the link shows the brief, the directions I rejected and why, and where the project landed. If that is the kind of thinking you want, the first paid phase is a discovery workshop, and the fee credits toward the project.
Send it when the request is friendly. If they push for a comp anyway, the what spec work is page has the firmer scripts and the spec value calculator puts a number on the ask. AI mockups as the new unpaid pitch covers the version that arrives with a generated draft attached.
Case study page checklist
- Brief in one paragraph, with the real constraint named
- At least one discarded direction, with the reason it lost
- The decision, stated plainly, with the reason
- Before and after, or earliest artefact and final
- Outcome with a sourced number, or an honest outcome without one
- Two or more dated process shots
- Provenance line: role, collaborators, tools, generated material, dates
- Originals kept offline: native file, version history, correspondence
Frequently asked questions
What if I have no process material for older work?
Say so. A note that the project predates your current record-keeping is more credible than a case study padded with reconstructed sketches. Show what you have and document new work properly. One well-evidenced recent study outweighs six thin older ones.
Should I say a project used generative tools if the client did not?
Yes, if your name is on the case study. The disclosure is about your process rather than the client's marketing. Keep it specific: which stage, which kind of tool, what was replaced by hand. If the contract restricts what you can say, treat the study like NDA work.
Can I show work I did as an employee or at an agency?
Usually, with the role stated accurately. "Lead designer on the checkout flow, one of four designers on the product" is fine. "Designed the app" when you were one of four is the claim that ends interviews. Check your employment agreement for portfolio-use terms and strip anything confidential.
Does a process portfolio replace Content Credentials or version history?
No. It is the public, readable layer on top of them. Content Credentials travel with the exported file, version history sits in the tool, and the portfolio is the narrative a person reads. The article on Content Credentials for designers explains what the file-level record proves.
What to do this week
Pick the project you are proudest of and rebuild its page as a design process portfolio entry using the checklist above. Then confirm the native file and version history still exist. That is one afternoon, and it makes the rest of the site believable.
Do the same for each new project on the day it ships. The Proof of Work hub holds the rest of the lane; start with the provenance stack for a disputed design if the originals folder does not exist yet.