If You Don't Have a Decision Role, You Don't Need a Seat

If You Don't Have a Decision Role, You Don't Need a Seat

Shrinking the room without shutting people out

This is Part 2 of a three-part series on decision-centric meeting culture. If you haven't read Article 1 -- "Your Calendar Is Broken Because Your Decisions Are" -- that's the best place to start. It lays the foundation for everything here.

In Article 1, I argued that your calendar is overloaded because your decisions aren't designed. When nobody knows who decides, who drives, or who's just informed, we invite everyone "just in case."

Now let's go one level more uncomfortable.

If you don't have a decision role, you don't need a seat in the meeting.

Someone had to say it.

I don't mean you don't deserve to be heard. I mean that awareness and inclusion don't have to take the form of synchronous attendance -- and pretending otherwise is costing everyone, including you.

The Spectator Section

You know these people. Sometimes you are these people.

You join because your boss invited you, and declining felt risky. You sit on mute with your camera off. You multitask your way through your inbox and feel mild guilt about it. You speak once, maybe twice, just to signal that you're paying attention. You're not sure why you were invited. You're not sure the person who invited you knows either.

You're not a bad employee. You're just not actually needed there. You've been invited as a human safety net:

"They might have thoughts." "They might need to be aware." "We don't want to upset them by leaving them out."

It's well-intentioned. It's also a slow drain on human energy and trust. Because here's what repeatedly inviting people to meetings where they have no real role actually communicates, whether you mean it or not:

"We don't respect your time." And underneath that: "We haven't done the work to design this decision properly."

No Role, No Seat: The Rule Worth Enforcing

Here's the standard worth holding:

No calendar invite without a clear role in the decision -- either in making it or in bringing something essential to it.

Using RACI, DACI, or RAPID makes this concrete rather than subjective:

The Decider / Approver / Accountable must be there. No exceptions. If the person who makes the call isn't in the room, you're not having a decision meeting -- you're having a rehearsal.

The Driver / Recommend / Responsible must be there. They'll frame the issue, present the options, and move things to a conclusion.

Contributors / Input / Consulted sometimes need to be present -- particularly for complex, cross-functional decisions where real-time expertise might shift the direction. But "sometimes" is the key word. Many of these people can contribute just as effectively through async input before the meeting.

Perform / Informed do not need to be in the room. They need the outcome and the rationale -- both of which can be delivered in a clear written summary.

That's it. That's the list. Everyone else is a spectator, and spectators deserve their time back.

Designing the Invite List Around Decision Roles

Start from the decision itself (which you've already defined, as we covered in Article 1), then run this quick check for each potential attendee:

Who is making the call? That's your Decider. They must be present -- if they're not available, reschedule. A decision meeting without the Decider is just a discussion.

Who is driving the process? Your Driver or Recommend person. They must be present too, since they'll frame the issue and the options.

Who truly needs to contribute in real time? For most decisions, this is one to three people whose expertise or perspective could genuinely change the direction in the moment. Not everyone who has a relevant opinion -- only those whose live input is necessary.

Who can contribute asynchronously? Other stakeholders and experts can comment on a pre-read, add notes in a shared doc, or respond to a targeted question. Their input matters. Their attendance often doesn't.

Who just needs to know afterward? Anyone else belongs in Informed. They get the summary, the decision, and the rationale -- not the invite.

You will be tempted to add people "just in case." That's the old reflex at work. Resisting it is part of the job now.

"But What About Inclusion and Psychological Safety?"

This is a fair concern, and it deserves a direct answer rather than a dismissal.

Tighter meetings must not become a cover for exclusion, particularly for underrepresented voices or for team members who are already on the margins of key conversations. So the answer is not "small rooms only" -- it's inclusive design plus smaller rooms. They're not in conflict if you're intentional about it.

Async input for broader voices. Share the decision brief in advance with a wider group. Explicitly invite comments, questions, and alternative views. Consider anonymous input channels where your culture calls for it.

Rotating representation. Instead of inviting ten people from one function, rotate one or two representatives and make sure those people have a clear mandate to speak for their peers and bring decisions back.

Transparent summaries. Make decision notes and rationales visible to anyone who has an interest. Invite follow-up questions or challenges in writing after the decision is made.

Inclusion is not "everyone in every room, all the time." Inclusion is everyone having a structured, legitimate way to shape and understand decisions. The mechanics are different; the commitment is the same.

Try This: Rewrite One Recurring Invite List

Choose a recurring meeting that feels too big -- you probably already know which one.

List every current attendee. Next to each name, assign one role for the main decision this meeting is supposed to serve, using whichever framework you prefer (Decide/Drive/Contribute/Inform works fine as a shorthand).

Then redesign the invite:

Keep Decide and Drive as required attendees. Keep two to four key Contribute/Input people as required; push the rest to async. Move Perform/Informed to a distribution list for notes.

Then rewrite the invite description to make roles explicit. Something like: "Required: Decider, Driver, and the three named contributors below. Everyone else: your input is welcome in the shared doc -- you'll receive a clear summary with the outcome and rationale."

Run it for three cycles. Watch what happens: meetings get shorter and sharper, people who no longer have to sit in spectator status get focus time back, and the people who remain in the room know exactly why they're there. That last one matters more than it sounds.

Respecting Time Is Respecting People

We say people are our most valuable resource. Then we burn their time in meetings where they neither decide nor contribute nor learn anything they couldn't have read in a two-paragraph summary.

Respecting people means respecting their focus, their energy, and their autonomy over their own working hours. A smaller, sharper, role-based invite list is not a bureaucratic exercise. It's a signal that you've done the work to design the decision properly -- and that you take seriously what it costs other people to show up.

In Article 3, we'll look at the other half of this problem: even with the right people in the room, we still waste enormous time "getting everyone up to speed" on information that could have been read in advance. We'll dig into how pre-work, async input, and AI can turn your meetings from 90-minute update sessions into 30-minute decision forums.

If you found this article first, start with Article 1 -- "Your Calendar Is Broken Because Your Decisions Are" -- to see the full picture from the beginning.

Take one recurring meeting this week. List the attendees. Assign each person a decision role. How many don't have one?