It usually starts around the forty-five minute mark.
The last department head finishes their update. A few follow-up questions get asked. Someone raises a topic that probably deserves its own conversation. The founder makes a few observations. There is a general sense that everyone is now more informed than they were an hour ago.
Then the meeting ends.
Nobody writes down what was decided, because nothing was decided. Nobody assigns a next step, because the meeting was not structured around next steps. Everyone goes back to their desks with a slightly fuller picture of what is happening across the company, and absolutely nothing has changed about what they are going to do today.
This is the status update meeting. And it is the default format for leadership meetings in most founder-led companies, often without anyone realizing it has happened.
The problem is not that the people in the room are incapable of making decisions. The problem is that the meeting was never designed to produce them.
Nobody sits down and says "let us design a meeting that produces no outputs." Status update meetings evolve naturally from a reasonable instinct: founders want to know what is happening across the company, and gathering the leadership team in one place to find out feels efficient.
In the early days it is efficient. When the company is small and the founder is genuinely uninformed about what each department is doing, a round of updates provides real value. Everyone gets context. The founder can course-correct in real time. The meeting earns its place on the calendar.
Then the company grows. The founder becomes more informed between meetings, through Slack, one-on-ones, and shared tools. The round of updates starts to cover ground the founder already knows. But the format stays the same, because formats are sticky and nobody has explicitly named what the meeting is supposed to produce.
By the time the meeting has become a problem, it has also become a habit. Department heads prepare updates because that is what the meeting requires. The founder listens and asks questions because that is what the meeting invites. The structure shapes the behavior, and the behavior reinforces the structure.
Breaking it requires naming it first.
It is not always obvious from the inside. Here are the clearest signals.
The preparation is a summary of the past week. If everyone walks in having prepared a recap of what their team did since the last meeting, the meeting is oriented toward the past. A decision-making meeting requires preparation oriented toward the future: what needs to be decided, what is blocked, what options are on the table.
The founder talks the most. In a well-functioning leadership meeting, the facilitator asks questions and the team provides answers, debates options, and reaches conclusions. When the founder is doing most of the talking, the meeting has become a forum for one person to think out loud while everyone else listens. That is not a leadership meeting. That is an audience.
The same topics come back week after week. When a topic recurs across multiple meetings without resolution, it is a sign that the meeting is surfacing issues without resolving them. Discussion is happening. Decisions are not. The topic returns because nothing changed after the last time it was raised.
There are no notes because there is nothing to note. If the meeting ends and nobody feels compelled to write down what happened, it is because nothing happened that needed recording. Decisions generate notes. Status updates generate memories that fade by Thursday.
The shift is structural, not cultural. You do not need a different team or a different founder. You need a different format.
A leadership meeting designed to produce decisions has three characteristics that a status update meeting lacks.
It is organized around open questions, not department updates. The agenda is built around what the team needs to decide or unblock this session. Not around who reports first, second, and third. Each item on the agenda is a question that the meeting is expected to answer: should we extend the sales hire deadline, what is blocking the product launch, how do we respond to the pipeline shortfall in Q3. Questions have answers. Updates do not.
Progress review happens before the meeting, not during it. When goal tracking is visible to everyone in a shared system, the meeting does not need to spend time on information transfer. Everyone arrives already knowing where things stand. The meeting picks up from that shared baseline and immediately focuses on what it means and what to do about it.
This is the single biggest structural change most leadership teams can make. Moving status out of the meeting and into a shared tracking system recovers thirty to forty minutes per session and redirects that time toward the conversations that actually move things.
Every agenda item ends with a named owner and a deadline. Not a plan to discuss further. Not an action to follow up on. A specific person who owns the next step and a specific date by which it will be done. This takes discipline in the moment, especially when a conversation is still warm and it feels premature to close it. But an open conversation with no owner produces no output. A closed decision with a clear owner produces accountability.
The cost of a bad leadership meeting is not just the hour it takes. It is everything downstream.
When decisions do not get made in the leadership meeting, they get made elsewhere. In one-on-ones between the founder and individual department heads. In Slack threads that half the team sees and half does not. In informal conversations that produce commitments nobody else knows about. The decision still happens, but it happens outside the structure that was designed to hold it.
This creates two problems. The first is inconsistency: decisions made in different places with different information produce outcomes that do not align. The second is invisibility: when decisions are made in scattered conversations, nobody has a complete picture of what has been agreed. The founder often ends up as the only person who holds the full thread, which is precisely the bottleneck most founders are trying to escape.
A leadership meeting that consistently produces decisions reduces the volume of scattered decision-making happening outside it. It centralizes the outputs that matter most and makes them visible to the whole team. Over time it builds a culture where the meeting is the place where things get resolved, not the place where things get reported.
That shift is worth more than it sounds. It is the difference between a leadership team that needs the founder to function and one that can execute independently.
Most founders know their meetings are not working as well as they should. Naming the problem is not the hard part.
The hard part is that whoever runs the meeting is also in the meeting. When the founder facilitates, they are simultaneously trying to manage the conversation, contribute to it, and track whether outputs are being captured. Those roles are in tension. The facilitator needs to stay neutral and keep the agenda moving. The founder needs to weigh in on decisions. Trying to do both at once means doing neither well.
This is why the same meeting problems recur even when founders have read the books, restructured the agenda, and started the meeting with good intentions. The structure is right but the facilitation is compromised by the fact that the person running the meeting has skin in every outcome being discussed.
An outside facilitator removes that tension entirely. The meeting runs to structure. The founder participates as a decision-maker, not a moderator. The outputs get captured by someone whose only job in the room is to make sure the meeting produces them.
It is a small change with a disproportionate effect on what the meeting actually achieves.
FounderMove facilitates bi-weekly leadership sessions so every meeting ends with decisions made, next steps owned, and nothing left for the founder to chase down afterward.
.jpg)
