Businesses do not hire practitioners to get more options; they hire them to get fewer, better ones. This chapter is about the judgment part of the craft: narrowing the options, letting the decider see the reasons, and keeping the presentation a place to defend a decision rather than a place to look for one. Judgment here is not taste spoken loudly; it is a choice with an owner and with reasons that can be checked.
Quick read: the core statement, when it comes up, and the test to take home. Full read also opens the reasoning, the limits and the sources. Each principle comes before its practices, so the numbers do not run in sequence.
A brand problem is a decision problem; the designer's first job is to narrow the options for whoever has to decide.
When it comes upWhen preparing to present options, when the client asks to see a great many directions, and when the design team wants to bring everything it has made to the table.
Resolution
Wide in the studio, narrow at the presentation table. The practitioner must explore many directions and show the client that they did (5.04), but put on the table only options they are willing to put their name to. A direction is a path explored in the studio; an option is what reaches the presentation table.
Full reasoning
Two goods pulling against each other
Showing many options makes clients feel respected, involved, not imposed upon; and sometimes the unexpected option is the right one. Showing few lets the decider focus on the question that actually needs answering.
Why it holds
Many equal options with none recommended push the burden of deciding onto the person in the room with the least design experience. When criteria are unclear, people choose by the taste of the moment, by whoever speaks loudest, or by combining: the colour of one option, the lettering of another, producing something no option intended. The presenter cannot stay outside either: they choose which options reach the table, which comes first, which stands next to which, so even without admitting it they have already decided part of it. Narrowing openly means accepting that responsibility and putting a name to it (0.3). Research on the decoy effect shows that adding a clearly inferior option can pull choosers towards the option beside it; but the effect is clear for options described by numbers and much weaker for visual options (Frederick et al. 2014), and design options are visual. The familiar finding that more choice makes deciding harder gave inconsistent results when researchers repeated it. This principle relies on neither.
When it fails
In the discovery stage, when there are no criteria yet, laying out many rough directions such as mood boards or sketches for the client to react to is a way of finding criteria, and does not contradict this principle. When the contract specifies the number of options to present, keep to that number; narrowing then means saying clearly which option is recommended and why, not withholding promised options. Clients with their own design team can be shown more.
What it costs
Clients sometimes feel they have less choice; the practitioner must answer in front of the client when the recommended option is wrong; much finished work has to stay in the studio.
Sources
Joel Huber, John W. Payne and Christopher Puto, Adding Asymmetrically Dominated Alternatives: Violations of Regularity and the Similarity Hypothesis, Journal of Consumer Research, 1982
Benjamin Scheibehenne, Rainer Greifeneder and Peter M. Todd, Can There Ever Be Too Many Options? A Meta-Analytic Review of Choice Overload, Journal of Consumer Research, 2010
Shane Frederick, Leonard Lee and Ernest Baskin, The Limits of Attraction, Journal of Marketing Research, 2014
Present the directions rejected in the studio and the reason for rejecting each, so the client sees the choice was narrowed, not that options were missed.
When it comes upWhen preparing presentation materials, especially for clients who are used to seeing a lot.
A test to take home
(1) Before the presentation, list every direction tried, including sketches abandoned halfway. (2) For each rejected direction write one line in three parts: what the direction was, which criterion it failed (using exactly the criteria the decider confirmed, 3.05), and what it had going for it. The third part is mandatory: rejecting a direction without naming any strength is rejecting for convenience, not with judgment. (3) Present the recommended option first, then turn to the page of rejected directions at thumbnail size, enough to see, not enough to choose. The number of options specified in the contract is still presented in full, at full size; only directions rejected in the studio are shown small. (4) File that table in the project records, next to the design rationale in the handover set, so the future standards keeper can read both what was chosen and what was dropped. Pass: when the client asks why not try that style, the answer is already on the table. Fail: the client picks a rejected direction again without any new criterion to justify it, meaning the table was not trusted or the criteria were wrong.
Record each fork the moment it happens: what was chosen, what was dropped, by which criterion, who decided, on what date.
When it comes upEvery time the project changes direction or drops a direction, whether in a meeting or by a message.
A test to take home
(1) One fork log per project, each line with five fields: date, chosen, dropped, reason by criterion, decider. (2) Record it the same day, not at the end of the project; a message like ok let's go with direction two is also a fork. Recorded late, memory rebuilds the reason around the known outcome, so a log written afterwards differs from one written at the time. (3) Send the new line to the decider to confirm with a word. (4) Reread the log three months later. Pass: someone new to the project reads the log and can explain why the design is what it is today. Fail: when an argument arises over who asked for this, you have to dig through messages; or the reason field says the same thing on every line.
Sources
Sources
Baruch Fischhoff, Hindsight ≠ foresight: The effect of outcome knowledge on judgment under uncertainty, Journal of Experimental Psychology: Human Perception and Performance, 1975
When the client asks for more options, ask which problem the new option must solve that the existing ones do not.
When it comes upAfter a presentation, when the client says do a few more directions just to be sure.
A test to take home
(1) Do not answer yes or no at once. Ask: what must the new option achieve that the existing ones cannot? (2) If the answer attaches to an agreed criterion, the fault lies in the existing option; revise that option against that criterion, no new option needed. (3) If the answer is a new criterion not in the brief: record the fork (5.07), confirm the new criterion with the decider, then work; if it exceeds the number of options in the agreed scope, state the extra work before doing it. (4) If the answer is just to be sure, or to compare: that is not a problem but a decider who does not yet trust enough; go back and score against the criteria (5.05), or find the real decider (3.02). Pass: every extra option has a line stating which problem it solves. Fail: a fifth option appears and nobody can say on which criterion it differs from the third.
Judgment can only be sold when its reasons are visible; hide the reasons and all that is left to sell is the designer's taste.
When it comes upWhen writing the rationale for an option, and when the client asks why this colour, why this lettering.
Resolution
Show first, give reasons afterwards; and give reasons at the level of the decision (why this direction, what it costs), not at the level of every stroke.
Full reasoning
Two goods pulling against each other
Keeping the reasons private lets the design speak for itself; long explanations spoil the first impression and open the door to arguing over every detail. Showing the reasons gives the decider something to defend the choice with in front of others.
Why it holds
The decider is rarely the only person who has to be convinced; they must also carry the design back to a board, a family or partners (3.02). Without reasons they can only say I like it, and one I don't like from someone else is enough to knock it down. With reasons tied to the agreed criteria, they have an argument to stand on. Reasons that are shown can also be scrutinised: others can check and refute them, so the practitioner speaks with certainty only about what they can prove (0.7). Reasons constructed backwards after drawing usually give themselves away because they explain everything equally. And reasons are the part that survives handover: the future standards keeper knows what may change and what may not (11.02).
When it fails
Reasons cannot replace a good drawing; a good reason for a weak option is persuasion, not judgment. Some choices are purely visual, such as the curve of a stroke or the space between two letters, where the real reason is the trained eye; then say plainly that it is a visual judgment and offer a test in the real context (5.06), rather than building a strategic reason for it.
What it costs
Every reason stated is a point that can be refuted; the practitioner loses the mystique of the artist; time goes into writing rationale the client may not read in full.
Sources
Hugo Mercier and Dan Sperber, The Enigma of Reason, Harvard University Press, 2017
Open the presentation with the agreed criteria, then score the options against exactly those criteria in front of the decider.
When it comes upThe first five minutes of the presentation. The criteria are written and confirmed in the brief (3.05); this is about using them at the presentation table.
A test to take home
(1) The first page of the presentation reproduces word for word the criteria the decider confirmed, with the date of confirmation. Sinh Vũ agrees the criteria for judging options with the decider during discovery, so this page exists before any visuals do. (2) Ask one question: has anything changed since then? If so, record it immediately, before anyone sees a visual. (3) Present the visuals. (4) Score the recommended option yourself against each criterion: met, partly met, not met, and state plainly where it falls short before the client finds it. (5) Invite the decider to score with you; any comment that cannot be attached to a criterion goes into the taste column (3.07), not into immediate revisions. Pass: the presentation ends with a sentence in terms of criteria, such as four out of five met, the third criterion needs work here. Fail: the presentation ends with let us think about it, and nobody can say which criterion is being thought about.
The presentation is where a mature decision is defended, not where a decision is sought from the reactions of whoever is in the room.
When it comes upWhen scheduling and preparing the options presentation; when planning to show the client something and see what happens.
Resolution
Working together belongs to discovery sessions and the direction meeting (3.06); the options presentation defends. The two kinds of meeting carry different names on the calendar, so attendees know whether they are there to open things up or to close them.
Full reasoning
Two goods pulling against each other
Working together in the room gives fresh feedback, makes the client feel like a co-creator, and sometimes produces genuinely good ideas. Presenting a mature decision makes the meeting tight, the outcome clear, and the next step known to all.
Why it holds
On-the-spot reactions in a meeting room are group reactions: the person with the most authority speaks first and others lean towards them; the first view tends to pull later ones, much like the anchoring effect measured in numerical estimation. Janis's groupthink model describes this kind of drift, though the empirical evidence for it remains disputed (Esser 1998); this principle does not need the whole model, only the order of speaking in the room. A meeting that brings no clear recommendation will decide by that mechanism, not by criteria. A meeting with a clear recommendation asks a different, answerable question: does this option meet the criteria, and where does it fall short? The decider (0.3) must also be present; without them, the presentation becomes a rehearsal for another presentation the practitioner will not attend. That is why, in the list of what is needed from the client, Sinh Vũ states that the decider must attend the options presentation.
When it fails
When the presentation reveals that the agreed criteria are wrong, because the client brings new information or the market has just changed, insisting on defending is wrong; stop, record the fork (5.07), go back and agree the criteria again before drawing further. Defending does not mean not listening. Do not send the option files by message before the presentation: the decider looks at them alone on a phone, without reasons, and the presentation is lost before it takes place. If meeting in person is impossible, present over a guided call and send the files afterwards.
What it costs
The practitioner must decide before the presentation and risk being wrong in front of the client; the presentation may end with a clear no instead of a comfortable let us look further.
Sources
Irving L. Janis, Groupthink: Psychological Studies of Policy Decisions and Fiascoes, Houghton Mifflin, 1982
Amos Tversky and Daniel Kahneman, Judgment under Uncertainty: Heuristics and Biases, Science, 1974
James K. Esser, Alive and Well after 25 Years: A Review of Groupthink Research, Organizational Behavior and Human Decision Processes, 1998
Present the design in its real context of use, at the worst touchpoint it will meet, before showing it on a white background.
When it comes upWhen building presentation materials. A touchpoint is any place a customer meets the brand. The detailed tests at small size, on the shelf and on materials are in test 2.06 and principle 9.04; this is about order and arrangement at the presentation.
A test to take home
(1) Choose three contexts: the touchpoint customers meet most often; the worst touchpoint (smallest, farthest, poorest material, worst light); and a touchpoint made by someone outside the craft, such as a notice printed in the office or a photo taken on a phone. (2) Place the option into those three contexts using real photos of the business itself, not glossy downloaded mock-up templates. (3) Present the contexts first, the logo-on-white page last. Colour is not approved on a projector or meeting-room screen: on-screen contexts are only for approving layout; colour is settled only on a real printed sample or a swatch book, viewed under standard viewing light for prints (ISO 3664:2025). Legitimate exceptions: colour for digital touchpoints is approved on several of the client's real screens; colour for lightboxes is approved on a real material sample, lit, viewed after dark. Pass: the decider discusses context, such as on the street sign it looks like this, not just strokes. Fail: the option only works on white; or the client approves it and then sees it for the first time at a real touchpoint.
Sources
Sources
ISO 3664:2025, Graphic technology and photography: Viewing conditions
