Your leadership team meeting is holding your startup back

Picture the regular leadership team meeting. Each function takes its turn. Engineering reports where the build has got to, sales runs through the pipeline, finance walks the numbers, operations flags what is stuck. The founder listens, asks a sharp question here and there, and nods the room along. Everyone leaves informed.

It was a well-run reporting session. It was not a team deciding anything.

Last week's note argued that a set of functional heads each reporting to the founder/CEO is not yet a leadership team but a hub-and-spoke management model: the founder as the one point every cross-functional decision has to pass through. This week is about the single forum where that structure is either replaced or unwittingly reinforced: the leadership team meeting, and what it is actually for.

Here is the most uncomfortable part first. The meeting most founders run, with each head reporting progress to the founder in turn, does more than eat time. It reinforces the hub-and-spoke structure, meeting after meeting, in plain sight. And because it looks so much like worthy diligence, it is almost impossible to see as the problem.


The most natural meeting is the trap

The default agenda is the status update: each function reports its progress, in turn, to the person at the centre. It is the most natural meeting to build, because it mirrors how a hub-and-spoke company already works. Functional heads may already be resolving day-to-day issues between themselves, but the big cross-functional choices, the ones whose company-wide impact demands real debate, still travel up to the founder for resolution.

The shape gives itself away in where the talk flows. Each head addresses the founder, not the table. Two functions with a dependency between them do not resolve it in the room; they each report their side to the hub and wait for it to be reconciled afterwards. The meeting runs its course, everyone is updated, and not one decision that needed the whole team has been made by the whole team.

That is the tell. A real team, in Katzenbach and Smith's distinction, produces something none of its members could alone. A status update produces a sum of updates. It can run flawlessly for years and never once ask the group to be a team, because it never puts a cross-functional decision on the table for the group to own.


The room trains everyone to defend a lane

There is a subtler cost, and it is the one that does the real damage. This kind of meeting quietly teaches each attendee the wrong job.

If the meeting exists so that you report your function's progress, then your task, walking in, is to arrive with a clean account of your function. You prepare to show that engineering is on track, that the pipeline is healthy, that the burn is under control. You are, in effect, preparing to justify your existence. So is everyone else. And a room full of people each defending their own lane is the exact opposite of a team working a problem together. Everyone is so occupied with their own turn that no one truly engages with anyone else's.

This is what Lencioni meant when he called the polite, conflict-free meeting a kind of artificial harmony: the disagreement that should happen in the room gets suppressed, and then resurfaces later in the corridor, as politics. The status update does not merely fail to build the team. It actively trains the behaviour that keeps the team from forming.


Unpreparedness is not a lapse - it is what the format taught

So, when the trade-offs that decide a company's direction never get made together, the instinct is to blame the people. They are not senior enough. They did not come ready. But they came ready for the meeting they were given.

Nobody arrives prepared to argue and settle a cross-functional trade-off, because the room has never once asked them to. In a hub-and-spoke management structure, those trade-offs were always resolved afterwards, by the founder, one spoke at a time. The team has had no reason to build the muscle, because the founder's own centrality quietly removed the need for it. Unpreparedness to decide together is not a failing of the individuals. It is the faithful product of the structure they have been working inside.

Which is why the fix is not a better agenda, or more frequent meetings, or a rule that they start on time. Those are real, but they are surface. The change that matters is in what the forum is for. A meeting built to make decisions demands a kind of preparation a status update never asked for, and it is that demand, not the discipline, that begins to forge the team.


Push the reporting into writing, and free the room to decide

The practical move is the one the best operators converge on. Take the status reporting out of the meeting and put it in writing, circulated and read before anyone sits down. Then spend the time you reclaim on the decisions that need the whole team present.

The effect on preparation is immediate. When the meeting is where the cross-functional calls get made, people arrive having done the thinking, because they are no longer filing a report; they are advancing the decisions that unblock their own work. Some founders circulate the recommendations ahead for a pre-read; others hold a few minutes of silent reading at the top so nobody free rides on having skipped it. Either way, everyone is preparing in the sense that matters, even if not everyone brings a decision every time.

This mirrors a discipline we set out in the board series: send the pack early and refuse to recite it. That was about signalling command upward, to your investors; this runs the other way, a forum built to make the team decide laterally, among peers. The mechanic is the same. Written word for the information; live time for the judgement.


Not every decision belongs in the room

But load the meeting with every day-to-day decision and it fails just as surely, so be clear about which decisions the forum is for. A good operating rule is cross-functional impact: a choice that reaches across functions is what the leadership team exists to make together, because no single head can make it well alone.

The most common of these, and the one that most animates functional heads, is the setting and resetting of priorities: whose work comes first when the quarter is overloaded, and what gets dropped to make room. Reallocating people and money is usually where the impact really bites and where the trade-offs need frank and honest debate.

One special kind of proposal should be among the most important the forum debates: the founder's own. When you intend to take a recommendation to the board, bring it here first and let the leadership team stress-test it. A proposal that has survived the judgement of your own senior staff arrives at the board tested, not hopeful. And the bonus? The team learns how the biggest calls get shaped.


What the founder is actually learning to do

Underneath all of this sits the skill nobody warned the founder they would need. A first-time, often deeply technical founder has spent years running vertical, one-on-one conversations - mostly founder to engineer in the early stages. Chairing a room where peers argue a trade-off to a conclusion is a different craft entirely, and most have never had to build it.

The chair's job is not to keep the peace. It is to draw out the disagreement people would rather avoid, because that debate is where the decision gets pressure tested. And when the argument does not resolve itself - when the debate is genuine and no clean answer emerges - the chair decides, in the room, in front of everyone. This is not decision by committee, and it is not consensus. Everyone is heard; then a decision is made and owned by the whole team. And how you make it is being watched: the team is reading not just what you decide but how you decide it.

That last move draws on the principle Andy Grove built into Intel's decision culture: once a call is made, those who argued against it are as bound to its success as those who argued for it. The disagreement is a duty before the decision and a debt after it. A room that can do this - argue hard, decide clearly, leave committed - is a team. A room that cannot is still a hub-and-spoke assembly, whatever the org chart says.

The real test of the chair is the meeting that runs without them. When you are away for a week, a healthy team settles what it can and lets only the few genuinely founder-level calls wait, rather than storing every decision up for your return. A room whose members are accountable to each other, not each to you, does not fall silent when your chair is empty.


The room where the culture is set

A founder who builds this forum discovers an additional payoff they never designed. When the leadership team watches you weigh a genuine trade-off - which company value wins when two collide, what the company vision demands when the easy path runs the other way - they are seeing the culture in action. They carry what they see back into their own teams and decide the same way. The forum where decisions get made is where the culture is most visibly practised, and it cascades from there or not at all.

So, the questions to ponder are not about your agenda. When two functions collide, is the choice made together in the room, or brought to you alone after the meeting? When the debate stalls, does anyone chair it to a close? And when your people leave the room, having lost an argument, do they leave committed, or do they leave to reopen it in the corridor?

If the forum only ever reports to you, you have not been running a leadership team. You have been holding the spokes in place, one meeting at a time. The work is not to change the agenda. It is to change what the room is for and let the team you wanted become the team the company needs.

This is the second of three notes on building a leadership team that runs without you at its centre. The last turns to the hardest part: getting the right senior people into the right seats, and the hard truth that not everyone who got you here should keep their seat as the company grows.

Let's talk.