Decision-Layer Scaling Model
Move decisions outward as teams grow while preserving alignment and guardrails.
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 94%
The model describes leadership scaling as a progression in where decisions are made. With roughly one to thirty people, the leader can make most decisions and remain the central source of truth. Around thirty to seventy people, direct reports must increasingly decide, requiring the leader to establish guardrails, trust, aligned goals, and cross-team coordination. Beyond roughly seventy people, the teams beneath those direct reports make many decisions, so informal knowledge and direct supervision stop working. The leader must then build systems that preserve alignment across layers. The numbers are directional rather than absolute; the reusable mechanism is to move authority outward as complexity grows while replacing personal control with clear goals, decision rights, and coordination structures.
Origin
Kieran Flanagan used team-size stages to explain leadership transitions on Marketing Against The Grain.
Core principles
- 01The appropriate source of decisions changes as an organization grows.
- 02Small-team leaders can act as the primary source of truth.
- 03Middle-stage leaders must equip direct reports to decide within clear guardrails.
- 04At greater scale, the teams beneath direct reports must make decisions.
- 05Delegation without aligned goals and cross-team mechanisms creates friction and confusion.
How to run it
- 1
Locate the current stage
Estimate whether most decisions are made by the leader, direct reports, or the teams beneath them.
Pro tip Use actual recent decisions rather than the organization chart.
Watch out Nominal delegation may differ from where approval really occurs.
- 2
Expose the bottlenecks
Identify decisions that wait for a leader who no longer needs to make them.
Pro tip Review delayed projects and repeated approval requests.
Watch out Do not decentralize pivotal decisions without capable owners.
- 3
Define guardrails
Give direct reports clear goals, constraints, budgets, and escalation conditions.
Pro tip Specify what can be decided without consultation.
Watch out Telling people to own decisions without boundaries creates uncertainty.
- 4
Align across teams
Resolve conflicting goals and create mechanisms for decisions that span functions.
Pro tip Assign a single accountable owner for cross-team decisions.
Watch out Local optimization can damage the broader organization.
- 5
Push authority outward
Move routine decisions to direct reports and then to their teams as capability grows.
Pro tip Delegate categories of decisions rather than isolated tasks.
Watch out Repeatedly overruling delegated decisions teaches teams to wait for approval.
- 6
Change the leader's work
Shift attention toward priorities, organizational gaps, resources, and system-wide alignment.
Pro tip Measure whether decisions continue moving when the leader is absent.
Watch out A leader who keeps operating like the head of a ten-person team will constrain a larger organization.
In the wild
A marketing leader who once approved every campaign now manages fifty people. They establish channel goals, budget limits, and escalation rules so direct reports can approve campaigns independently.
→ Routine decisions accelerate while the leader retains oversight of consequential exceptions.
At eighty people, functional leaders cannot personally arbitrate every program choice. Teams receive shared goals and explicit decision rights, while cross-team conflicts move through a defined coordination process.
→ Decision-making continues across multiple layers without relying on executive omniscience.
Common mistakes
Delegating without guardrails
Authority without goals, constraints, and escalation rules produces inconsistent decisions rather than healthy autonomy.
Keeping conflicting goals
Teams will optimize for themselves when their objectives are not aligned with one another.
Remaining the source of truth
A leader who continues making every decision prevents the next layer from developing judgment and capacity.
Is it for you?
Best for
Founders and functional executives whose teams are growing from tens to hundreds of people.
Not ideal for
Small stable teams where additional management layers and distributed decision rights are unnecessary.
From the transcript
“when you're in the one to 30 zone, you make all the decisions, right?”
“your job becomes how do I get my team to be able to make the decisions, right? How do I actually set guardrails and have…”
“And then you have like the 70 to let's say 150, 200 where your direct reports teams make the decisions.”
From the episode
Are You a Simplifier or a Complexifier? (The Power of a Great 2x2)