01Portfolio review #1
How the desk reads a creative-lead portfolio.
A walk through one representative submission — the kind of portfolio a senior art director or design lead sends when they're ready for the next role. The desk reads it the same way it briefs a search: against the decisions the work was made from, not the polish of the artefacts.
02What the desk looks for
Briefed against the decisions, not the polish.
A creative-lead portfolio answers three questions, in this order. Who decided the brief was worth shipping. What they changed in the work because they owned it. And what the room looked like when the work landed. The desk reads the answers in this order because they signal whether the candidate ran the project or simply shipped it.
Most submissions lead with the artefact — the campaign film, the identity system, the launch deck. The desk reads those too, but in service of the three answers above, not the other way around. A polished artefact with no decisions behind it reads as a collaborator; a less-polished one with clear decisions reads as a candidate the desk would surface.
The same reading frame is applied to the resume service the desk runs end-to-end — the resume tells the same three answers in text form, the portfolio tells them in artefact form. Candidates preparing for an ECD search send both.
03NDA-safe redaction
Show the decision, mask the artefact if the brief was confidential.
A working portfolio almost always includes work the candidate cannot publish in full. The desk expects that. What it does not accept is a black box where a decision should sit. The rule: redact the artefact, never the decision.
Concretely: a confidential client name becomes "a category-defining DTC brand"; a confidential category becomes "a regulated consumer vertical". The role you played, the constraints you navigated, and the call you made on the brief are all fair game — those are what the desk reads. The artefact itself, when it cannot be published, becomes a thumbnail with the decision written around it in two sentences.
For candidates who would rather hand the redaction off entirely, the resume service writes the portfolio narrative end-to-end — same NDA-safe frame, run by the desk that reads hundreds of these a quarter.
04An annotated walkthrough
One representative portfolio, three takedowns.
The submission below is anonymised — the candidate is real, the work is loosely drawn from a portfolio the desk actually surfaced for a recent ECD search, and the annotations are the ones a senior recruiter would put in the internal shortlist note.
Takedown #1 — the cover image. The portfolio opens on the campaign still from the candidate's highest-budget project — a four-frame hero, beautifully shot, typographically tight. The desk rates the artefact, but the annotation against it is "polish only — insufficient." A reader can't tell from the hero who decided the brief was worth shipping.
Takedown #2 — the case-study opener. The second frame is a one-paragraph case-study opener, written by the candidate, stating the brief and the role. This is where the portfolio starts to read — the desk annotates "clear ownership, brief is real, role is bounded." Candidates who can write a one-paragraph case opener ship half the desk's work for them.
Takedown #3 — the constraints section. Halfway through the same case study, a short "constraints" block names the budget cap, the timeline, the two teams the candidate negotiated with, and one decision the candidate made against pushback. The desk annotates "decision-led, willing to take a position." This is the section that moves a portfolio from candidate to shortlist.
ClosingIf this read sounded like you
Open a candidate file — the desk reads it the same way.
The same three questions apply to the candidate intake — who decided, what changed, what did the room look like. The desk reads every submission within two business days and writes back whether the timing fits the current brief list.
Next in the series
Portfolio review #2 — a front-end engineering portfolio.
The next entry in the series walks a representative front-end engineering portfolio through the same three-question frame, with the system-design section treated the way the desk reads it: as the artefact, not the story.
Filed back into the resource index when it ships.