I’ve watched this pattern repeat across organizations of different sizes and industries. A team of eight people makes a decision in a meeting. The same decision, attempted by a team of eighty, takes weeks. The decision itself hasn’t become more complex. The organization has.
When I first noticed this, I assumed it was about process – that larger organizations simply had more formal approval layers. That’s part of it, but it’s not the main thing. The real friction emerges from something more fundamental: as organizations expand, the conditions that enable fast, confident decisions gradually disappear.
In smaller teams, everyone involved in a decision typically has direct exposure to the same information. A product manager, engineer, and designer sit near each other. They’ve heard the same customer complaints. They’ve seen the same data. When they meet to decide on a feature direction, they’re working from roughly the same mental model. The conversation moves quickly because gaps in understanding surface immediately and get filled in real time.
Information Becomes Fragmented
As an organization grows, people stop having overlapping exposure to the same facts. The product manager hears feedback from enterprise customers. The support team hears feedback from SMB customers. Engineering knows about technical debt that nobody else sees. Marketing has data on what messaging resonates. Each group has legitimate, real information – but it’s partial. Nobody has the complete picture.
When a decision needs to be made, the organization now has to surface and reconcile these different data sets. This isn’t trivial. A decision that seemed obvious to one group looks risky or wrong to another, not because anyone is being unreasonable, but because they’re literally working with different information. The process slows because the organization has to do the work of making sure everyone is operating from the same facts. Sometimes that work reveals that the facts themselves are contradictory or incomplete, which creates even more delay.
I’ve seen teams spend days assembling a decision brief that synthesizes information from five different departments. That brief is necessary. Without it, the decision-maker would be choosing based on incomplete information. But the time required to create it is a direct cost of scale.
Consensus Becomes Harder to Achieve
In a small organization, decisions often happen by rough agreement. People air their concerns, someone proposes a direction, and if nobody has a serious objection, the group moves forward. The social dynamics are tight enough that people understand the trade-offs being made and why. There’s usually enough trust that if something goes wrong, the group can adjust quickly.
Larger organizations can’t operate this way. When a decision affects multiple teams, each team has legitimate reasons to want input. The engineering team needs to know if a decision will create technical problems. The finance team needs to know the cost implications. The legal team needs to know if there are compliance questions. Each group’s concerns are real. But the more groups involved, the more potential points of disagreement.
What often happens is that decision-making becomes a negotiation process rather than a discovery process. Instead of a group working together to understand a problem and find the best solution, you get different factions advocating for their interests. The decision doesn’t get made when the best option becomes clear – it gets made when enough stakeholders have been convinced or appeased. That’s a slower, more political process.
I’ve noticed that organizations sometimes try to solve this by creating clearer decision rights. “The product team decides on features. The engineering team decides on architecture.” That helps, but it creates its own problems. Decisions that actually affect multiple domains get made in silos, and then people discover downstream that the decision created problems nobody anticipated.
Accountability Becomes Diffuse
In a small team, it’s clear who made a decision and who will live with the consequences. If the decision was wrong, everyone knows it, and the person responsible feels the feedback directly. That creates a strong incentive to decide carefully but also to decide quickly – because waiting doesn’t reduce the risk of being wrong, it just delays the feedback.
In larger organizations, accountability gets distributed across multiple people and layers. A decision might have been made by a committee, approved by a director, and implemented by a team that had some input but wasn’t the final decision-maker. If the decision turns out badly, it’s not clear who should have decided differently. That diffusion of accountability actually makes people more cautious, not less. If you’re not sure you’ll get clear feedback about whether your decision was right, you tend to want more certainty before you decide.
This shows up in how organizations handle decisions with uncertain outcomes. A small team might try an experiment, see if it works, and adjust. A larger organization often wants to be more confident before committing resources, which means more analysis, more stakeholder input, more delay.
Organizational Distance Creates Risk Aversion
There’s a structural issue that becomes more pronounced as organizations grow. When the person making a decision is close to the people affected by it, there’s a natural feedback loop. You see the impact. You adjust. You learn quickly what works.
When there’s distance between the decision-maker and the people affected, that feedback loop breaks. A director making a decision about a process that affects a team three levels down might not see the actual impact for months. By then, the decision is embedded in how things work, and changing it is expensive. This creates a rational incentive to be more cautious, to gather more information, to get more input before deciding.
I’ve seen organizations where middle management layers actually slow decision-making not because the managers are incompetent, but because they’re insulating senior leaders from the real impact of decisions. The senior leader makes a decision based on what they think will work. The middle manager knows it won’t work, but instead of just saying so, they have to build a case, gather data, and present it in a way that won’t make the senior leader feel second-guessed. That process takes time.
The Structural Reality
The hard truth is that some of this slowdown is inevitable. You can’t have a hundred people making decisions the same way eight people do. The information has to be coordinated. The stakeholders do need to have input. The accountability questions are real.
What I’ve observed in organizations that manage this better is that they tend to be explicit about which decisions need broad input and which don’t. They invest in making sure information flows quickly across team boundaries, not because it’s nice to have, but because decision speed depends on it. And they’re willing to accept that some decisions will be made with incomplete information, as long as the organization has the ability to adjust quickly if the decision turns out to be wrong.
The slowdown isn’t a sign that something is broken. It’s a sign that the organization has grown. How much friction that slowdown creates depends on whether the organization has adapted its decision-making structures to match its size.
