Stakeholder meeting

Most people think a good meeting is about charisma, or an agenda, or keeping it to 30 minutes. It isn't. After running and sitting through thousands of them, the difference between a meeting that moves work forward and one that quietly wastes an hour comes down to two things:

1. 🤓Know what type of meeting you're in — and prep for that type.

A meeting to make a decision is not the same animal as a meeting to gather opinions. When you don't name the type, you bring the wrong prep, ask the wrong questions, and everyone leaves unsure what just happened. Naming the type is half the work.

2. 🧐Ask powerful questions.

A meeting is only as good as the questions in the room. Weak questions get you status updates and silence. Powerful questions get you the thinking you actually came for. Prep gets the right people and information in the room; powerful questions get the value out of them.

That's the entire framework. Everything below is just applying these two moves to the meetings you already run.

Some meetings barely need prep. Some live or die by it. Here's the quick map, then the three that deserve real attention.

The light ones

These run fine on instinct.

The next three don't.

The three that reward prep — and powerful questions.

These are the meetings where "winging it" costs the most, because each one is really about getting information into or out of a room. The more you front-load the prep, the better the questions land.

The job: Inform the team or a stakeholder about something and confirm they actually understood it — even if that just means a few questions at the end.

Prep that makes it work: The hard part of an informative meeting is that people nod without absorbing. So your prep is about clarity and verification, not just delivery. Decide the one thing they must walk away knowing. Cut everything that isn't in service of that. Then plan how you'll check understanding, because "any questions?" almost always gets you silence.

Powerful questions to ask:

👉(Template: Informative meeting)

The job: Gather opinions, knowledge, and experience — brainstorms, input from other departments or stakeholders, exploring an idea. Risks get weighed and ideas explored, but nothing is decided here. It's a discussion, and that's the point.

Prep that makes it work: The most common failure is treating an opinion meeting like a decision meeting and pressuring people to "land it." Don't.

Your prep is about framing the question wide enough to get real range, and inviting the right mix of perspectives — not just the people who agree with you. Send the topic ahead of time so people arrive with thought, not reflex.

Powerful questions to ask:

👉(Template: Opinion meeting)

The job: Make a final call — approve something, continue a project, or choose between options.

Prep that makes it work: This is the meeting that most needs prep, because the decision quality is set before anyone walks in. Whoever prepares the session — async or live — has to gather and share all the necessary information beforehand so the decision-maker(s) have everything they need. If people are reading the context for the first time in the room, you're not in a decision meeting; you're in a slow, expensive opinion meeting. Name the decision-maker. Name the options. Share the evidence ahead of time.

Powerful questions to ask:

👉(Template: Decision meeting)

Here's the part nobody puts on the calendar invite: over 60% of the meetings in most departments can be done async — and they actually work better that way.

That's not a productivity hack. It's a quality upgrade. When you move the right meetings to async, four things happen:

People have time to think. A live meeting rewards the fast answer. Async rewards the good one. You get considered opinions and real evaluations instead of raw, half-formed ideas blurted to fill silence.

It's not just the loudest voice anymore. In a room, the most confident or senior person sets the tone and everyone else calibrates to them. Async flattens that — the quiet expert and the loud generalist get the same blank space to write into.

Better input, not faster input. When the format isn't a ticking clock, you get thoughtful evaluation instead of reaction. The opinion meeting that produces three real arguments async would've produced one confident shrug live.

Nobody's work is held hostage to a calendar. The worst tax of meetings is the wait. A decision that needs six people doesn't wait for the one slot all six are free — which is often days out. Async, the work keeps moving while people weigh in on their own time.

So which 60%? As a rule of thumb: Informative and Opinion meetings are almost always better async — broadcasting information and gathering input don't need everyone breathing the same air at the same time. Even a lot of Decision prep belongs async, with the live session reserved only for the final call (if you need one at all). What genuinely needs to be live: 1:1s, anything emotional or relational, real-time problem-solving, and decisions where you need to read the room.

The move isn't "have fewer meetings." It's: default to async, and earn the right to be live. Before you send the invite, ask the most powerful question of all —

"Does this actually need to be a meeting?"

More often than you'd think, the honest answer is no. And the work is better for it.