When an organization grows from roughly 100 to 500 employees, it's not just scale that changes — it's the decision-making mechanism itself. What worked well at first — short lines, quick alignment, "just loop everyone in" — can flip into its opposite: more stakeholders, more meetings, more re-litigating mid-execution, and ultimately less execution power.
My observation (which I see repeated across many growth organizations) is simple but stubborn:
- Everyone gets to give input, so everyone gets involved.
- Decisions become slow, or stay "provisional".
- The same discussion resurfaces during execution ("did we actually decide this properly?").
- Teams compensate with extra governance, OKR rituals, roadmaps and alignment sessions.
- The core problem remains: the gap between strategy, decisions and initiatives.
This article translates that observation into a clear narrative, backed by research on group decision-making and practical governance insight on decision rights and accountability.
In small organizations, "consensus" is rarely an explicit process. It's a social reality: you sit close together, context travels naturally, and decisions feel relatively safe because everyone understands the trade-offs. As you grow, though, a structural effect kicks in:
- More interfaces (teams, layers, domains) → more dependencies
- More specialization → more valid perspectives, but also more friction
- More risk (reputation, compliance, customer impact) → more need for alignment
- More internal customers → more political dynamics around priorities
Consensus thereby shifts from "natural alignment" to an institutional reflex: input = involvement, involvement = buy-in, buy-in = safety. The problem: if nobody makes explicit who actually decides, the system becomes more inclusive and less decisive at the same time.
2) The hidden cost: decision delay and reopening mid-execution
Research on group decision-making reveals a tension that closely mirrors what you experience in growth organizations: groups can arrive at better judgments, but the process can also slow down and cause missed opportunities (Bang & Frith, n.d.; Hsieh, Fific, & Yang, n.d.; Berekmeri & Zafeiris, n.d.).
In practice, the pattern usually looks like this:
- The decision is made "in principle", but still carries exceptions and caveats.
- Execution starts because there's pressure to deliver.
- Friction or unexpected effects arise (always).
- People go back to the table: "we need to re-align on this."
- Delivery slips, scope shifts, ownership blurs.
Important: the problem is rarely unwillingness. It's usually ambiguity — what type of decision is this, who owns it, and which input is advisory versus decisive?
When "decisions" aren't made explicit, strategy comes back as a discussion — except now it's in the middle of execution.
3) Why "more governance" often makes it worse
When decision-making gets sluggish, organizations often reach for solutions that feel rational: extra steering committees, more alignment meetings, OKR cascades, stage gates, risk boards and RACIs. That can help — but only if it solves the actual gap: ambiguity in decision rights. Without clear decision rights, you mostly just create more places where the same discussions can resurface.
Practitioner literature on program governance and transformation risk names ambiguous decision-making as a direct delivery risk, and stresses that clarity on decision rights is critical to protecting execution (PwC, 2025).
4) The real gap: strategy ≠ decisions ≠ initiatives
Many growth companies have both strategy and initiatives, but are missing the connecting layer: concrete decisions that make trade-offs explicit. Without explicit choices, every project becomes an island. And every point of friction triggers the same discussion all over again — resulting in delay and frustration.
Examples of decisions that often stay implicit:
- Which segment gets priority when capacity is scarce?
- Where do we centralize, and where do we give autonomy?
- Which risks do we explicitly accept?
- Which trade-off wins: time-to-market or reliability?
Governance best practices therefore emphasize documenting decisions, making delegated authority explicit (delegation of authority), and sharply defining accountability (PwC, 2023; PwC, n.d.).
5) A workable alternative: from consensus culture to decision architecture
The goal isn't "less collaboration" or "hard top-down control". The goal is: faster, more consistent decisions while keeping the input that matters. That requires design:
5.1 Classify decisions (not everything is the same)
- Type A – Direction (strategy/policy): few, heavy, rare
- Type B – Trade-offs (priority/capacity): frequent, business-critical
- Type C – Execution (team choices): many, close to the work
5.2 Make input explicit: "consulted" is not "co-decider"
Don't just say who needs to be in the room — say who owns it, who advises, who gets informed, and when something is final.
5.3 Build a decision log as the backbone
A public (internal) register with: decision, date, owner, rationale, trade-off, and revision rules. This reduces re-questioning because the "why" is always retrievable.
5.4 Governance = deciding, or activating a decider
If a committee is mainly gathering opinions, make it advisory (and don't let it block anything) — or give it the mandate to actually decide.
Closing: execution power is a design choice
The core of the growth paradox isn't that people suddenly get worse at their jobs. It's that informal consensus doesn't scale. The solution, then, isn't "even more alignment" — it's an explicit decision architecture that organizes input without paralyzing decision-making.
- Consensus is a tool, not a default.
- Governance is a decision system, not a meeting structure.
- Strategy only works once decisions are traceable and repeatable.
References
Bang, D., & Frith, C. D. (n.d.). [Title unknown]. Royal Society Open Science.
Berekmeri, D., & Zafeiris, A. (n.d.). [Title unknown]. Cognitive Research: Principles and Implications.
Hsieh, M., Fific, M., & Yang, Y. (n.d.). [Title unknown]. Scientific Reports.
PwC. (2025, August 15). Three questions about program governance and delivery risk in transformation.
PwC. (2023, November 20). The eight key effective corporate governance practices.
PwC. (n.d.). Governance, Risk and Compliance (GRC).