Most leadership advice is written for people managing individual contributors. Managing managers is a different job. The feedback loops are longer, the problems hide better, and the instincts that got you here start working against you. This is what actually changes when you add a management layer between you and the work.
The first time I managed someone who also managed a team, I made every mistake you can make quietly.
I gave feedback the same way I always had. I asked for updates the same way. I assumed that because I could not see a problem, there was no problem.
It took about three months for the reality to surface: one of the managers on my team had been covering a performance issue for six weeks, and I had no idea it existed.
That is the core shift nobody explains clearly when you move into managing managers. The gap is not about authority or organizational complexity. It is about what you can no longer see directly - and how long it takes for the things you cannot see to become visible.
Most writing on leadership skills for senior managers treats the transition as a natural extension of what came before. Add a layer, apply the same principles at altitude. That is not how it works.
What Actually Changes When You Start Managing Other Managers
The single most important thing that changes when you start managing managers is your proximity to the actual work.
When you managed individual contributors, you could see the output. You were close enough to the execution that problems had a short travel time to reach you. A missed deadline, a friction point with a client, a skill gap in someone's work - these surfaced fast because you were nearby.
When you manage managers, you are one full layer removed. The signals are lagged. By the time something becomes visible to you, it has usually been a problem for a while.
The manager under you has been managing it, or avoiding it, or unaware of it themselves.
At Zendesk, I watched a team deliver consistently strong QBR metrics for two consecutive quarters while the actual client relationships underneath were quietly deteriorating. The manager running that team was technically competent and genuinely liked by her team. She was reporting what looked good.
She believed the numbers. What she did not have was visibility into what her CSMs were missing in the day-to-day client conversations. And I had no visibility into her blind spots.
That is how cascading failures work. Not through deception. Through distance.
The discipline of managing managers effectively is really the discipline of closing that distance without collapsing it.
Why the Leadership Skills That Got You Here Start to Break Down
This pattern is well-documented but not said plainly enough: the behaviors that made you promotable as a direct manager become liabilities once you are managing managers.
High-performing individual contributor managers tend to be skilled at:
- Solving problems quickly when they see them
- Giving specific, detailed feedback on work they understand directly
- Staying operationally close so they can course-correct fast
- Being the most competent person in the room on the work at hand
Managing managers requires almost the opposite instinct in each case.
Solving problems directly when you see them bypasses the manager between you and the problem. It signals that you will step over them when things get hard. It erodes their authority in front of their own team - often without you realizing it has happened.
Giving detailed feedback on work you understand well is less useful when you are no longer the closest expert to that work. Your manager is. Your job shifts from being the sharpest technical voice to helping your manager develop their own judgment.
Those are not the same thing.
Staying close to the execution layer by attending team meetings, pulling delivery data, or asking questions that belong at the manager's level - this becomes micromanaging from two levels above. It communicates distrust without meaning to. I have seen this particular failure cause more organizational damage than almost any other mistake leaders make in their first year of managing managers.
I used to think the fix was discipline - just stop doing it. What I found is that the impulse lives in confidence. People stay operationally close because that is where they feel competent.
The harder work is building confidence in the new layer of work: organizational sensing, people judgment, longer time horizons.
The Feedback Infrastructure You Actually Need
The question of how to manage managers effectively is really a question about information. How are you getting signal? From which sources?
With what lag? And are the sources you rely on showing you what is real or what people want you to see?
Here is what has worked in practice:
Skip-level conversations done right. Not audits. Not informal performance reviews run from above the manager's head.
Conversations where you are genuinely trying to understand the texture of how work is going - not trying to surface problems about the manager.
The difference matters practically. If your team senses that you are using skip-levels to monitor their manager, the manager loses authority and the skip-levels become performance theater. People perform fine conversations for you and say the honest things to each other afterward.
The question I use most: "What is taking longer than it should, and what is getting in the way?" That is not a question about the manager's effectiveness. It is a question about the work. But the answers will tell you a great deal about where the friction is and whether the manager is connected to it.
Leading indicators, not lagging ones. Attrition, missed targets, declining engagement scores - these are lagging indicators. By the time they show up, you have months of accumulated dysfunction to work through.
The early signals are subtler: the volume and type of escalations reaching you directly, how questions move through the team, whether documentation is getting maintained, response patterns in async channels.
At Adobe, a team I worked closely with had an unusually high volume of escalations landing on me directly - bypassing the manager entirely. The manager was technically solid and the team liked him. What the escalation pattern was showing was that the team had learned, through repeated experience, that he would hold a problem rather than move it.
The team had adapted to a gap I had not yet named.
That information was in no report. It took six weeks of paying attention to escalation routing before I could articulate what I was seeing.
Regular exposure to the actual work - structured and light, not reactive. I do not mean attending every team meeting or reviewing every deliverable. I mean reading a sample of what gets produced each week.
Listening to one client call a month. Not to assess the work or give feedback on it, but to stay calibrated on what the work actually looks like. Without that calibration, feedback to the manager is abstract.
It does not land.
Coaching a Manager Is Not the Same as Managing One
One of the most common mistakes at this level is conflating coaching with managing. They are different modes, with different purposes, and the failure to separate them creates a specific and expensive problem.
Managing a manager means being clear about what the role requires, honest about whether they are meeting it, willing to have accountability conversations when they are not, and clear-eyed about what happens if the gap does not close.
Coaching a manager means helping them develop judgment, work through decisions, build capability over time. It is forward-looking. It is additive.
The failure mode: leaders who default entirely to coaching because it feels more collaborative and avoids directness. They frame every performance conversation as a development conversation. They use the language of growth to avoid saying something that needs to be said plainly.
I sat in on a review discussion once where a senior leader had been having bi-weekly coaching conversations with a manager who had been underperforming for four months. The coaching notes were excellent. The developmental goals were thoughtful.
And the team under that manager had lost two strong people in the same period.
Coaching a performance problem does not fix it. Sometimes a manager is developing. Sometimes they are in the wrong role.
The discipline is knowing which is true before the cost accumulates.
What the Day-to-Day Skill Set Actually Looks Like
If you want a grounded picture of leadership skills for senior managers in practice - not the framework version, the actual day-to-day - here is what separates effective from ineffective at this level:
Tolerance for incomplete information. You will not know exactly how work is getting done at the team level. If that ambiguity is uncomfortable, you will either over-control and undermine your managers, or you will disengage and lose touch.
Both are common. Neither produces good outcomes.
Precision in communicating non-obvious expectations. What counts as good judgment in your organization? At what threshold should a manager escalate versus decide?
What does "ownership" mean in practice when something goes wrong? These things are obvious to you because you developed them over years. They are not obvious to a manager who is eight months into a role.
Spelling them out explicitly - even when it feels unnecessary - closes a huge amount of the gap.
Willingness to update your read on someone's capability. The most expensive mistake in managing managers is holding a conviction about what someone can do beyond what the evidence supports. The instinct to believe in people is good.
The failure is letting it override pattern recognition for too long.
The ability to raise a concern before you are certain. Most performance issues at the manager level get addressed too late because leaders wait until they have enough evidence to be sure. By then, six months have passed.
The skill is naming what you are seeing at the first sign - as a question, as a concern, not as a verdict. "I have noticed X three times now. Help me understand what is happening."
Knowing when to step in directly - and doing it rarely enough that it means something. There are legitimate moments to bypass a manager and address something directly: a client relationship at serious risk, a team dynamic that has turned harmful, a decision that cannot wait. This is sometimes the right call.
The discipline is doing it seldom enough that when you do it, everyone understands it is serious.
The Most Common First-Year Mistakes When Managing Managers
Most leaders who are new to managing managers make the same three or four mistakes in the first twelve months. Worth naming them directly.
Measuring activity instead of outcomes at the manager level. Tracking whether your managers are doing one-on-ones, running team meetings, completing reviews - this tells you about process adherence, not about whether the managers are actually managing well. A manager can hit every process metric and still be ineffective.
Letting the relationship with one strong manager crowd out the others. There is almost always one manager on the team you click with, who communicates in ways that match how you think, who gives you clean information. It is easy to over-invest in that relationship and underinvest in the ones that feel harder.
The managers you are in less natural alignment with are usually the ones who need more of your attention, not less.
Avoiding the hard conversation because of what it might trigger. If you address a performance issue, the manager might leave. If you are direct about a gap, it might create tension that makes the working relationship worse.
These are real risks. But the math of avoidance almost always goes in the wrong direction. The longer the gap goes unnamed, the harder the conversation gets and the more damage accumulates.
Treating your management layer as a relay system rather than a leadership layer. Managers who report to you are not just transmitters of decisions and status. They are the primary culture-shaping mechanism for the teams under them.
What they model every day matters more than any value statement you put in a deck.
How Your Own Development Changes at This Level
When you managed individual contributors, your development was relatively close to visible. You could see what you were working on. The feedback was near specific behaviors.
When you manage managers, your development becomes harder to track. The feedback loops are longer. The consequences of your decisions take months to emerge.
The mistakes you make today show up in attrition data half a year from now.
What that means practically: you have to seek feedback more deliberately, from more directions, and be more skeptical of the positive signals. Positive signals at your level often mean you are not close enough to where the real problems are living.
I used to think structured upward feedback cycles were sufficient. I am less certain now. The most honest signal I have gotten about my own effectiveness as a manager of managers has come from watching what my former managers do after they move on - whether the judgment we worked on sticks, whether they apply the frameworks, whether they cite conversations we had.
That is a long lag. But it is less filtered than almost anything else.
At Intelegencia, we brought on a senior manager who had worked for a leader I deeply respected. Within three months, the quality of her decision-making in ambiguous situations was clearly shaped by how that leader had worked with her. That is the long game of developing managers.
You are not shaping the quarter you are in. You are shaping the manager they become four jobs from now.
Related reading:
