The Meeting That Should Have Been a Decision

Two years ago, my calendar was a solid block of meetings from 8 AM to 6 PM, Monday through Friday. I had standing meetings to prepare for other meetings, sync meetings to align on upcoming meetings, and retrospective meetings to discuss what happened in previous meetings. I was meeting-rich and decision-poor.

The breaking point came when I realized we had spent six weeks discussing whether to change our pricing model for small hotels. We had fourteen meetings involving twenty-seven people. We had beautiful slide decks, detailed competitive analysis, and passionate debates. What we didn't have was a decision.

That's when I understood something fundamental about scaling companies: meetings often become theater. They create the appearance of progress while actually preventing it. We were using meetings as a substitute for decision-making, a way to spread accountability so thin that no one person could be responsible for an outcome.

The Meeting Taxonomy

We started by categorizing every recurring meeting on our calendars. We found they fell into four buckets:

Decision meetings: Where choices get made (12% of our meetings)
Alignment meetings: Where information gets shared and understood (28%)
Status meetings: Where updates get reported (45%)
Habit meetings: Where we meet because it's Tuesday (15%)

The problem was clear: only 12% of our meeting time was actually moving decisions forward. The rest was either preparation for decisions, reporting on decisions, or ritual without purpose.

The 40% Cut

We made a radical decision: we would eliminate 40% of our recurring meetings within 30 days. Not reschedule, not optimize, eliminate. Each team had to justify every meeting on their calendar against three criteria:

Does this meeting result in a specific decision or action?
Could the purpose be accomplished asynchronously?
Are all attendees necessary for the outcome?

The results were surprising. We eliminated our weekly all-hands status meeting (replaced with a Friday written update). We killed the "prep for board meeting" prep meetings (created a shared document instead). We dissolved the cross-functional "innovation working group" that had met for eight months without producing anything shipped.

The most resistance came from eliminating status meetings. People worried they wouldn't know what others were working on. We solved this by implementing a simple async system: every Friday, everyone posts their week's accomplishments and next week's priorities in a Slack thread. It takes five minutes to write and ten minutes to read, versus the sixty-minute meeting it replaced.

Decision Meetings vs. Alignment Meetings

The key insight was distinguishing between meetings that should make decisions and meetings that should create alignment. They're different animals requiring different approaches.

Decision meetings have three non-negotiable rules:

A single decision owner who is accountable for the outcome
All background material circulated at least 24 hours in advance
A clear "decide by" date that cannot be extended

Alignment meetings have different rules:

No decisions are made during the meeting
The goal is shared understanding, not consensus
Follow-up actions are assigned to individuals, not committees

We found that most of our meetings were trying to do both simultaneously, and failing at both. By separating them, we made better decisions and created clearer alignment.

The Pricing Model Decision

Remember the six-week pricing model discussion? After implementing our new meeting framework, we revisited it. Here's how it went:

Week 1: We held one 90-minute alignment meeting where the product team presented three options with pros and cons. No decisions were made. Everyone left with the same information.

Week 2: The sales, marketing, and product leads each spent time with their teams discussing the options. They documented concerns and preferences in a shared document.

Week 3: We held a 60-minute decision meeting. I was the decision owner. We reviewed the documented feedback, discussed trade-offs, and I made a decision at the 55-minute mark. The entire process took three weeks instead of six, involved 40% less meeting time, and resulted in a clearer, more confident decision.

Accountability Avoidance

The hardest pattern to break was what I call accountability avoidance. This is when teams use meetings to diffuse responsibility. If fifteen people are in a room discussing something, no one person can be blamed if it goes wrong. If no decision emerges from the discussion, no one can be held accountable for inaction.

We combat this with two mechanisms:

The DRI system: Every project has a Directly Responsible Individual. That person owns the decision and the outcome.
Meeting minutes that assign actions: Every meeting ends with a list of specific actions, each assigned to one person with a due date.

The shift was cultural. We had to reward people for making decisions quickly, even if some of those decisions turned out to be wrong. We had to penalize indecision more than we penalized mistakes.

The Results

Eighteen months after cutting 40% of our meetings, here's what changed:

Time to decision decreased by 65% across all major initiatives
Employee satisfaction with meetings increased from 3.2 to 4.7 on a 5-point scale
We shipped 22% more product features with the same team size
My own calendar has 12-15 hours of free time each week for deep work

The most surprising outcome was how it changed our communication. When you can't rely on meetings to share information, you have to write things down. Our documentation improved dramatically. When you can't use meetings to avoid decisions, you have to make them. Our velocity increased.

Meeting Hygiene

We maintain our meeting discipline with quarterly audits. Every three months, we review all recurring meetings and ask: is this still necessary? Could this be async? Are the right people attending?

We also have simple rules for all meetings:

No meeting longer than 60 minutes (most are 30)
Agendas required 24 hours in advance
No laptops unless you're presenting
Action items documented within one hour of meeting end

These rules seem basic, but they're remarkably effective. They force clarity of purpose and respect for everyone's time.

The Meeting That Should Have Been an Email

We have a Slack channel called #meeting-that-should-have-been-an-email. When someone feels a meeting was unnecessary, they post a polite summary of what could have been communicated async. It's not about shaming, it's about learning. We review these monthly to identify patterns.

The most common pattern: meetings called to "get alignment" when what was really needed was a decision. The second most common: meetings where one person talks for 45 minutes and then asks for questions. That's a presentation, not a meeting.

Meetings are expensive. A one-hour meeting with eight people costs the company about $800 in salary time, not including opportunity cost. We should spend that money as carefully as we spend any other resource.

Final Thought

I still have meetings. Good meetings are essential for complex coordination and creative collaboration. But I'm much more selective about which conversations deserve synchronous time.

The test I use now: if we're not going to make a decision or have a breakthrough insight, we probably shouldn't be meeting. Information can be shared asynchronously. Updates can be written. Alignment can often be achieved through clear documentation.

Decisions, though, decisions often need conversation. The back-and-forth, the questioning, the weighing of trade-offs. That's what meetings should be for. Not for avoiding decisions, but for making them.

What decision is your next meeting avoiding?