How do you empower your managers?
At this level, the best measure of your leadership is how little your managers need you to get through the week.
Jay Sampat, Chief Mirror Holder · Drafted with AI · coach review pending · Updated · 9 min read
The short answer
You empower your managers by making yourself less necessary to their week. In practice that means four habits: letting decisions be made without you, passing information on before they need to ask, developing them as leaders rather than checking their work, and making sure their teams see them get the credit.
You stepped up to lead managers because you were good at running a team. Now you have several teams, each with its own manager, and you can feel the pull to run all of them. You reply to the thread, you join the meeting, you make the quick call so things keep moving. Each one feels helpful. Then you go on holiday for a week and come back to a queue of decisions that waited for you, and a few that your managers made while quietly hoping you’d agree.
That queue is the clearest sign of whether you empower your managers or hold them back. This post is about the habits that build it, and how to change them.
What does it mean to empower your managers?
It means making yourself less necessary to their week. An empowered manager knows which decisions are theirs, hears what matters in time to act on it, is being developed as a leader, and is seen by their own team as the person in charge.
At Coach42 we think of leaders of managers as sitting somewhere between two ends. At one end is the amplifier: their managers get more done, think bigger and grow faster because of the way they lead. At the other end is the bottleneck: decisions, news and credit all flow through them, so their managers wait, check and play it safe.
Hardly anyone is a pure bottleneck, and nobody is a pure amplifier. Most of us are amplifiers in some habits and bottlenecks in others. In our experience the habits that matter most fall into four areas:
- Decisions: how many of your managers’ calls wait on you.
- Information: whether your managers hear things first, or last.
- Development: whether you grow your managers or just check their work.
- Credit: whether your managers’ teams see them win, or see you.
Why does empowering managers matter more than empowering a team?
Because at this level your habits don’t stay with you. Your managers copy them, and their teams feel the result. A small bottleneck at the top becomes several small bottlenecks one layer down.
Gallup’s research makes the point about managers in general. In a 2015 Gallup article, Randall Beck and Jim Harter write that managers account for “at least 70% of the variance in employee engagement scores” across business units. If managers shape how their teams feel about work that strongly, then the person who shapes the managers has a lot of reach.
Gallup’s latest State of the Global Workplace report adds a warning. Managers used to be more engaged than the people they led, but Gallup now finds “they are increasingly only as engaged as those they lead.” A manager who has to check every decision with you is not likely to feel much ownership, and their team picks that up.
So empowering your managers isn’t a nice extra. It’s most of the job.
Are your managers waiting on your decisions?
If you have to ask, probably. Decisions that wait on you are the most common bottleneck, and the hardest to see from your own seat, because from where you sit everything seems to be moving.
The waiting rarely comes from a rule. It comes from habits. You ask to see the plan before it goes out. You like to be copied in. You overturned one decision six months ago, and your managers remember. None of this says “check with me”, but all of it teaches it.
We call the pile of decisions that build up this way Decision Debt. It grows quietly, and at this level it compounds: when a manager waits for you, their team waits for them. If you want to put a rough number on it, the Decision Debt calculator shows what the waiting costs.
The fix is to be explicit about which calls belong to your managers. Pick one recurring type of decision, such as hiring within budget, changing a project’s scope or agreeing a deadline with another team, and say plainly that it’s theirs, with a limit. Then comes the hard part. When a manager makes that call differently from how you would have, let it stand. The first decision you leave alone does more than any message about trust.
Do your managers hear things first, or last?
An amplifier passes information down before their managers need to ask. A bottleneck holds it, sometimes out of caution and sometimes just because they’re busy, so their managers keep finding out late.
This one is easy to miss because holding information feels responsible. You don’t want to share a plan that might change. You’re waiting for the right moment. You assume someone else has told them. Meanwhile your managers hear about a reorganisation from a peer, or learn about a change in priorities from a meeting you forgot they weren’t in.
The cost is double. Your managers make worse decisions, because they’re working with old information. And they lose standing with their teams, because people notice when their manager is the last to know.
A simple test: after your next leadership meeting, ask yourself which three things your managers need to hear from you this week. Tell them within a day, including what’s still uncertain. “This might change, but here’s where it’s heading” is far more useful to a manager than silence until it’s final.
Are you developing your managers, or just checking their work?
Developing a manager means helping them get better at managing. Checking their work means making sure the output is right. Both matter, but most leaders of managers spend far more time on the second.
The gap is often biggest with newer managers. The Center for Creative Leadership says the new reality for a first-time manager is that “their success is about working with, and through, others.” It also recommends that new leaders have “a boss who’s capable of holding coaching conversations” and offering feedback and development. If some of your managers are new to the role, that boss is you.
Gallup’s 2026 report is blunt about why this matters: “few managers have natural management talent,” and “many have not received the training they need” to coach their teams. Your managers are unlikely to arrive fully formed. They get better because someone helps them.
Checking work feels like development, but it isn’t. If your one-to-ones with a manager are mostly about the status of their projects, you’re managing the projects, not the manager. Try spending one session a month on their team instead: who is growing, who is stuck, and what they’re finding hard as a leader. Then ask what they’d do about it before you offer your view. For more on that last habit, read why new managers give answers too fast. It applies just as much one level up.
Who gets the credit when your managers’ teams do well?
It should be your managers, and their teams should see it. When the credit for good work flows past a manager to you, the team learns that the real decisions happen above their boss.
This often happens without anyone meaning it. You present the results at the leadership meeting because you’re the one in the room. Senior people thank you, because you’re the name they know. You reply to the team’s update with praise, and your reply is the one everyone remembers. Each moment is small. Together they make your managers look like messengers.
CCL’s advice for leaders of new managers includes letting them know they’re doing important work and to “give formal recognition when they do well.” We’d go a step further. Give the recognition in front of their team, and give it to the manager, not just the work.
Two habits help. When good news comes from one of your areas, let the manager share it, even if you could do it faster. And when someone senior praises you for something your manager led, name the manager in your reply. It costs you nothing and it shows everyone where the work came from.
What does this look like in a real month?
Here’s a hypothetical example. A head of operations leads three managers, each with a team of about eight. She’s well liked and works hard. Here’s one month.
- Week one: a manager wants to swap two people between shifts. It’s within her budget and her team, but she asks first, because last quarter a similar change was reversed. The head of operations is travelling and replies three days later. (Decisions.)
- Week two: at the leadership meeting, the head of operations learns that a key supplier is changing its delivery days next month. She plans to tell her managers once the details are final. One of them hears about it from a supplier contact a week later. (Information.)
- Week three: her one-to-ones with each manager run through project updates. A manager mentions that one of his team leads is struggling. She says she’ll have a word with the team lead herself. (Development.)
- Week four: a team hits a record month. She shares the result in the company update and thanks “the operations team”. The director replies to congratulate her. The manager who led it isn’t named. (Credit.)
Nothing here is a disaster. She did nothing unkind. But in one month, a decision waited three days, a manager found out late, a coaching moment became her task, and a win landed on her name. Her managers will check more next month, not less.
The fix isn’t to work harder. It’s four small moves: tell managers which shift changes are theirs to make, pass on the supplier news with “details to follow”, ask the manager what he’d do about his struggling team lead, and name him in the update.
Can you empower your managers too much?
Yes, if empowering turns into stepping away. Managers still need direction, context and someone to think things through with. Handing over decisions without that support isn’t empowerment. It’s absence.
There are also times when staying close is the right call: a crisis, a manager who is brand new to the role, or a decision that really does need your authority, such as setting direction for the whole area or decisions about your managers’ own pay and performance. In those moments, being more involved is a sensible trade-off, as long as you know you’re making it and say so. “I’m going to be closer to this one for the next month, and here’s why” keeps trust intact. Quietly taking things back does not.
The aim isn’t to be absent. It’s for your involvement to make your managers bigger, not to replace them.
Are you an amplifier or a bottleneck?
Most leaders of managers have one area that matters far more than the rest. Knowing which one tells you where to start, so you can change one habit well instead of trying to fix all four at once.
Amplifier or Bottleneck is a free test built for exactly this. It takes about 5 minutes, needs no sign-up, and your answers stay in your browser. You answer 14 questions about how you lead your managers, and you get an amplifier score out of 100. It looks at the four areas, decisions waiting on you, information flow, developing your managers and sharing credit, and shows the two where your team waits on you most, each with one thing to try.
For now, you rate yourself. A team version, where your managers rate you anonymously, is coming, and that’s usually the more honest view. Either way, the score isn’t a diagnosis. It shows where you’re trading your managers’ growth for your own control, so you can decide whether that trade is worth it.
If you want a wider read on how you lead, including how often you let a decision stand that you’d have made differently, try The 42 Test. You’ll find the other tests and posts for this stage on the managers of managers page, including the span check if you suspect you simply have too many people to lead well.
Empowering your managers isn’t one big decision to let go. It’s a handful of small choices each week: a decision you leave alone, a piece of news you pass on early, a question you ask instead of an answer you give, a name you put in the update. Start with the one your managers wait on most.
Ask one of your managers what they waited on you for last week. Then tell me what they said.
Jay
Key takeaways
- When you lead managers, your habits don’t stay with you. They get copied, one layer down.
- Most leaders of managers don’t hold on to power on purpose. They hold on to it a little at a time, through small habits.
- The four habits that matter most are decisions, information, development and credit.
- An empowered manager is one whose team rarely needs to ask where you stand.
- Pick the habit your managers wait on most and change that one first.
Questions people also ask
- What does it mean to empower a manager?
- It means giving a manager the decisions, information and backing to run their area without checking with you first. An empowered manager knows which calls are theirs, hears what matters early, gets coached rather than corrected, and is seen by their own team as the person in charge.
- Is empowering managers the same as leaving them alone?
- No. Leaving people alone without context or support is just absence. Empowering them means agreeing the goal and the limits, then staying close enough to coach without taking the decisions back.
- How do I know if I’m a bottleneck for my managers?
- Look at what waits for you. If decisions sit until you reply, if managers often hear news from you late, or if their teams come to you directly, the work is running through you. A self-test like Amplifier or Bottleneck can show which habit is the biggest cause.
- What should I never hand over to my managers?
- Keep the things that need your authority: setting direction for the whole area, decisions about your managers’ own pay and performance, and anything confidential above their level. Most other decisions can move down, with clear limits.
- How long does it take for managers to feel more empowered?
- Usually longer than you expect, because trust follows behaviour. If you let a few decisions stand without overriding them, managers tend to start acting on their own within weeks. One override can undo that quickly.
Sources
Keep reading