
Leaders who say 'they're not ready' often haven't prepared them. A 30-day plan with specific behaviors turns delegation from a wish into a reality. Readiness is built, not discovered.
When I ask leaders who might take over some of their responsibilities, a common answer emerges: "I would love to delegate. They are not ready yet."
That answer deserves a harder look. What if they are not ready because you have not prepared them?
Successful leadership shows up in the growth of other people. If no one around you is stepping up, the problem may sit closer to home.
Get specific. What would that person be doing if they were ready? Vague expectations produce vague results. "I need you to step up" does not describe a behavior. It describes a wish. Replace it with concrete language: "I need you to lead the weekly review without me in the room" or "I need you to make the first pass on client escalations and only loop me in when you hit a decision you cannot make." Or "I need you to own the quarterly budget review from start to finish." Each of those sentences describes a measurable action. The person knows exactly what "ready" looks like.
Describe the behavior shift. That turns a hope into a target. Without a target, the person cannot aim. Without aim, they drift. Drift looks like waiting for permission.
Now ask yourself: who have you prepared in the last thirty days? If the answer is "none," the bottleneck is not the team. It is the leader. That is a hard fact to swallow. Most leaders prefer to blame the team's capability. The data says otherwise. A leader who has not invested in preparation is a leader who has chosen to stay the bottleneck.
The next question is harder: how will you prepare someone over the next thirty days? A plan with a date and a specific skill beats a general intention every time. Write it down. "By March 15, I will have coached Sarah on handling the monthly client escalation call. She will run the call on March 20 while I observe. On March 21, we will debrief for 30 minutes." That is a plan. "I will work on developing Sarah" is a wish.
What becomes possible when people act without asking permission? That is the real measure. A leader who has prepared someone well does not need to be consulted on every decision. The person already knows the boundary, the judgment call, and the escalation point. The leader gains time. The team gains speed. The organization gains depth.
Preparation is not a one-time conversation. It is a sequence of exposures: small decisions first, bigger ones later, always with feedback after each one. The goal is not perfection on day one. The goal is a person who can handle the next level of complexity without the leader holding the pen. Each exposure builds confidence. Each feedback loop closes a gap.
Consider a manager at a mid-size tech firm. She spent 30 days teaching her direct report how to handle vendor negotiations. Week one: observe and discuss. Week two: co-lead a negotiation. Week three: lead with the manager in the room. Week four: lead alone. By month two, the direct report closed a deal without the manager present. The manager gained back 10 hours a week. The direct report gained a promotion track.
That sequence works because it is deliberate. It is not accidental. Accidental development takes years. Deliberate development takes weeks.
Leaders often fear that letting go will drop quality. The short-term dip is real. The long-term gain is larger. A team that waits for permission on every decision is a team that moves at the leader's pace. A team that acts within clear boundaries moves at the market's pace.
If you are waiting for someone to become ready on their own, you will wait a long time. Readiness is built, not discovered. The question is not whether the team can step up. The question is whether the leader will build the ladder.
©2025 Leadership Freak / Dan Rockwell. All rights reserved.
Prepared with AlphaScala research tooling and grounded in primary market data: live prices, fundamentals, SEC filings, hedge-fund holdings, and insider activity. Each story is checked against AlphaScala publishing rules before release. Educational coverage, not personalized advice.