Your Calendar Is Broken Because Your Decisions Are

Your Calendar Is Broken Because Your Decisions Are

Why we invite everyone "just in case" -- and how to stop

Count the meetings on your calendar next week. Now ask yourself, honestly: how many of them have a clearly defined decision attached? How many have a named person who will actually make that call?

If you're like most of the managers and knowledge workers I talk to, the answer is uncomfortable. Maybe two or three out of ten, if you're generous.

We blame meeting culture for overloaded calendars, and that's fair as far as it goes. But underneath meeting culture is something more fundamental: decision culture. When decision rights are fuzzy, when nobody is sure who owns the call, we compensate by inviting everyone "just in case." That's how you end up with twelve people in a room for an hour, a lot of talk, and nothing actually decided.

The problem isn't just the meetings. The problem is that your decisions aren't designed.

Someone had to say it.

The "Just in Case" Invite Problem

Most meeting invites are written in polite corporate code. You know the ones:

• "Let's get together and discuss."

• "Would love your thoughts."

• "Quick sync on where we're at."

None of those say what decision is being made, who owns that decision, or who's providing input versus who's actually accountable for the outcome. And when those things aren't clear, the person sending the invite defaults to the only safe move available to them: invite everyone who might have an opinion, anyone who might be offended if they weren't included, and a few people who "should probably know about this."

The result is a calendar full of what I call political insurance meetings. Nobody wants to make the wrong call or upset the wrong person, so they buy sixty minutes of everyone's time to protect themselves. It feels safer. It's also an enormous drain on organizational capacity, repeated dozens of times a day across the business.

The Missing Piece: Decision Roles

There's nothing mystical about clarifying who does what in a decision. We already have simple, well-tested frameworks for this. We just rarely apply them to how we design meetings.

Three of the most common are worth knowing:

RACI breaks it into: Responsible (who does the work), Accountable (who owns the result and makes the call), Consulted (who gives input before the decision), and Informed (who needs to know after).

DACI uses: Driver (who orchestrates the process), Approver (who has final say), Contributors (who provide expertise and input), and Informed (who is updated on the outcome).

RAPID covers: Recommend (who proposes a course of action), Agree (who must sign off and can veto in their domain), Perform (who executes once decided), Input (who provides data or perspective), and Decide (who makes the final call).

The frameworks differ in flavor, but they all make the same essential point: when you know who decides, who drives, who contributes, and who is simply informed, you don't need fourteen people in the room "just in case."

Design Decisions First, Then Meetings

Most organizations do this completely backwards. Something vague needs attention, so someone says "we should set up a meeting," the usual suspects get invited, and everyone hopes a decision will emerge somewhere in the conversation.

What if we flipped it?

Before scheduling anything, ask these questions first:

What exact decision are we making? Be specific to the point of discomfort. "Align on next steps" is not a decision. "Decide whether to delay the Q3 launch by two weeks" is.

Who is the Decider? In RACI terms, that's Accountable. In DACI, it's the Approver. In RAPID, it's Decide. This must be one named person -- not a committee, not "the team," not "leadership." One person.

Who is driving the process? In DACI that's the Driver; in RAPID it's Recommend. This person gathers input, frames the options, and moves things forward. They may or may not be the same as the Decider.

Who genuinely needs to provide input before the call is made? Think domain experts, impacted owners, risk or compliance where relevant. Here's the critical reframe: many of these people can provide input asynchronously. They don't need a meeting slot.

Who only needs to be informed after? These are stakeholders who care about the outcome but don't shape it. They get a summary, not a calendar invite.

Only after you've answered those questions do you ask: "Do we even need a meeting? And if so, with exactly whom?"

Sometimes the answer is yes, you need synchronous time. But often, once the roles are clear and async input is collected, what felt like a 90-minute meeting becomes a 20-minute decision conversation -- or disappears entirely.

Try This: One-Decision Micro-RACI

Pick one upcoming meeting on your calendar that feels fuzzy or over-staffed. Grab a notepad and work through this before you hit "accept":

1. Write down the one decision this meeting is supposed to produce. If you can't name it clearly, that's your first problem -- and fixing it might make the meeting unnecessary.

2. Name one person as Accountable / Approver / Decider for that decision. Write their actual name, not a team or a title.

3. Name one person as the Driver / Recommend / Responsible. Again, one name.

4. List no more than three people who truly need to provide input before the decision is made. If you're listing more than three, ask yourself whether some of those could contribute in writing beforehand instead.

5. Move everyone else to Informed. They get the outcome; they don't need the meeting.

Now go back to the invite list and trim it accordingly. Keep the Decider, the Driver, and your one to three key input providers as required. Convert everyone else to "no need to attend -- you'll receive a summary."

Will that feel uncomfortable the first time? Yes. Will it save time and sharpen the conversation? Also yes.

Your Calendar Is a Mirror

Your calendar is not just a time-management problem. It is a mirror of how your organization designs -- and avoids -- decisions.

If decision rights are unclear, your calendar will be chaotic, over-populated, and exhausting. If decision rights are clear, your calendar will be lighter, sharper, and more respectful of everyone's time, including yours.

This is the first article in a series where we keep pulling on this thread. In Article 2, we'll take it one level further with a rule that might feel radical at first: no one should be in a meeting without a clear decision role, and how to make that work without shutting people out. In Article 3, we'll look at how to use pre-work, async input, and AI so that meetings become 30-minute decision forums rather than 90-minute update marathons.

If you're joining at a later article, start here. This is the foundation.

How many meetings on your calendar this week actually have a named Decider attached? Count them. That number will tell you a lot.