Further Reading — Chapter 4: Discovery and Vision

Tier 1 = real, published, verifiable. Tier 2 = widely known practice, attributed without invented detail. Nothing here is fabricated.

The problem this chapter solves — converting a client's felt preference into an executable specification — is not an events problem. It belongs to every design discipline, and the disciplines that have thought hardest about it are architecture, brand strategy, and user research.

The design brief, done properly

The RIBA Plan of Work and the AIA's programming phase documentation. (Tier 1)

Architecture has a formal name for what §4.2 does: programming (or "briefing" in the UK). It is a distinct, billable phase that occurs before design begins, and its entire purpose is to convert a client's aspirations into a document of requirements, constraints, and priorities. The RIBA Plan of Work makes it Stage 1 and will not let you proceed without it.

Read the stage descriptions — they are freely available — and notice one thing in particular: architecture treats the brief as a deliverable, charged for, signed off. Events treats it as something you do informally on the way to the fun part. That difference explains a great deal about why architectural clients get what they asked for more often than wedding clients do.

Pena, William, and Steven Parshall. Problem Seeking: An Architectural Programming Primer. Wiley. (Tier 1)

The classic text on the programming phase, and the closest thing in print to a rigorous methodology for §4.2. Its core framework — separating goals, facts, concepts, needs, and the problem statement — maps almost directly onto the vision document's sections. Its most useful contribution for this chapter is the insistence that the brief must be falsifiable: a statement you cannot disagree with has not stated anything.

On what people actually want versus what they say

Norman, Don. The Design of Everyday Things. Basic Books. (Tier 1)

For the gap between stated and revealed preference (§4.6), and for the general principle that people are excellent reporters of their frustration and poor reporters of their requirements. Norman's distinction between what users say they want and what their behavior demonstrates is exactly the divergence the §4.6 photography example turns on.

Contextual inquiry and the "five whys." (Tier 2)

User research methodology, borrowed wholesale. The technique of asking "why" repeatedly until you reach a reason rather than a preference is precisely what §4.2's moment questions are doing indirectly. The events version — "where are you standing? what can you hear? what are people doing with their hands?" — is a softer form because a client planning a wedding will not tolerate five consecutive whys, but the mechanism is the same: descend from preference to cause.

Jobs-to-be-Done, and Clayton Christensen's milkshake example. (Tier 2)

Widely recounted, and the definitive short illustration of §4.8's Image 8 principle. The finding — that a fast-food chain's morning milkshake buyers were not buying a beverage but hiring something to occupy a long commute — is the same move as recognizing that a ceremony arch is not an object but a solution to a problem of attention. Once you know what the object is for, you have alternatives. Reliable summaries are widely available; the anecdote is well-documented and the framework is worth twenty minutes.

On priority and trade-off

Kano model of customer satisfaction. (Tier 2, associated with Noriaki Kano)

A framework distinguishing features that delight from features whose absence causes dissatisfaction but whose presence goes unnoticed. Directly applicable to the forced ranking: a great deal of a wedding budget goes into hygiene factors — working restrooms, food arriving on time, a room at a tolerable temperature — where excellence produces no delight and failure produces disaster. Sam's late-night food is a delighter; the shuttle is a hygiene factor. Ranking them against each other with a single list obscures this, and it is the strongest available critique of §4.4 (exercise D.2).

MoSCoW prioritization — Must have, Should have, Could have, Won't have. (Tier 2)

A project-management convention worth knowing because of one feature: the "Won't have" category is explicit and named. The chapter's "the one you're most relaxed about" is doing the same work with less confrontation, but the MoSCoW version is more honest, and for corporate clients (Chapter 31) it is often the better instrument.

On the image and the selection effect

Berger, John. Ways of Seeing. Penguin. (Tier 1)

Short, and permanently useful. Berger's argument — that images are made under conditions and carry the interests of their makers — is the intellectual foundation of §4.5's selection-effect claim. A wedding image circulates because it photographed well; it photographed well partly because of money and partly because of composition, light, and restraint. Separating those two is the whole board-pricing technique, and Berger will make you better at it.

Any serious treatment of photographic lighting. (Tier 2)

Not to become a photographer — to be able to look at an image on a client's board and see where the light is coming from and what it is doing. This single skill accounts for most of the value in the board-pricing conversation, because light is the most common driver of an image's appeal and the cheapest thing to reproduce. Case Study 2's Image 1 — where a $9,500 greenery installation was competing with candles for the client's actual response — is a lighting observation.

On the events side

Bailey, Preston. Design for Entertaining. (Tier 1)

Chapter 1 recommended it as an example of the ceiling of event design. Here it serves a different purpose: read it specifically to practice §4.5, by taking his most spectacular installations and asking what is driving the cost and what a viewer is actually responding to. Bailey's work is frequently expensive because of volume and installation — the two most reducible drivers — and the exercise of finding the 20% version of a Bailey table is excellent training.

Allen, Judy. Event Planning. Wiley. (Tier 1)

Her treatment of the client brief is more structured and less emotionally attentive than this chapter's, because her clients are corporate and have written objectives. Read the contrast: a corporate brief begins with a measurable business objective (Chapter 31), which the wedding brief lacks entirely. The vision document exists because there is no objective function, and something has to substitute for one.

What to be careful with

Style-quiz and "find your wedding aesthetic" content. Abundant, and it does the opposite of this chapter. It sorts clients into pre-existing named categories — boho, modern, classic, romantic — which is precisely the substitution of a template for a translation. A client who has been told they are "boho" will describe their wedding using a vocabulary that belongs to a magazine, and you will have to undo it before you can find out what they actually respond to.

Mood-board tools that emphasize collection over annotation. The tools are fine and the behavior they encourage is the problem: pinning is cheap and annotating is not, so boards accumulate unexamined images. Whatever tool a client uses, the annotation is the thing that matters, and it usually has to happen in a room with you.

A note on what is missing

There is no published methodology for the wedding vision interview. Architecture has programming, product has discovery, brand has strategy — events has "have a chat about what they like."

This chapter is an attempt at filling that, assembled from the adjacent disciplines above and from trade practice. Treat the specific structures — the six segments, the translation table, the five cost drivers — as a working proposal rather than a standard, and improve them. The parts most worth testing against your own experience are the fidelity estimates in Case Study 2, which are honest guesses, and the claim that roughly a third of any board has no attached response, which is trade observation rather than measurement.

If you do the work in exercise E.3 and find the claim is weaker than stated, that is a genuine contribution. Say so in an issue.