Design meetings aren't about design

One Monday a slice of red pepper showed up on a designer's desk.¹ The CEO's wife had picked it for the new logo's color. He had taken the drafts home for the weekend, dinner guests around the table chimed in, and his wife pointed to whichever vegetable came closest to what she liked. The designer set the pepper next to the color picker. The CEO's one line had been: "Use the color my wife chose."

It would be a stretch to call this a small-company picture. Gap's 2010 logo lasted six days.² The draft that ditched the blue box for Helvetica went out with unanimous sign-off from Gap's executive boardroom, and came back to the old logo within six days.

In neither meeting room was the design itself wrongly decided. What was wrongly decided wasn't the design but who got to be in the room. The CEO's wife wasn't qualified to decide a color; she was simply in a position where she could participate in the decision. Same for Gap's executive room.

You've seen this scene before. Five people in the infra meeting, five in the finance meeting, fifteen in the design meeting. Whether the company is 50 or 200 people, the design meeting is always the most densely populated room.

It's not because the company values design that much. The real decisions — pricing, layoffs, market exit — are made by a small group. As far as I know, design is the only domain where the more important it gets, the more people end up in the room.

Design has the lowest cost of entry for an opinion

Other agendas have qualifications. To voice an opinion on indexing strategy in a DB schema meeting, you have to be able to read query patterns. To opine on capex classification in a finance meeting, you need to know accounting principles. Contract review is done by people who can read legal language. People without the qualification don't speak up even when they're in the room.

Design doesn't filter. Color is visible to everyone, font size is comparable by anyone, and anyone can say a logo's balance "feels off." The cost of entry for an opinion is the lowest of any agenda in the company, and that's why everyone shows up to the design meeting.

Parkinson named this pattern the Law of Triviality back in 1957.³ The observation that a nuclear power plant agenda passes in thirty minutes while the bike-shed paint color drags on for three hours. Bikeshedding got its nickname there.

Design isn't measured, so it gets dressed in unfalsifiable language

To draw the line upfront: the design this essay deals with is brand, identity, aesthetics — not funnel/CRO design. Whether removing a form field on a checkout page lifts conversion by a few percent is something A/B testing answers almost instantly. Expedia famously made $12M a year extra by removing one checkout form field.⁴ That's that kind of domain. Those design meetings don't run long, because measurement filters them. The design meetings that run long are the ones in domains measurement can't reach — brand, identity, aesthetics.

Compare again with other agendas and the difference sharpens. Engineering is measured. Bad code makes response times spike, error rates climb, services go down. No words in the meeting room can turn those numbers into a lie. Finance gets every classification decision audited backward at quarter end. Legal loses disputes when contracts are written wrong.

Design doesn't get that. Who decides six months later whether the new logo was good, and how? If revenue went up, was it the logo, the ads, or the market cycle? If revenue went down, was it the logo's fault or every other variable's? Even the Nielsen Norman Group, the authority on UX measurement, admits ROI prediction for intangible benefits like brand awareness is "nearly impossible."⁵ Measurement doesn't filter.

Where measurement can't filter, decisions get wrapped in unfalsifiable language. The phrases you hear in those rooms — "it fits the brand identity," "it resonates with users," "the tone feels right" — are not factual statements. They aren't propositions you can refute; they're self-reports dressed up in vocabulary that rationalizes the opinion. Nobody can fire back, "the brand identity you just named is measurably wrong." Not because numbers are missing. Because the vocabulary itself refuses measurement.

Organizational theorist Karl Weick wrote in 1995 that organizations run on plausibility, not accuracy.⁶ Consensus in a meeting room chases a plausible narrative, not a fact. The design meeting is the stage where this mechanism operates most nakedly. As long as it sounds plausible, any opinion survives.

A collapsed bridge can be called collapsed. A bad design has no vocabulary for being called bad.

So hierarchy takes the seat

When measurement can't filter and vocabulary refuses to push back, the decision still has to be made by someone. That someone is the highest-ranking person in the room. The data-driven decision movement calls this the HiPPO — Highest Paid Person's Opinion.⁷ When measurement can't act as the counterweight on consensus, the counterweight seat gets taken by hierarchy. Other agendas have measurement and qualification keeping hierarchy somewhat in check; design has neither.

The flatter the org — similar titles, blurred authority — the sharper the picture. When hierarchy isn't explicit, speaking up in a meeting becomes one of the only ways to make your seat visible. Design meetings rent out that stage for next to nothing. No qualification needed to opine, no vocabulary to refute what's been said.

A committee-decided design fails with nobody accountable⁸ — psychology's diffusion of responsibility playing out inside an org — is a byproduct of the same picture. When it's unclear whose decision it was, the company can't learn whose decisions were good and whose were bad. The signal that lets you recognize people with good taste disappears, and the company loses the ability to grow that taste in-house.

The asymmetric cost

The cost of this mechanism lands in two places. The designer's time, and the blandness of the output.

In a design meeting, the designer usually speaks the least. (That was true in most of the meetings I sat in.) The person who brought the top pick and the reasoning ends up speaking the least — that's a design meeting. The silence isn't agreement; it's fatigue. The silence of someone watching their design intent get chipped away week after week, under zero-cost opinions dressed in unfalsifiable vocabulary.

Imagine a marketer, an engineer, an accountant, and the CEO sitting in a film editing room deciding the cuts. It sounds ridiculous. Why doesn't the designer's room sound ridiculous?

The output pays too. A design run as a decision-substitute turns bland. It becomes the average of one-line additions from each person, and the screen the user outside the company sees inches toward that average. The anonymous proverb gets it right: a camel is a horse designed by committee.

Beyond design

Design is just one point on a spectrum.

There are areas in any organization measurement doesn't reach. Company culture. Long-term strategy. Hiring evaluation. Quarterly review conversations. Brand positioning. Everyone gets in the room, everyone has an opinion, and decisions get made inside unfalsifiable vocabulary — "it fits our identity," "it's the right call long-term," "they're a good fit," "qualitatively, the review is fair." The mechanism of the design meeting operates there too, exactly the same way.

Kaplan and Norton estimated that more than 75% of the average firm's market value comes from intangible assets that don't get measured.⁹

And where do all these meeting attendees' hours — their salaries — come from? In domains measurement can't reach, the company can't measure the outcome, and it also can't measure the cost of the process that got there. Every week the same people gather for the same meeting and reach the same decisions using the same vocabulary. They're effectively spending payroll on it. Meetings in measurable domains stay aware of their own cost. When that awareness collapses, you get scenes like the one I saw at a fintech: fifteen people in a big meeting room every morning for a thirty-minute standup. Each person's day was laid out on the table before it began. When a design meeting runs long, the payroll in the room burns long.

Five prescriptions

1. The designer brings the top pick with the reasoning.
2. If there's no explicit objection, ship it (lazy consensus).
3. Leader input ends at the brief stage.
4. Comments on the artifact stay at reactions only (the Jobs–Ive model).
5. Don't object in unfalsifiable vocabulary — replace "it doesn't fit the identity" with one line: "change this, this way, for this reason."

Closing

I'm not a designer. I sat in the seat with the weakest claim to exercise hierarchy in an unmeasurable domain — the engineer crammed into the design meeting. I couldn't open my mouth in the room. I quietly agreed with option one, and never said the one line that would have ended it: this meeting doesn't need to run this long.

I just thought "this isn't quite right." Looking for the reason behind that "not quite right" is how this essay started. Whether I'll be able to open my mouth in the next meeting, I don't know.

Confucius once said to his disciple Zi Lu: to know what you know and to know what you don't know, that is knowing.¹⁰ Zi Lu had a habit of insisting he knew things he didn't.

Two and a half thousand years on, Zi Lu sits in conference rooms everywhere.