Leadership Sandboxes
Divide executive ownership clearly, then synchronize every week
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 92%
Leadership Sandboxes divide the company into explicit domains with a single senior owner for each. The founder keeps the areas where their contribution is existential; the operating leader owns the rest and receives genuine agency rather than nominal responsibility. The pair then spends at least an hour each week synchronizing across boundaries. At Tesla, Elon Musk owned product, engineering, and manufacturing, while McNeill took the remainder of the business. The mechanism works because clear decision rights reduce duplicate direction and micromanagement, while the recurring sync prevents independent domains from drifting apart. A sandbox is not isolation: it is bounded authority paired with regular alignment and mutual respect for who decides what.
Origin
McNeill and Musk adapted principles that Sheryl Sandberg and Mark Zuckerberg used to divide leadership responsibilities, calling the resulting domains sandboxes.
Core principles
- 01Clear ownership prevents executive overlap
- 02Each leader needs agency inside their domain
- 03Respect for decision rights builds speed
- 04A short recurring sync keeps divided work coherent
How to run it
- 1
Identify existential domains
Determine the two or three areas where the founder or CEO must remain directly involved.
Pro tip Base the choice on unique contribution, not title or habit.
- 2
Partition the rest
Assign every remaining major domain to another named leader so no important area has split ownership.
Watch out Shared accountability often becomes no accountability.
- 3
Set the boundaries
Clarify which decisions belong inside each sandbox and where consultation is required.
Pro tip Use recent disputed decisions to test whether the boundaries are clear.
- 4
Grant real agency
Let each leader run their sandbox without routine intervention from the other.
Watch out Responsibility without decision authority is not a sandbox.
- 5
Synchronize weekly
Meet for at least one focused weekly session to exchange context and coordinate cross-domain work.
Pro tip Discuss interfaces and exceptions rather than re-running every decision.
In the wild
Musk chose product, engineering, and manufacturing as the three areas he loved and needed to lead. McNeill took the rest of the business. They respected those boundaries and spent at least an hour together each week staying synchronized.
→ McNeill reports that the arrangement gave the team agency while the business grew from $1.8 billion to $20 billion in sales over 30 months.
Common mistakes
Drawing vague boundaries
If both leaders still believe they own the same decisions, the labels add no operating clarity.
Skipping the synchronization
Independent domains still interact. Without a recurring sync, local decisions can pull the company in conflicting directions.
Is it for you?
Best for
Founder-led companies adding a president, COO, or powerful functional leader.
Not ideal for
Teams where leaders lack the trust or competence to exercise independent decision-making.
From the transcript
“We called those sandboxes and we said okay this is your sandbox Elon it was product and engineering and uh manufacturing.”
“we would respect each other's sandboxes which was really good.”
“we spent at least an hour a week together catching up on those two things.”
From the episode
Episode 541: Jon McNeill: Why "Less" and "Simple" are the Smartest Growth Strategies
Jon McNeill