Meetings Are for Declarations, Not for Decisions

Nobody has ever been convinced in a comment section.

Think about it. Millions of arguments. Thousands of hours of back-and-forth. Evidence presented, positions defended, logic deployed. And at the end of it all — almost nobody changes their mind. Not because people are irrational. Because by the time someone enters a comment section, they've already decided. The arguing is theater. The decision was made before the first word was typed.

Meetings work exactly the same way. And most designers don't know it.

The Avalanche Was Already Moving

Here is what most people believe about meetings: that the decision starts forming when people sit down, builds through discussion, and lands somewhere by the end. Like a snowball rolling down a hill, gathering size and shape as it goes.

That is not what happens.

The snowball starts rolling the moment the meeting is scheduled. When someone sees the title, they form a first impression. When they read the agenda, they start building a position. When they see who else is invited, they begin calculating. By the time they actually sit down — physically or virtually — the avalanche is already in motion. What happens in the meeting is not a decision being formed. It is a decision being declared.

You are not arriving at a decision meeting. You are arriving at a declaration meeting. The question is whether the declaration goes your way.

Their Framework Got Them Here

Every person in that room carries a decision framework. A set of beliefs, experiences, and mental models that they have been operating from — and that, from their perspective, has been working. It got them their title. It got them their track record. It got them into this meeting in the first place.

Your design is new input hitting an old filter.

That filter might flag a strategic misalignment — your design doesn't map to the goals they're being measured on this quarter. It might flag a personal preference dressed up as objective feedback. It might flag a concern they can't quite articulate but feel strongly about. Whatever it flags, the filter was already in place before you opened the file.

And here is what makes this hard: your design work — the thing you've spent days or weeks on, the thing you care about deeply — might be nothing more than a checkbox on their list. One item in a day full of competing priorities, each filtered through the same framework. You are not the centre of their meeting. You are a stop along the way.

Do Your Homework Before You Walk In

If the decision is already forming before the meeting, then the most valuable work you can do happens before you arrive.

For corporate stakeholders: what other projects are they running right now? What are the strategic priorities for this quarter? What pressures are they under that have nothing to do with your design but will color how they see it?

For clients: what is the state of their business? What does success look like for them — not for the project, but for them personally? What have they had to defend recently, and to whom?

This is not background reading. This is frame intelligence. The more you understand about what filter your work is going to hit, the better you can position it — or at minimum, the less surprised you will be when it gets filtered.

Use the Design as a Target Board

Sometimes you walk in without enough intelligence. The stakeholder is new, the context is unclear, or the meeting was scheduled too fast. That is fine. The meeting itself becomes your research.

Present the design. But don't present it to be approved. Present it to be shot at.

Put the work on the table and watch where the objections land. Each reaction is a data point about their framework. A comment about the color scheme might be aesthetics — or it might be anxiety about brand consistency dressed as a design note. A concern about the navigation might be a usability opinion — or it might be a political signal about whose department owns what. A question about timeline might be logistics — or it might be a test of how much you've thought this through.

Open-ended questions unlock this. Not "do you like it?" but "what does this bring up for you?" Not "is this the direction?" but "what would need to be true for this to work in your context?" Let them talk. Let them reveal. The more they speak, the more you understand the filter you're actually working with.

You are not losing control by listening. You are gathering the intelligence you need to design the next conversation.

The Meeting Is Not Where You Win

Stop trying to convince people in meetings. It almost never works — not because your argument is weak, but because the decision was already forming before you arrived. Pushing against a pre-formed position in real time, in a room full of people, with status dynamics in play, is the hardest possible way to change a mind.

The meeting is where you declare what has already been decided — or where you discover that the decision went the wrong way and you need to design a better situation for next time.

The real work is what happens in between. The one-on-one conversation before the group meeting. The framing email that lands two days before. The question asked to the right person in the right moment, before the room fills up and positions harden.

If you walk out of a meeting frustrated that nobody listened — ask yourself this: when did you actually try to influence the decision? If the answer is "in the meeting," you were already too late.

Design the Situation, Not Just the Deliverable

Meetings are not where decisions happen. They are where decisions land. The decision was already in motion — shaped by context, by framework, by everything that happened before anyone walked in the room.

Your job is not to win the meeting. Your job is to design the situation so that by the time the meeting happens, the right decision is already the obvious one. That is a different skill from presenting well. It requires understanding how decisions actually form — and working at that level, not just at the level of the deliverable.

The avalanche is already moving. The question is whether you designed the slope.