The meeting ends. Everyone gets up, goes back to their desks, and keeps doing what they were doing before it started.
Nothing was resolved. Nothing was decided. The same issues that came up last week came up again this week. And somehow there’s another meeting on the calendar for Thursday.
The default diagnosis is that there are too many meetings. So the team cuts a few. The issues that used to surface in the meetings now don’t surface at all, which isn’t better. Or the meetings stay and everyone quietly resents the time they’re losing.
Neither fix works because neither addresses the actual problem.
The issue isn’t the number of meetings. It’s what the meetings are designed to do.
The Meeting That Feels Productive but Isn’t
Most meetings that don’t work have the same shape.
Someone shares an update. There’s some discussion. Another topic comes up. There’s more discussion. The hour ends and the team leaves with a general sense of what’s going on but nothing specifically resolved.
The meeting felt engaged. There was conversation. Things got raised. It doesn’t feel like a waste of time in the moment, which is part of why the problem persists.
But look at what actually happened. Updates were shared, which is information transfer. Issues were raised, which is problem identification. Discussion happened, which is information exchange. None of those things are decisions. The meeting produced activity without producing resolution, and the same issues will be on the agenda next week.
Five Signs Your Meetings Aren’t Working
The same issues surface every week. Not new issues. The same ones. Because raising an issue and resolving an issue are different things, and the meeting is set up to do the former but not the latter.
Decisions get “tabled.” Something gets raised that needs a call, and the response is “let’s take that offline” or “let’s revisit that next week.” Tabling is sometimes necessary. When it’s the default response to anything that needs a real decision, the meeting has no mechanism for making calls.
The founder is the only one making decisions in the room. Everyone else is presenting, discussing, and updating. The founder is deciding. Which means the meeting isn’t a team function. It’s a briefing for the one person whose approval everything needs.
Most updates could have been an email. Status on something that’s tracking normally. Numbers that are in the expected range. Progress that doesn’t require a decision or a conversation. When the majority of a meeting’s time is things that didn’t need a meeting, the meeting is filling time rather than using it.
Nobody leaves knowing what they’re doing next. The meeting ends and the next actions are unclear or unassigned. Everyone has a sense of what was discussed. Nobody has a specific thing they’re doing before the next meeting with their name on it.
Any one of these is a signal. All five means the meeting structure needs to be rebuilt, not reduced.
Status Updates Are Not Decisions
This is the core design problem in most team meetings.
Status updates tell people what’s happening. Decisions determine what happens next. They’re different activities and they require different things from the people in the room.
For a status update, you need to be present and paying attention. For a decision, you need the right people in the room, a clear picture of the issue, an understanding of the options, and someone with the authority to make the call.
Most meetings are built around updates. The format is: here’s what I’ve been working on, here’s where it stands, here’s what’s coming up. Then the next person goes. Then the next. An hour later, everyone knows what everyone else is doing and nothing has been decided.
The information transfer isn’t useless. But information transfer alone doesn’t move the business forward. Decisions do.
A meeting designed to produce decisions looks different. The format isn’t updates first. It’s issues first.
What a Meeting That Actually Produces Decisions Looks Like
The structural shift is simple, though it requires deliberate design.
Before the meeting, everyone contributes issues they need resolved. Not updates. Not progress reports. Issues: things that need a decision, a conversation, or an action that requires more than one person. The issues list becomes the agenda.
In the meeting, issues get worked one at a time. For each one: what’s the problem, what are the options, who decides. The decision gets made in the room, or gets assigned to a specific person with a specific deadline if it requires more information. Either way, the issue resolves or has a clear owner.
At the end, every issue on the list is either resolved or has a named next action with a named person accountable for it. Nobody leaves unclear about what’s been decided or what they’re doing next.
The meeting doesn’t run longer because it has more to cover. It often runs shorter, because the discussion is focused on resolution rather than information sharing that could have happened another way.
The Most Common Meeting Design Mistakes
Wrong people in the room. The decision that needs to be made requires someone who isn’t there. The meeting either stalls or makes a call without the person who should be making it.
No issues list. The agenda is a list of topics, not a list of things that need resolution. Topics prompt discussion. Issues prompt decisions. The distinction matters.
No format. The meeting flows from conversation to conversation without a structure that moves things toward resolution. Discussion happens. Decisions don’t.
No decision-maker identified. The issue gets discussed and nobody is clear on who actually makes the call. Discussion keeps going. The meeting ends with a sense that something was worked through but no actual decision made.
No accountable next action. Even when a decision is made, the follow-through isn’t clear. Who’s doing what, by when? Without that, decisions made in meetings don’t become things that actually happen.
What to Do With Issues That Can’t Be Resolved in the Meeting
Not every issue can be resolved in the room. Sometimes more information is needed. Sometimes the right people aren’t present. Sometimes it’s genuinely complex enough that it needs more time than the meeting has.
The answer isn’t to table it.
Tabling puts the issue back on the list without an owner or a deadline. It comes up again next week in exactly the same state. Nothing has moved. The cycle repeats.
The answer is to assign it. Who is responsible for getting this resolved before the next meeting? What do they need to do to move it forward? When will it come back to the group for a decision?
The issue doesn’t get resolved in this meeting. But it gets owned. There’s a person accountable for it and a timeline for resolution. That’s different from tabling, which is just deferral with a polite name.
When every issue either resolves or gets owned, the meeting is doing what it’s supposed to do.
Find Out What’s Slowing Down Decision-Making in Your Business
If your meetings are producing discussion but not decisions, it’s usually a symptom of a wider accountability and structure problem, not just a calendar problem. The Business Diagnostic Quiz helps identify where decisions are stalling in your business and what’s causing it.
