There is a particular kind of meeting that most teams recognise by feel long before they can name it — the one where a decision that should have taken twenty minutes has now occupied three separate sessions, generated a shared document with eleven versions, and still has no owner. The people in the room are not incompetent. The organisation is not badly led. What has happened, usually, is that the team has outgrown the invisible decision-making architecture it built when it was smaller, and nobody has yet noticed the scaffolding has been left behind. In five years of diagnostic work inside teams ranging from six-person early-stage ventures to divisions of several hundred, the same seven structural failure points appear with such consistency that they have come to feel less like accidents and more like laws. Understanding them does not require a restructure. It requires, first, the willingness to look at the map.

I. The founder's verbal approval, still embedded in the process ¶

At five people, every significant decision passes through one person. This is not dysfunction — it is appropriate. The founder or lead knows the context, carries the risk, and can be found in the next chair. The process works because the loop is short. But at twenty-five people, the loop has not been shortened; it has been stretched. The founder is now in a different city three days a week. The product manager who needs sign-off on a pricing change sends a Slack message at eleven-thirty on a Tuesday. It is read on Thursday. The team, not wanting to be seen as passive, begins filling in the gap with assumptions — and the decision is made, quietly, by the person with the most confidence and the least accountability. The verbal approval habit never died; it just became a ghost. What teams in this phase need is not permission to decide without the founder, but a written map of which decisions still require that approval and which have already, functionally, been delegated. The absence of that map is where the stalling lives.

II. Consensus as a default, mistaken for culture ¶

Consensus is not a decision-making method. It is an outcome that sometimes emerges from one. Teams that grew up in a collaborative, psychologically-safe environment — which is to say, the kind of team that reads all the right things about how to build good organisations — often arrive at fifteen or twenty people having quietly installed consensus as their default mode without ever choosing it. What this produces, in practice, is a pattern where any one person's hesitation is enough to delay a decision indefinitely. Nobody has veto power formally. Everybody has it informally. The delays are polite. The frustration accumulates beneath the politeness. A useful corrective is the DACI framework — Driver, Approver, Consulted, Informed — not because acronyms save organisations, but because it forces the uncomfortable question: who, specifically, makes the call when the consulted parties disagree? Naming the Approver is the move that teams in consensus culture most resist, and it is almost always the move that most needs making.

III. The information asymmetry nobody has mapped ¶

A decision stalls when the person who must make it does not have the information required, and the person who has the information does not know a decision is pending. This sounds elementary. It is, in practice, the most common single cause of delay that surfaces in diagnostic interviews — more common than unclear ownership, more common than conflict, more common than resource constraints. At thirty people, the sales lead knows the client's actual budget ceiling. The product director does not. The product director is being asked to prioritise a feature that the sales lead knows, from a conversation last week, the client no longer wants. The feature goes through two weeks of specification before anyone discovers this. The asymmetry was not malicious. The information existed; it simply had no route to the decision point. Building routing — which means deciding, explicitly, which information classes must travel to which decision-makers before a given class of decision can proceed — is unglamorous work. It does not produce a new strategy deck. It produces, instead, meetings that end with something decided.

IV. The role that grew without its authority growing with it ¶

This is among the subtler failure points, and the one that produces the most sustained personal frustration inside growing teams. A person joins at eight people as the Head of Operations. At that scale, head of operations means you do most things and make most calls. The title implies authority that is never formally stated because, at eight people, formal statements feel unnecessary. The organisation grows to thirty-five. The Head of Operations is still making the same class of decisions — vendor contracts, process changes, tooling — but now three other leads sit in the same tier, and there is no written record of what the Operations role is actually authorised to decide. So decisions that this person makes begin to be questioned, not out of bad faith, but because nobody agreed on the scope. The Head of Operations starts seeking approval they never needed before. The leadership layer starts fielding approvals they never intended to handle. Both parties are acting rationally within a structure that has simply never been written down. Writing it down — role by role, decision class by decision class — takes a half-day. Teams routinely defer it for eighteen months.

V. The cross-functional decision with no natural home ¶

As teams grow, the decisions that matter most are increasingly the ones that live between functions rather than inside them. A pricing change is simultaneously a finance decision, a product decision, a sales enablement decision, and a customer success decision. At twelve people, the person who calls the meeting is, implicitly, the owner. At forty people, four leads sit around the table, each with a legitimate stake, none with clear authority over the others. The meeting ends with an action item to schedule a follow-up. The follow-up surfaces a new dependency. The decision ages. These cross-functional decisions do not stall because organisations are indecisive. They stall because no one has answered the prior question: for decisions of this type, which function is the tiebreaker? Not the loudest voice, not the most senior title, but the designated owner. In most diagnostic conversations, the answer to this question has never been discussed — not because it is controversial, but simply because the scenario had not yet occurred when the team was smaller, and no one thought to pre-answer it before it did.

VI. The documented process nobody has touched since the Series A ¶

Growing organisations develop process documentation in bursts — usually around funding rounds, audits, or the arrival of a new operations-minded hire. The documents are accurate at the moment of writing. They then age, invisibly, as the organisation around them changes. At forty people, a team will frequently have a hiring approval process written for a fourteen-person company, a budget sign-off matrix calibrated for a different financial structure, and a product roadmap review cycle inherited from a time when the CTO attended every meeting. The documents are not wrong, exactly. They are misaligned — and people know it, which means they partially follow them, partially improvise around them, and are never quite sure which parts still apply. The result is a kind of procedural fog: nobody wants to go entirely off-script, nobody wants to follow a script that no longer fits, and decisions orbit the documented process without ever landing cleanly inside it. A half-yearly process review — not a wholesale rewrite, but a structured walk through each documented process to confirm current validity — dissolves this fog faster than almost any other single intervention.

VII. The delay built into the calendar ¶

The final stall point is the one most often overlooked because it wears the costume of good governance. Leadership teams that meet fortnightly to review major decisions will, structurally, delay every decision that arrives between meetings by up to two weeks. This is not a cultural problem or an authority problem. It is a calendar problem — and it multiplies. If a decision requires input from the leadership team, and the leadership team meets every other Thursday, and the decision arrives on a Friday, and the following Thursday agenda is already full, the decision is now three weeks old before it is first discussed. Teams in diagnostic work often express frustration with their own slowness without realising they have engineered that slowness into their meeting structure. The remedy is not more meetings; it is a tiered decision cadence — identifying which decisions can and should wait for a scheduled review, which should trigger an asynchronous approval within forty-eight hours, and which require a brief, unscheduled call with the two or three people who matter. Building that tiered cadence takes, in practice, about ninety minutes of focused design work. Most teams have not done it.

None of these seven points require an organisational redesign to address. Each one requires, instead, a willingness to make explicit what has been operating, silently and imperfectly, as implicit structure. The organisations that move quickly at forty people are not the ones that hired the fastest or built the most sophisticated systems. They are the ones that, at some point, sat down and drew the map — named the owners, wrote the thresholds, retired the outdated documents, and built a calendar that matched the pace at which the real work needed to move. The map is not complicated. The sitting down is the hard part.