- STAGE
- Early Scale Stage
- ORIENTATION
- Roughly $50M-$100M / Typically 100-200 employees
- NAME OF THE GAME
- Decentralize It
- MASTERY TARGET
- Distributed Authority
- FOUNDER ROLE
- Enterprise CEO: set context, boundaries and review outcomes
- DOCTRINE
- Know which game you are playing before you decide what advice to follow.
Your Company Has Leaders. Do They Have Authority?
An Early Scale company can look professionally managed. There is an executive team. There are functional leaders, operating systems, dashboards, budgets and management layers. Yet a pricing exception appears and someone asks what the founder thinks. A key hire reaches the final stage and the decision pauses. Two functions disagree and the issue travels upward. A leader makes a defensible decision the founder would have made differently, and everyone watches to see whether it gets reversed.
This is one of the defining tensions of the Early Scale Stage. Capability has been built, but authority has not fully caught up. People may be responsible for results while the decisions that shape those results still travel upward.
The Decentralize It game is won when capable leaders can make consequential decisions inside clear context, limits and escalation rules, own the consequences and learn from outcomes without using founder approval as the default integration mechanism.
ASK ATHENA WHERE AUTHORITY STILL LIVES
Tell Athena what decisions still come upward, who is accountable for the outcome and what happens when a leader chooses differently from you.
What Winning This Game Means
Distributed Authority is behavioral. A title, org chart, delegation memo or business-unit structure does not prove authority has moved.
Authority has moved when capable leaders make consequential decisions inside clear boundaries without routine founder approval, including decisions about pricing, hiring, spending, operating tradeoffs and resource use that genuinely belong to their accountability.
What Management Must Accomplish at This Stage
- Match accountability with meaningful authority.
- Define what stays with the founder, CEO or board and what explicitly belongs to executives, functions or units.
- Move economic authority with operating accountability so leaders can affect the outcomes they own.
- Separate enterprise standards from local discretion.
- Create cross-unit integration mechanisms so autonomy does not become fragmentation.
- Review decisions and outcomes without turning every review into an approval session.
- Build succession and leadership depth before vacancies create urgency.
Problems and Stall Signals That Often Show Up Here
- Executives own outcomes but still need founder approval for the decisions that shape them.
- The founder retains an expanding preference-based veto list that no one can clearly describe.
- Cross-functional or cross-unit disagreements still route to the CEO.
- Business reviews become approval meetings rather than outcome and learning reviews.
- Local leaders have responsibility without pricing, hiring, spending or operating authority.
- The same delegated decision is repeatedly reopened without new evidence.
- Leaders wait for founder alignment because the operating cadence has trained them to do so.
Founder Experiences That Often Show Up Here
The Early Scale Stage often turns structural authority questions into deeply personal founder experiences. These moments are not exclusive to this stage, but their consequences become larger here.
- Decisions Return to the Founder: formal delegation exists, but consequential ambiguity still travels upward.
- Delegated Responsibility Migrates Back: responsibility was transferred, then reclaimed through revision or rescue.
- Senior Leadership Cannot Remove Founder Dependency: executive titles exist, but the decision architecture remains founder-centered.
- Different Stops Meaning Wrong: a capable leader makes a defensible decision the founder would not have made.
- Genuine Founder Absence Becomes Proof: the organization handles consequential work well without the founder.
- Being Needed Becomes Part of Personal Value and Pride in a Result Not Personally Produced: identity must catch up with the new architecture.
Which of these sounds most familiar?
Select a problem to read its canonical description. These are characteristic stage problems, not claims of statistical prevalence.
Strategies and Tactics That Fit Now
Consequential Decision Inventory
Map the recurring consequential decisions that shape results, not every small decision. Name the owner, required inputs, boundaries and escalation conditions. The goal is a manageable decision architecture, not bureaucracy.
Accountability-Authority Audit
For each executive or unit outcome, ask whether the leader controls enough pricing, hiring, spending, operating or resource decisions to be genuinely accountable. Accountability without authority produces escalation and learned helplessness.
Founder Reserved Decision Set
Define the small set of decisions that genuinely remain with the founder, CEO or board. Keep the set principle-based and stable. An expanding preference-based veto list means decentralization has not happened.
Executive or Unit Charters
Clarify the result, decision classes, economics and boundaries a leader owns. A charter cannot fix weak capability, but it can make legitimate authority visible once capability exists.
Center-versus-Local Boundary Map
Where the company has multiple units or locations, distinguish enterprise standards that preserve coherence from choices local leaders should own. Uniform policy is not the same as enterprise alignment.
Cross-Unit Integration Design
Normal conflict should resolve laterally or inside designed forums. If ordinary interdependence keeps routing to the CEO, the integration mechanism is still too founder-dependent.
Delegated Economic Authority Matrix
Align spending, pricing, hiring and capital thresholds with accountability and reliable financial controls. Authority without economic visibility creates risk. Accountability without economic authority creates escalation.
Monthly Business Review, Quarterly Strategy/Resource Review and Escalation Review
Use reviews to examine outcomes, assumptions, exceptions and resource movement. Review should not become approval. Track recurring escalations as system evidence. If the CEO stopped attending a forum, the designated leaders should still know what they are authorized to decide.
Decision Relitigation Review
Inspect decisions that repeatedly reopen without new evidence. A different preference is not new evidence. Non-revision discipline is part of building legitimate distributed judgment.
Wrong-Game Advice to Reject
- Decentralizing before Growth-stage Organizational Capability is dependable.
- Creating Mature Scale governance machinery to solve an Early Scale authority problem.
- Centralizing decisions simply because corporate leadership has more experience or better analytics.
- Using charters and matrices to mask weak executive capability.
- Treating every escalation as a people problem when the real issue is unclear authority or founder override.
How You Know You Are Winning
- Leaders can describe the outcomes, decisions, economics and boundaries they own.
- Authority matches major accountabilities.
- Recurring upward decisions decrease because escalation rules are clearer.
- Cross-unit conflict resolves laterally or in designed forums.
- Monthly reviews focus on outcomes and learning rather than securing founder approval.
- Important delegated decisions are not routinely reopened because the founder would have chosen differently.
- Founder absence increasingly becomes proof that the architecture is working.
What Opens Next
Once Distributed Authority is dependable, the developmental problem changes again. The enterprise must continue to perform, adapt, allocate resources and renew leadership beyond dependence on any one executive without allowing discipline to harden into bureaucracy.
That is the Mature Scale Stage. The next game is Institutionalize It. The next mastery target is Institutional Maturity.
Ask Athena About This Stage
Go Deeper
Use the Early Scale Stage Playbook for the complete authority field guide. Read The Founder’s Trap for Capability, Authority and Identity mechanisms and The Founder’s Compass when the issue is what principles should govern delegated authority.
THE FOUNDER’S GAUNTLET
See how Organizational Capability becomes Distributed Authority and how each gate changes the founder’s job.