Managing managers is a different job than managing individual contributors. The skills that made you effective as a direct manager - close oversight, hands-on problem-solving, high personal involvement in decisions - actively undermine you when your team is a layer of managers rather than a team of ICs. The transition requires deliberately unlearning behaviors that were rewarded at the previous level.
The failure pattern I see most often is executives who intellectually understand they need to empower their managers but operationally can't let go. They sit in every meeting. They override decisions. They jump directly to their managers' reports when something goes wrong. Each of those behaviors signals to the manager that they don't actually have authority, which means every decision gets escalated rather than made.
Why Strong ICs Struggle to Step Back
High-performing individual contributors get promoted to manager because they're excellent at the work. They get promoted to executive because they're excellent at managing the work. At each transition, the behaviors that drove success at the previous level become less relevant and sometimes actively counterproductive at the new level.
At Spark Networks, managing a product and growth organization across multiple dating platforms during a period of significant operational change, the challenge wasn't getting the work done - it was getting it done through managers who were still developing their own judgment and confidence. The temptation was to stay involved in the operational details I understood well. The discipline was identifying which decisions required my judgment and which ones required my managers to develop theirs.
Every decision you make that your manager could have made is a decision that didn't develop their judgment. Empowerment is not about trust - it is about deliberately creating the conditions where your managers build the capability you need them to have.
Six Principles for Empowering Without Losing Control
1. Explicit scope, not implicit trust
'I trust you' is not a scope definition. Trust is table stakes. Scope is the specific decisions and outcomes your manager owns without escalation. Until you have written, explicit scope definitions - including what's in scope, what's out, and what requires consultation - your managers are operating on assumption. Assumptions generate escalation.
2. Let small misses happen
Protecting your managers from every minor mistake is one of the most common ways executives undermine the managers they're trying to develop. A manager who never makes a recoverable mistake never develops the judgment that comes from being wrong and working through it. Your job is to calibrate the risk tolerance - not to prevent all failure, but to ensure the failures that happen are recoverable and instructive.
At PermissionTV, where I ran product for clients including Fox, MGM, and The Metropolitan Museum of Art, we had to develop junior PMs quickly because the client work demanded it. The approach was deliberate exposure to progressively higher-stakes situations, with close enough oversight that recoverable mistakes happened but catastrophic ones didn't. The managers who came out of that environment were significantly more capable than ones who had been protected from failure.
3. Coach on context, not just content
When your managers come to you with a problem, the reflex is to solve it. The better move is to transfer the context that would allow them to solve it themselves. What are the constraints they don't know about? What has been tried before? What does leadership care about that isn't obvious from the problem statement? That context transfer is what builds the judgment your managers need to make better decisions independently over time.
When a manager brings you a problem, ask yourself: do they need the answer, or do they need the context to find the answer themselves? The first builds dependency. The second builds capability.
4. Inspect what you expect, consistently
Regular check-ins are not micromanagement. They are the mechanism by which you know whether empowerment is working. The check-in should be focused on outcomes and blockers - not task status. 'Are you on track for the Q2 retention goal? What's getting in the way?' Not 'walk me through what you've been working on this week.'
5. Celebrate publicly, correct privately
New managers crave feedback but rarely ask for it directly. The public celebration of wins - in team meetings, in company updates, in 1:1s with your own leadership - signals to the organization that your manager has authority and your backing. That signal is more valuable than you think, because organizations are extremely good at reading where the real power sits and adjusting their behavior accordingly.
Corrections belong in private. A manager who gets corrected publicly in front of their team has lost authority that takes months to rebuild. The discipline is separating the developmental conversation from the performance signal the organization is watching.
6. Protect your own strategic capacity
You can't lead strategically if you're operationally involved in everything your managers own. Protecting your strategic oxygen means being ruthless about which meetings you attend, which decisions you stay involved in, and which escalations you accept. If your calendar is full of your managers' operational problems, you're not doing your job - you're doing theirs.
How This Shows Up in Practice
The most common failure pattern: a VP of Engineering who was a hero IC gets promoted to a director role managing three engineering managers. He stays deeply involved in technical decisions because that's where he adds value and he knows it. His managers stop making technical decisions because they've learned he'll override them anyway. Every technical decision escalates to him. He becomes a bottleneck. He works 60-hour weeks and wonders why his team isn't developing.
The fix isn't a conversation about empowerment. It's a structural change: explicit scope definitions for each manager, a deliberate withdrawal from technical decision involvement over a defined period, and check-ins focused on outcomes rather than technical choices. Three months of that pattern and the managers start making decisions. Six months and the VP has time to think about the next 18 months instead of just the next sprint.
| Mistake | Why It Happens | Better Move |
|---|---|---|
| Swooping in to solve every issue | Old habits die hard | Ask questions first, fix last |
| Hiding feedback out of niceness | Want to be liked | Be direct, coach privately |
| Letting chaos rule “for growth” | Misreading empowerment | Set clear check-ins, visible goals |
| Losing all visibility (“hands off”) | Fear of micromanagement | Use consistent process, not pop-ins |
| Measuring yourself by your own output | IC identity lingers | Measure by team outputs and growth |
| Trusting without verifying | Too much faith, too little structure | Inspect what you expect |
| Situation | Step In? | How to Act |
|---|---|---|
| First-time a manager owns a new deliverable | No | Set clear goals; observe, check-in weekly |
| Repeated minor misses but learning is visible | No | Coach at 1:1s, let learning happen |
| Misaligned approach (risks business) | Yes | Flag real risks, guide decision, don’t fix |
| Missed alignment but no critical risk | Maybe | Ask probing questions, nudge privately |
| Major project is derailing or ethical breach | Yes | Step in, fix openly, clarify expectation |
| Signs of team confusion, lack of direction | Yes | Re-state priorities, align, involve manager |
| Everything is going smoothly, team is growing | No | Cheerlead, unblock as needed |
You're Not Losing Power - You're Multiplying It
The mental model shift that makes this work: you're not giving away control, you're building an engine that generates more output than you could produce through direct involvement. A manager who owns their scope fully and executes well is worth more than a direct report you have to stay involved in. Three of them together create organizational capacity that no amount of personal effort can match.
A manager who owns their scope fully is worth more than three direct reports you have to stay involved in. Empowerment is not a management style - it is a leverage strategy.
Navigating the Delegation Transition?
Empowering managers without losing strategic control is one of the hardest transitions in leadership. I work with executives who are navigating this shift - figuring out where to let go, how to build manager capability, and how to protect the strategic capacity they need to lead effectively. Let's talk.
