Development should reduce dependence
This is the clearest test. At the beginning, a new or developing manager may need a lot from you. That is normal. More questions. More review. More guidance. More reassurance. But over time, the pattern should change. They should need you: less often; at a higher level; for more complex issues. If the same ordinary problems keep returning month after month, something is not developing.
Support should have a direction
Good development is not endless availability. It is moving someone towards greater capability. Perhaps the sequence is:
“Let’s work through this together.”
Then:
“What do you think?”
Then:
“Bring me your recommendation.”
Then:
“This is yours. Let me know what you decide.”
That is progression.
Propping up looks different
The CEO still: makes the difficult decisions; reviews every communication; fixes the manager’s relationships; handles their difficult employees; reminds them of commitments; runs their meetings; chases their actions; explains the same management principles again. The manager has the title. But somebody else is supplying a large part of the management.
Ask what would happen if you stopped helping
This is a very revealing question. If you reduced your support tomorrow, what would happen? Would the manager: still function; ask sensible questions; use judgement; continue progressing? Or would the role collapse? If it collapses, look carefully at how much capability really exists.
Development creates retained capability
If you coach someone through an issue this month, what should happen next month? They should carry more of it themselves. Not necessarily perfectly. But the learning should stay. Otherwise you may simply be solving individual incidents.
Repeated coaching on the same thing is information
You explained delegation. Again. And again. You coached the difficult conversation. Again. You discussed preparation. Again. You talked about ownership. Again. At some point ask:
“Why is this learning not sticking?”
That matters.
Do not measure development by conversation count
You can have twenty coaching conversations and create very little development. The measure is not:
“How much support did I give?”
It is:
“What can they now do that they could not do before?”
That is much stronger.
Look for evidence of behaviour change
After coaching, does the manager: prepare better? bring recommendations? have the difficult conversation? delegate differently? raise problems earlier? follow up without being chased? Those are development outcomes.
Do not confuse understanding with capability
Someone can say:
“Yes, I completely understand.”
Good. Can they do it? That is the real test. Management development needs to move from insight to behaviour.
Watch whether you are still doing the thinking
A manager brings a problem. You ask questions. Good. But who is doing most of the reasoning? If you continually lead them step by step to the answer, they may become dependent on the coaching process itself. Eventually they need to produce more of the thinking before they come to you.
Ask for thinking before the conversation
Try:
“Before we discuss it, write down what you think is happening, your options and your recommendation.”
Now the manager arrives with a brain engaged. That changes the development dynamic.
Build the deep well
A developing manager should gradually build a deeper well of judgement. They experience something. Think. Decide. Review. Learn. Next time they draw on that experience. If every new situation still feels entirely new, they may not be integrating the learning.
Development should improve judgement
Not merely compliance. You do not want a manager who becomes better at guessing what the CEO wants. You want someone who can think. That is a different outcome.
Watch for permanent permission-seeking
“Can I do this?”
“Would you do this?”
“Is this okay?”
Some consultation is appropriate. But over time, ordinary decisions should shift towards:
“I’m going to do this because…”
That language often signals growing ownership. If you answer every permission question, you may be maintaining the problem Ask:
“What do you think you should do?”
Then let them answer.
Propping up often feels efficient
This is why it survives. You can see what needs doing. So you: write the email; tell them what to say; make the call; fix the customer; decide the staffing issue. Fast. But you have saved the situation and removed the learning.
Ask whether your support is creating future capacity
This is the commercial test. Does the time you invest today mean less support will be needed tomorrow? If yes, good. If not, question the pattern.
Good coaching should eventually reduce coaching on the same issue
Not eliminate development. The subject matter should rise. Earlier: how do I run this meeting? Later: how do I improve the leadership capability across my function? The level should change.
The level of their questions should rise
This is a useful sign. A developing manager starts with:
“What do I say to this employee?”
Later perhaps:
“I think I have a pattern across the team. Here is what I’m considering.”
That is growth.
Look at whether problems arrive better formed
Earlier:
“I’ve got a problem.”
Later:
“This is what happened, this is what I think caused it, these are the options, and this is my recommendation.”
Excellent. That is evidence.
Look at follow-through
Development is not only about decisions. Does the manager do what they said? By when they said? Without repeated reminders? If you still have to chase every action, you may be supplying the accountability structure personally.
Stop being their diary
You should not have to remember all their commitments for them. Record actions. Dates. Follow up in the agreed rhythm. The system should support accountability. But the manager should increasingly manage themselves.
Ask whether they manage their own team without you
This is a major test. Can they: give feedback; hold one-on-ones; clarify expectations; manage poor performance; develop people? Or are you still being pulled into their team? If so, why?
Do not become the real manager behind the manager
This happens quietly. Employee works for Manager A. But difficult matters go to CEO. Important decisions go to CEO. Performance conversations go to CEO. Then Manager A is not fully carrying the role. The reporting line exists on paper. Not in practice.
Support before the conversation, not instead of it
A newer manager may need help preparing. Fine. Role-play. Review evidence. Talk through likely responses. Then they have the conversation. Do not automatically have it for them.
Debrief afterwards
Ask: What happened? What did you learn? What would you do differently? That converts experience into development.
Watch whether the same rescue keeps recurring
One emergency intervention may be sensible. Five similar interventions are a pattern. Ask:
“Why do I keep needing to step into this?”
Distinguish inexperience from incapability
Someone new to management will have gaps. That does not mean they cannot develop. Look at: learning speed; application; ownership; response to feedback. Those tell you more.
Distinguish support need from role mismatch
Perhaps the manager keeps struggling because the role is wrong. Too large. Wrong mix. Beyond current capability. Development cannot fix every structural mismatch.
Ask whether expectations were clear
Before concluding the manager is failing, ask: Did we define what good management looks like? Or did we simply promote them and hope? You cannot fairly assess against a standard that was never clear.
Define management success
Perhaps it includes: team performance; delegation; one-on-ones; timely feedback; clear decisions; early risk escalation; development beneath them; less unnecessary dependence upwards. Now you have something real to track.
Track progress over time
This is where memory can mislead. You may think:
“They seem better.”
Fine. Better how? What evidence? Progress tracking helps distinguish optimism from actual movement.
Look at independence, not confidence alone
A manager may sound much more confident. Good. But are they: deciding; acting; following through; carrying consequence? Confidence without greater capability can be misleading.
Look at whether they are building capability beneath themselves
This is crucial. A manager can become less dependent on the CEO while making their own team more dependent on them. That is only moving the bottleneck. Strong development should cascade. Who are they developing? Ask:
“Who in your team is stronger because of your leadership?”
The answer matters. Do they build successors? A manager who cannot identify anyone beneath them with growing capability may not yet be thinking as a leader. Development should produce development.
Watch how they respond under pressure
Anyone can appear capable when things are calm. Under pressure: do they think? raise risk? take ownership? or immediately throw everything upwards? Pressure reveals how much capability is actually embedded.
A temporary wobble is not failure
Development is not a straight line. People regress sometimes. The question is pattern. What happens across months? But do not reset the clock after every wobble This is how leaders accidentally prop people up forever.
“They had a difficult month.”
Again. And again. Look at cumulative evidence.
Ask whether you are lowering the role to protect the person
This is another warning sign. The role requires X. The manager cannot do X. So gradually everyone stops expecting X. Now the person appears to fit. Because the role was weakened around them. That is propping up.
The standard should remain visible
Support the person towards the role. Do not quietly redesign the standard every time they miss it unless the role genuinely should change. Ask what peers are compensating for Perhaps another manager is:
making decisions for them; repairing relationships; taking extra workload; explaining their function. That compensation may make the manager look more successful than they are. Ask what employees are compensating for Strong employees may also hide the gap. They take over. Work longer. Solve things.
Then the team appears to perform. But leadership weakness remains.
Development should reduce the cost to others
Over time: fewer rescues; less rework; less peer compensation; less CEO intervention. If none of those improve, question what the development is achieving.
Beware the “lovely person” trap
You may genuinely like them. They may care. Be loyal. Wonderful. That does not answer the role question. Development decisions need compassion and evidence.
Beware the sunk-cost trap
“We have invested so much in them.”
Investment matters only if it is producing a reasonable return in capability. Past coaching does not create an obligation to continue forever.
Ask whether they are doing their share of the development work
Do they: prepare for coaching; practise; seek feedback; reflect; take action? Or do they arrive expecting you to develop them? Development is a two-person bargain.
You cannot care about their development more than they do
You can help. Challenge. Encourage. Provide opportunity. But the manager must carry their part.
Watch for sophisticated dependency
Senior managers can become very good at sounding developmental. They discuss. Reflect. Analyse. Have excellent coaching conversations. But behavioural change remains small. Do not let articulate reflection substitute for execution. Ask: what changed on Monday? This is one of the best tests. Insight Friday. What changed Monday? If nothing, the learning is unfinished.
Development must survive outside the coaching room
That is the whole point.
Give managers real responsibility
People do not develop solely through conversation. They need: decisions; stretch; accountability; consequences. Real work. Then coaching helps them learn from it.
Do not remove all risk
If you structure every task so tightly that the manager cannot fail, you also limit their opportunity to build judgement. Use sensible risk.
Let them own the outcome
Do not secretly shadow-manage it from behind. If you delegate, delegate. Set the guardrails. Review at agreed points. Let them carry.
Increase autonomy when evidence supports it
Development should lead to more room. That reinforces capability.
Reduce autonomy if evidence requires it
If judgement is repeatedly poor, closer support may be necessary. That is not punishment. It is proportionate management. But know whether the plan is temporary.
Avoid permanent training wheels
Temporary closer oversight should have a purpose. What needs to improve before support reduces? Otherwise training wheels become the operating model.
Use a development ladder
For a recurring management responsibility:
Stage 1 — Observe
They watch you.
Stage 2 — Prepare together
They contribute.
Stage 3 — They lead, you support
Real practice.
Stage 4 — They lead, you review afterwards
More independence.
Stage 5 — They own it
You only become involved by exception. That is visible development.
If the person never moves up the ladder, ask why
Skill? Confidence? Will? Role fit? That diagnosis matters.
Development should make the manager more useful at a higher level
Not merely better at surviving the current week. Can they handle: more ambiguity; more people; more complex decisions? That is growth.
Ask whether the business is receiving leverage
A manager exists partly to create leverage. More capability than one person could provide alone. If the CEO must supply an extraordinary amount of ongoing support simply to keep the role functioning, the leverage may be negative.
Calculate the hidden management cost
Not literally if you do not need to. But think. How many CEO hours? How much peer intervention? How much rework? How much team frustration? That is part of the performance picture.
Propping up can make the CEO feel indispensable
This is a trap too.
“They really need me.”
Perhaps. But is that good? The goal of development is not permanent need.
A successful coach creates independence
The same applies inside the business. The aim is not:
“Come to me forever.”
It is:
“You can carry more because of the work we have done.”
A practical development-or-propping-up test
Ask: Is the manager more capable than six months ago? Evidence? Do they need me less for familiar problems? They should. Is the level of their questions rising? Good sign. Are they bringing recommendations? Thinking. Are they keeping their own commitments? Self-management.
Are they handling their people? Management. Are they developing others? Leverage. Are peers compensating less? Important. Is CEO intervention reducing? Strong signal. Does learning translate into changed behaviour? Essential. If support reduced, could they still carry the role?
Perhaps the most important question. What if the answer is “not yet”? That can be okay. If: the trajectory is strong; the timeframe is reasonable; the risk is manageable. Keep developing. What if the answer has been “not yet” for a very long time? Then the question changes. Are you still developing? Or maintaining?
Maintenance is not development
There may be situations where you consciously choose to maintain someone in a role with extra support. Fine. But call it what it is. Then decide whether that is acceptable for the business.
Do not disguise a role decision as more coaching
This is where development can become avoidance. Another book. Another course. Another session. Another conversation. But the evidence is unchanged. At some point coaching may no longer be the right intervention.
Give development a fair end point
Define: what needs to improve; what evidence you expect; what timeframe is reasonable. Then review. Calmly.
Recognise genuine growth
When the manager steps up, say so.
“Six months ago this would have come straight to me. You handled it yourself and made a sound decision.”
That helps the person see their own development.
Independence should be visible to them too
That builds confidence based on evidence.
One final question
Ask:
“If I keep supporting this manager exactly as I am now for another year, will they become substantially stronger — or will I simply become permanently embedded in their role?”
That is the test. Development should create movement. More thinking. More ownership. More judgement. More capability. Less dependency. If support is doing that, keep going.
If the manager can only continue because everybody around them keeps supplying what the role itself requires, you may no longer be developing them. You may be propping them up. And once you can see the difference, you can finally decide what the business — and the manager — genuinely need next.
