Managing Managers: The Skill Most Founders Skip
The second management transition gets almost no attention and causes more damage than the first. Going from contributor to manager is at least recognised as a change; going from managing people to managing managers is treated as the same job with more of it. It is not. The thing you are now responsible for is a system that produces good management, and the primary skill — counterintuitively — is restraint, because every instinct you have will pull you toward the work you can see rather than the layer you are supposed to be developing.
What’s inside
A different job, not a bigger one
The four things you manage instead
The skip-level question
Struggling manager or struggling team
The intervention ladder
The cost of skipping levels
Where Blomma fits
A different job, not a bigger one
When you manage contributors, you manage work: priorities, quality, blockers, output. When you manage managers, the work is two steps away and you should not be touching it. What you manage instead is judgment, standards, and capability — whether your managers make good calls, hold a consistent bar, and develop their people.
The practical difficulty is that the work is visible and the management is not. You can see that a project is late. You cannot see whether a manager is having the right conversations, setting clear expectations, or developing anyone. So attention flows to the visible thing, and you end up running projects two levels down while the layer you are responsible for goes undeveloped.
The diagnostic question: in your last month of one-to-ones with your managers, how much time went on their projects versus on how they are managing? If it was mostly projects, you are managing work through a manager rather than managing a manager.
The four things you manage instead
Four areas, and if your one-to-ones do not touch them, you are not doing this job.
Their judgment.Not their decisions — how they reach them. Ask how they got to a call rather than whether you agree with it. Over time you are calibrating their judgment against yours, which is the only thing that lets you stop reviewing their decisions.
Their standard.What they accept from their team. This is where quality actually lives at scale: your standard reaches the company only as far as your managers hold it. A manager who tolerates work you would not is a leak in the standard, and it will not show up in any metric for months.
Their people decisions.Who they hire, who they promote, who they are avoiding a conversation with. These are the highest-consequence things a manager does and the ones they most need help with, and they are almost never on the agenda unless you put them there.
Their own development.They are doing a job they are new to. If you do not develop them, nobody will — they have no other manager, and their peers are competitors for scope.
A useful habit: dedicate one one-to-one a month entirely to these four, with no project discussion permitted. Most founders find the first one uncomfortable and the third one revelatory.
The skip-level question
You need information from below your managers, and getting it without undermining them requires care.
Skip-levels work if you are explicit about their purpose. Say plainly:“This isn’t about checking up on your manager. I want to hear about the work from the people doing it, and I want to know what I’m missing.”Say it every time, because the assumption otherwise is the opposite and it will make people cautious.
Ask about the work and the obstacles, not about the manager. “What’s slowing you down?” and “what would you change?” produce useful information. “How’s it going with X?” puts someone in an impossible position and you will get a diplomatic non-answer.
Never act directly on what you hear. If a skip-level surfaces a problem, take it to the manager — that is the whole discipline. Solving something you heard in a skip-level, without involving the manager, teaches everyone that going around their manager works, and you will spend the next year as the escalation route for the entire organisation.
And tell the manager you are doing them, on a schedule, before you start. A skip-level they find out about afterwards reads as surveillance.
Struggling manager or struggling team
When a team is underperforming, three causes present identically and need completely different responses.
The manager is struggling.Signals: their people are not developing, they cannot articulate what good looks like, they escalate decisions they should own or make ones they should escalate, and their team’s problems arrive to you already framed as unsolvable.
The team has a problem the manager is handling.Signals: the manager can describe the problem precisely, has a plan, and is already acting. Output is down and management is working. The correct response here is support and patience, and intervening does real damage.
The structure is wrong.Signals: the team has responsibility without authority, or its outcome depends on three other teams. A capable manager will still fail. Run the attribution question — would the best possible manager succeed in this seat?
Ask the manager to explain the problem before you decide which you are in. The quality of their explanation is the most reliable single indicator: a manager who can tell you precisely what is wrong and what they are doing is managing, whatever the current numbers say.
The intervention ladder
When a manager is struggling, five options in escalating order. The mistake is jumping to the last one.
One. Ask for their diagnosis.Often they know and have not been asked. Sometimes the act of articulating it produces the plan.
Two. Coach the specific gap.Not general encouragement — the particular skill. Setting expectations, giving feedback, holding someone to a standard. Name it and work on it.
Behind two and three: get them real support.A first-time manager with no training will not improve through willpower. Coaching, a peer group, a mentor — something that is not just your occasional attention.
Three. Narrow the scope.Fewer reports, or one fewer area, temporarily. This is a legitimate and under-used move that lets someone succeed at a smaller version while they build capability.
Four. Change the structure.If the seat is the problem, fix the seat.
Five. Move them out of management.Sometimes the right answer, and it should be framed as a role fit rather than a failure — plenty of excellent contributors are not managers, and returning to contribution should be a real option rather than a humiliation.
What is not on the ladder: taking over their team while leaving them in place. That is the most common founder response and it removes the manager’s authority without removing the manager, which is worse than either alternative.
The cost of skipping levels
The single most damaging habit at this layer, and it always comes from good intentions.
You see a problem two levels down, you know how to fix it, so you talk to the person directly and fix it. Fast, effective, and it costs you three things. The manager’s authority — their team now knows there is a higher court. The manager’s information — they find out about the problem and the fix at the same time, from someone else. And the manager’s development — they never had to handle it.
Do this a handful of times and your managers become coordinators who route problems upward, because that is what you have taught them works. Then you conclude that your management layer lacks initiative.
The alternative is slower and it is the job: take what you saw to the manager, tell them what you observed, and let them handle it — including handling it worse than you would have. If it is urgent enough that it genuinely cannot wait, intervene and then tell the manager immediately, explaining why you broke the rule. An acknowledged exception preserves the norm.
Where Blomma fits
The hard part of this layer is restraint under visibility. You can see a problem, you know the answer, and the correct move is to hand it to someone who will handle it less well. There is nowhere to work that impulse out, and the people involved are the ones you cannot discuss it with.
Blomma is an always-on AI career coach with no stake in your team. Use it to work out which of the three situations a struggling team is actually in, before you intervene — the diagnosis founders most often get wrong. Use it to design the one-to-one that covers the four areas rather than drifting into project status. Use it to prepare the skip-level framing, and to decide what to do with something a skip-level surfaced. And use it in the moment you want to fix something two levels down, to work out whether it genuinely cannot wait.
The second application is the more important one. Your managers are doing a job nobody trained them for, and your capacity to develop them is the binding constraint on how well your company is managed. Coaching that does not depend on your calendar having room is how a management layer gets better rather than just larger..
Managing managers is not managing more people. It is building a layer that manages well without you — and the main skill is not taking over when you can see exactly how.