What a Portfolio Is Actually For

D&AD publishes the criteria its juries apply, in order of importance. First, "an original and inspiring idea". Second, "exceptionally well executed". Third, "relevant to its context". That is the whole list, and it is applied by more than three hundred judges across forty-six categories. Nowhere in it does the word "designer" appear.

That is not an oversight. An awards jury is looking at a thing on a table. It cannot see who fought for the idea, who lost the argument about the typeface, who noticed on the Thursday before print that the client's legal team had changed the copy. D&AD's own judging rules go further and remove the person deliberately: judges must abstain when they have worked on an entry, represent the submitting agency, or have worked there within the past year. The system is built to evaluate artefacts with the people scrubbed out.

A portfolio is assembled the same way, out of the same material, in the same order. And then it is handed to someone whose job is precisely the opposite: to work out what a specific person will do next, on a brief nobody has written yet, under constraints nobody can describe in advance. This is the mismatch, and most portfolio advice makes it worse rather than better.

Two kinds of judgement, one artefact

It helps to separate the two evaluations cleanly, because they look alike and are not.

The iF DESIGN AWARD publishes a longer criteria list than D&AD's: Task ("Is the task achieved?"), Relevance, Fit for purpose ("Is the idea appropriate?"), Aesthetics ("Why does it look the way it does?"), Emotional appeal, Execution ("How is it made?"), Usability, Efficiency, User Benefit, Innovation, Brand Differentiation, Effect ("Have targets been reached?"), Social Benefit and Sustainability. Judging runs in two stages: an online preselection using scorecards, with roughly the top half advancing, then an in-person jury meeting where jurors combine the scorecard results with their own reading.

Two of those fourteen criteria are genuinely about outcome rather than object. "Is the task achieved?" and "Have targets been reached?" ask what happened after the work shipped. The other twelve ask about the object. Even the outcome pair asks about the object's effect, not the designer's contribution to it.

That is the right design for an award. Awards are an evaluation of work. Hiring is an evaluation of a person's future work, which is a forecasting problem, and forecasting requires evidence about the process that produced the sample, not just the sample. A studio that hires from a portfolio alone is doing the equivalent of buying a factory on the strength of one finished part.

The artefact is the output of a function. A studio is not buying the output. It is buying the function.

What the professional guidance actually asks for

Here is the thing that surprised me. The professional body's guidance is already much closer to the forecasting problem than the awards criteria are, and much closer than most published portfolio advice.

AIGA's portfolio review checklist organises what a reviewer should find under four headings, and only one of them is about finished work. It asks for the brief and its context: the communication need, the audience, the required applications and constraints, who owned the decision, and where the candidate's role began and ended. It asks for working artefacts, listed as "Briefs, concepts, type and layout systems, proofs, revisions, and final production files". It asks for evidence of process, meaning design rationale paired with visible results, and documented alternatives "only when showing real decisions". And it asks for collaboration documentation: "Who wrote the brief, who developed concepts, who selected a direction, who produced the applications".

The reviewer's side of the checklist is equally specific. Reviewers are pointed at three levels: whether the brief was covered, whether the system behaves consistently across applications, and whether production was handled properly, including handoff and accessibility review.

The companion guide for early-career designers puts the case-study shape in one sentence: "A useful case study for this subject can open with the context and brief, then show the constraints that shaped the work." It gives a rule for how much to show that I think is the single best line in the whole literature: "Select the smallest set of working artifacts that makes the decision legible, and explain the designer's role beside each one." And it gives a rule for how the projects should relate to each other: each project should "add evidence the previous case did not".

The interview guidance is where it gets sharpest. It tells candidates to open each case by naming "the communication need, audience, constraints, your role, and the collaborators who shaped the outcome", then to "spend the most time on decisions the reviewer can see". For each element: "State what the element needed to do, which constraint influenced it, what option was selected, and how the team reviewed it." And where a result is claimed: "If an outcome can be supported by project records, name the measure and its source."

It also names the failure mode directly, in three words that should be printed on the inside of every portfolio template:

Process theater adds volume without showing why a choice changed.

What nobody can tell you, including AIGA

I went looking for evidence. Not advice: evidence. Studies of how reliably reviewers score the same portfolio, how well a portfolio score predicts on-the-job performance, how long a reviewer actually spends on a case study, whether showing process improves or harms a candidate's chances. I did not find any I could read in full and cite honestly. What exists in public is guidance written by practitioners, some of it very good, none of it measured.

AIGA is admirably blunt about this. Its own guide states: "There is no single mandatory portfolio format, project count, page count, platform, or case-study length in the verified source set." A professional body telling you there is no verified answer to the most commonly asked question in the field is more useful than a confident number would be.

The UK's Quality Assurance Agency describes what art and design graduates should be able to do in its Subject Benchmark Statement for Art and Design, and the language is all verbs: graduates should be able to "conceive, experiment, create and disseminate processes and outcomes that shape visual and material culture", combining "research, imagination, analysis, synthesis, making, practice and communication". Note that outcomes appear once, in a list where they are outnumbered five to one by activities. The accreditation standard describes a capability. The portfolio, as usually built, describes a product catalogue.

So the field's own standards, its professional body's guidance, and its awards criteria are pulling in two different directions, and nobody has measured which pull is right. That is the actual state of knowledge, and anyone who tells you otherwise is selling a template.

What I got wrong for about six years

I built case studies in the standard three-act shape: the problem, the process, the solution. Problem stated in a paragraph. Process shown as a grid of sketches, mood boards and rejected logos. Solution shown big, on a phone, on a billboard, at dusk.

Every one of those case studies was a lie of omission, and the lie was in act two. The sketches were real. They were also chosen after the fact, from a much larger and messier pile, to make the final answer look inevitable. Nobody looking at them could tell which of those sketches I had actually believed in, which one a client killed, which one I killed because it would have taken three more weeks. The grid of alternatives proved that alternatives existed. It proved nothing about how I chose between them, which is the only thing a studio cares about.

AIGA's phrase for it is process theatre. It took me an embarrassingly long time to notice that the more process I showed, the less a reviewer could tell about my judgement, because the volume buried the two or three moments where a real decision was made.

What a case study should contain

Here is the argument, concretely. A case study is not a narrative of how the work was made. It is a set of exhibits, each of which is evidence for a specific claim about the designer, and each of which could in principle be falsified. If an exhibit cannot be wrong, it is decoration.

The organising question is: what decision does this exhibit let a reviewer second-guess? If a reviewer cannot disagree with you about it, it proves nothing, because agreement is free.

The last row is the one people resist and the one that does the most work. Every real design decision costs something. A case study that reports no cost is reporting a decision that was not a decision.

A practical test you can run on your own portfolio in about twenty minutes:

For each project in the portfolio, answer in one line each:

  1. What was fixed before I started?
     (budget, deadline, legal, platform)
  2. What did I change about the brief?
     (if nothing, say nothing)
  3. Name one option I killed, and the reason.
  4. Name one thing that got worse as a result.
  5. Who else decided something here?
  6. What would I do differently, and what evidence
     changed my mind?

Scoring:

  Cannot answer 3 or 4      ->  the project is a portfolio piece,
                                not a case study
  Answer to 5 is "nobody"   ->  either a student project or an
                                unreliable narrator
  Answer to 6 is "nothing"  ->  six years have passed and nothing
                                was learned

For each project in the portfolio, answer in one line each:

  1. What was fixed before I started?
     (budget, deadline, legal, platform)
  2. What did I change about the brief?
     (if nothing, say nothing)
  3. Name one option I killed, and the reason.
  4. Name one thing that got worse as a result.
  5. Who else decided something here?
  6. What would I do differently, and what evidence
     changed my mind?

Scoring:

  Cannot answer 3 or 4      ->  the project is a portfolio piece,
                                not a case study
  Answer to 5 is "nobody"   ->  either a student project or an
                                unreliable narrator
  Answer to 6 is "nothing"  ->  six years have passed and nothing
                                was learned

For each project in the portfolio, answer in one line each:

  1. What was fixed before I started?
     (budget, deadline, legal, platform)
  2. What did I change about the brief?
     (if nothing, say nothing)
  3. Name one option I killed, and the reason.
  4. Name one thing that got worse as a result.
  5. Who else decided something here?
  6. What would I do differently, and what evidence
     changed my mind?

Scoring:

  Cannot answer 3 or 4      ->  the project is a portfolio piece,
                                not a case study
  Answer to 5 is "nobody"   ->  either a student project or an
                                unreliable narrator
  Answer to 6 is "nothing"  ->  six years have passed and nothing
                                was learned

Three or four projects that survive this are worth more than twelve that do not, which is roughly what AIGA means by each project adding evidence the previous one did not.

What this means for the reviewer

The obligation runs both ways, and studios are worse at this than candidates are.

If you are reviewing, you are not judging the work. D&AD judges the work, with a jury of three hundred and a five-round voting structure and explicit conflict-of-interest abstentions, because that is what it takes to judge work fairly. You have a single meeting and one person's account of the work. You are not equipped to do what a jury does, and attempting it produces the familiar bad outcome: hiring the candidate with the best-resourced projects, which usually means the candidate who has already worked somewhere good.

What you are equipped to do is interrogate a decision. Pick one element from one project, ask what it needed to do, ask which constraint shaped it, ask what else was considered, and ask what it cost. AIGA's guidance for candidates is, read from the other side, a list of questions reviewers should be asking: what the element needed to do, which constraint influenced it, what option was selected, and how the team reviewed it. A candidate who can answer that about a mediocre student project is a better hire than one who cannot answer it about an award winner.

The narrow conclusion

Portfolios are not going away, and they should not. They are the fastest way to establish that someone can make a thing at all, which is a real threshold and a lot of people do not clear it.

But the portfolio answers only the first question. It says: this person has produced work of roughly this standard, under conditions I cannot see. The second question, the one the studio actually needs answered, is: what will this person do when the budget halves, the client changes their mind, and the obvious answer is unavailable? No artefact answers that. Only an account of a decision, with its cost attached, comes close.

And to be clear about the limits of my own claim: I cannot show you evidence that portfolios built this way get more people hired. Nobody can, because as far as I can establish nobody has measured it. What I can say is that the professional body's published guidance, the accreditation language for design education, and the awards criteria are three documents describing three different objects, and only one of those three is trying to describe a designer.

Sources

• D&AD, "D&AD Awards judging process", dandad.org; the three criteria in order of importance, the five judging rounds, Pencil levels, the 50 per cent vote thresholds and the conflict-of-interest abstention rules.

• D&AD, "D&AD Awards", dandad.org; scale of the 2026 awards, 46 categories, over 300 judges across eight disciplines. www.dandad.org/en/d-ad-awards/

• iF International Forum Design, "iF DESIGN AWARD", ifdesign.com; the published evaluation criteria and the two-stage preselection and jury process.

• AIGA Career Resource Center, "Graphic Design Portfolio Review Checklist", designcareers.aiga.org; the four categories of portfolio content and the three levels of reviewer assessment. designcareers.aiga.org/career-resources/portfolio-13/graphic-design-portfolio-review-checklist-2026-137

• AIGA Career Resource Center, "Graphic Design Portfolio Guide for Early-Career Designers", designcareers.aiga.org; the case-study opening, the smallest-set-of-artefacts rule, the added-evidence rule, and the statement that no mandatory format or project count exists in the verified source set. designcareers.aiga.org/career-resources/portfolio-13/graphic-design-portfolio-guide-for-early-career-designers-2026-138

• AIGA Career Resource Center, "Graphic Design Portfolio Presentation for Interviews", designcareers.aiga.org; the rehearsed opening, the rationale-per-element formula, the instruction to name a measure and its source, and the phrase "Process theater adds volume without showing why a choice changed." designcareers.aiga.org/career-resources/portfolio-13/graphic-design-portfolio-presentation-for-interviews-2026-136

• Quality Assurance Agency for Higher Education, Subject Benchmark Statement: Art and Design (2026 edition), QAA. www.qaa.ac.uk/the-quality-code/subject-benchmark-statements/subject-benchmark-statement--art-and-design

Related reading

• Pricing Creative Work

• The Helvetica and Arial Question, Settled Properly

• Arguing With a Talk

• How Studios Lose Their Own Work

More from the Moc Mallen Studio journal