Your Meetings Aren’t the Problem. Your Decision Rights Are.
J Israel Greene, CDE, LSSGB
CEO & Founder of Mosaic Worx
When leaders complain about meeting overload, the usual prescription is calendar management: shorter meetings, fewer attendees, no-meeting Fridays, tighter agendas.
Those can help. But they rarely fix the real problem.
Most recurring meetings exist because people do not know who has the authority to decide. So they keep bringing the question back to the room week after week, hoping that more discussion will eventually create the clarity that should have existed before the meeting began.
It will not.
A team can have a beautifully managed calendar and still waste hours revisiting decisions, collecting input that nobody is accountable for using, and leaving the room unsure what was actually decided. That is not a meeting problem. It is a decision-rights problem.
The Meeting Myth
Here is the pattern: a decision comes up, someone says, “Let’s get the right people together,” and a meeting appears on the calendar.
Then the conversation expands. More people are invited because their input may matter. The group discusses options. People leave with different interpretations of what happened. Someone sends a recap. Next week, the issue is back on the agenda because the decision was never truly owned in the first place.
The meeting was not unnecessary because people should not have talked. It was unnecessary because the team had not answered three basic questions before the conversation started:
- Who owns the final decision?
- Whose input is genuinely needed before that decision is made?
- How will the decision, its rationale, and its implications be communicated afterward?
Without those answers, meetings become holding pens for unresolved authority.
Decision Flow Is the Issue
This is what the Decision Flow domain of the Team Alignment Risk Scan is designed to surface: whether a leadership team can move from discussion to decision without blurring ownership along the way.
Healthy decision flow does not mean one leader makes every call alone. It means participation and authority are distinct.
The people closest to the work may have essential expertise. Functional leaders may see risks the decision-maker cannot. Stakeholders may need a real opportunity to challenge assumptions before the choice is made. But none of that requires shared final authority.
In fact, treating every important decision as a consensus exercise often creates the opposite of collaboration: vague ownership, delayed execution, and quiet second-guessing after the meeting ends.
Input is not ownership. Alignment is not unanimity. Discussion is not a decision.
The best teams make the ownership clear before the meeting starts. They specify what input is needed, who will make the call, and when the group will hear what was decided. That structure gives people a meaningful voice without turning every topic into a negotiation over who gets the last word.
A Meeting Redesign
Consider a weekly, 90-minute leadership operations meeting with ten people in the room. Every issue staffing, budget tradeoffs, customer escalations, launch timing gets discussed by the full group. Decisions are often deferred because everyone wants “a little more input.”
The team calls it collaboration. The calendar says otherwise.
A better design begins by assigning one accountable decision-maker to each agenda topic before the meeting:
Before
- Every topic is discussed by the full group Each topic has one named decision-maker
- The meeting tries to create consensus The meeting gathers defined input
- Decisions are often deferred The decision-maker closes or names the next required step
- Recaps record conversation A commitment tracker records the decision, owner, due date, and rationale
- The meeting runs 90 minutes every week The meeting is cut to 45 minutes, with fewer topics and clearer outcomes
After
- Every topic is discussed by the full group Each topic has one named decision-maker
- The meeting tries to create consensus The meeting gathers defined input
- Decisions are often deferred The decision-maker closes or names the next required step
- Recaps record conversation A commitment tracker records the decision, owner, due date, and rationale
- The meeting runs 90 minutes every week The meeting is cut to 45 minutes, with fewer topics and clearer outcomes
In this version, the VP of Operations may own the staffing call, the CFO may own the budget tradeoff, and the Chief Revenue Officer may own the customer escalation decision. Other leaders still contribute perspective. They are not excluded; they are no longer asked to pretend they jointly own a decision they do not actually control.
The result is not less collaboration. It is collaboration with a purpose.
Context Makes Decisions Stick
A decision does not become real when the meeting ends. It becomes real when the people affected understand what changed, why it changed, and what they are expected to do next.
That is why decision rights and communication structure belong together.
Too many teams announce the conclusion without the context:
- “We’re delaying the launch.”
- “We’re changing the staffing plan.”
- “We decided to prioritize the enterprise segment.”
Those statements may be technically clear, but they leave room for rumor, resistance, and re-litigation. A stronger communication pattern answers four questions:
- What did we decide?
- Who made the decision?
- What input informed it?
- What does this mean for the work now?
This does not require a memo after every conversation. It requires enough context that people do not have to reconstruct the decision from hallway conversations, Slack threads, or competing versions of the story.
McKinsey estimated that improving communication and collaboration through social technologies could raise the productivity of interaction workers by 20 to 25 percent. The point is not to add another platform. It is to build a communication structure that makes decisions visible, searchable, and actionable.
A Direct Self-Check
The question underneath the Decision Flow domain is simple:
When an important decision is on the table, does everyone know who will make the final call before the discussion begins?
Not after the meeting gets tense. Not when the deadline has already passed. Before the conversation begins.
Try this in your next leadership meeting. For each agenda item, write down one name next to the question: Who owns the decision?
If that name cannot be identified quickly or if everyone has a different answer, you have found the reason the meeting keeps returning.
This is domain 2 of 5 in the Team Alignment Risk Scan: Decision Flow. Next week, the series moves into the accountability gap and why “nobody takes ownership” is often evidence of a broken operating system, not a people problem.
Tools & Resources
- Commitment Tracker Template: A practical tool for documenting the decision, accountable owner, due date, key rationale, and follow-through required after the meeting.
- Team Alignment Risk Scan: In four minutes, identify where alignment risk may be concentrated across Strategic Alignment, Decision Flow, Execution and Accountability, Trust and Productive Tension, and Leadership Consistency. The scan is a risk diagnostic rather than a generic engagement survey, and it is designed to reveal where unclear decision rights may be slowing the team.