Leadership Altitude Switching
Move deliberately between hands-on execution and strategic perspective.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 96%
Leadership Altitude Switching is the practiced ability to move from strategic perspective into detailed individual-contributor work and back again. The leader does not remain permanently above execution or permanently inside it. Hands-on work preserves current vertical expertise, reveals changing tools and constraints, and grounds strategic choices in reality. The leader then returns to a higher altitude to connect those details to priorities, organization design, and longer-term direction. This differs from micromanagement because the purpose is not to control every task or make the team dependent on the leader. The mechanism works when altitude changes are selective, transparent, and followed by a return of ownership to the team.
Origin
Elena Verna named this capability while arguing that AI-native companies will have less use for managers who retain only horizontal oversight.
Core principles
- 01Preserve the ability to perform the team's craft.
- 02Move between detail and strategy rather than choosing only one.
- 03Use hands-on knowledge to improve strategic judgment.
- 04Avoid pure horizontal oversight detached from execution.
- 05Treat vertical expertise as a continuing leadership requirement.
How to run it
- 1
Define both altitudes
Specify the strategic responsibilities and the hands-on craft activities that belong to the role.
Pro tip Choose craft activities that expose the leader to current customer and workflow reality.
Watch out Vague expectations cause either total detachment or constant interference.
- 2
Descend into real work
Periodically complete, prototype, analyze, or design something using the same tools and constraints as the team.
Pro tip Select bounded work that produces direct learning.
Watch out Do not seize a teammate's project merely to prove expertise.
- 3
Extract operational insight
Identify what the detailed work reveals about customer needs, bottlenecks, quality, or emerging capabilities.
Pro tip Record observations before returning to strategic discussion.
Watch out Hands-on activity without reflection becomes random contribution.
- 4
Return to strategy
Translate detailed evidence into priorities, principles, resource choices, or organizational changes.
Pro tip Explain which strategic conclusion came from which operational observation.
Watch out Remaining in execution can make the leader another bottleneck.
- 5
Preserve team ownership
Share guidance and context while allowing individual contributors to retain control of their work.
Pro tip Ask whether your involvement increased team capability or dependency.
Watch out Repeatedly finishing the team's work is not altitude switching; it is dependency creation.
In the wild
A growth leader investigates a customer problem, writes an AI-assisted specification, and builds a lightweight prototype. After learning what is technically and experientially possible, the leader steps back and uses that evidence to set priorities while an engineer owns production delivery.
→ Strategy is grounded in current craft without turning the leader into the permanent implementer.
Common mistakes
Calling micromanagement craft
A leader who repeatedly overrides the team or dictates implementation is controlling work, not productively changing altitude.
Staying at one altitude
Permanent strategic distance weakens expertise, while permanent execution prevents the leader from providing direction.
Practicing obsolete workflows
Hands-on involvement only informs strategy when it uses current tools, constraints, and customer evidence.
Is it for you?
Best for
It is best for leaders in small, fast-moving, AI-native teams who must both shape direction and contribute directly.
Not ideal for
It is not ideal when a leader uses hands-on involvement to override owners, micromanage execution, or become a delivery bottleneck.
From the transcript
“if a person has lost the ability to change altitudes, I call it like changing altitudes as you're working, to where you can get into…”
“if you're talking about AI native companies, that vertical expertise becomes absolute necessity in what to do.”
From the episode
Inside the $130M AI Startup Growing Faster Than ChatGPT