The most honest test of any leadership mentorship relationship is what happens when the mentor is unavailable.
If the mentee becomes more capable, makes better decisions, holds the situation with more steadiness, and draws on frameworks they have genuinely internalized, the mentorship was multiplication. If the mentee stalls, escalates, or defaults to “let me check with the mentor,” the relationship created dependency dressed in the appearance of development.
Both outcomes feel like mentorship from the inside. Only one of them is worth building.
What Most Mentorship Actually Produces
Senior leaders who take mentorship seriously usually invest in it generously. They make time, share perspective, and offer access to their networks and their thinking. This is not nothing. For the mentee, it often feels transformative.
The problem is the structure beneath the generosity. Most mentorship is built around advice: the mentor shares how they think about problems, the mentee learns to anticipate how the mentor would approach similar problems, and the mentor remains, indefinitely, the most competent person in the mentee’s decision-making process.
This is not development. It is apprenticeship without graduation. The mentee grows relative to where they started, but the growth is bounded by the mentor’s continued availability. Remove the mentor, and the ceiling reveals itself.
Capacity-building mentorship has a different architecture. Its explicit goal, stated, agreed to, and returned to regularly, is the mentor’s own redundancy in the mentee’s development.
The Multiplication Structure
The difference between mentorship that multiplies and mentorship that creates dependency is not warmth or investment. It is the structure of authority transfer.
Stage 1: Modeling with narration
Early in a genuine development relationship, the mentor models decision-making while narrating the process. Not just “here is what I decided” but “here is how I framed the problem, here are the factors I weighed, here is what I considered and rejected, and here is why.” The goal is making the reasoning legible, not just the outcome.
This is more exposure than most mentors provide. It requires intellectual vulnerability: sharing the drafts of thinking, not just the polished conclusions.
Stage 2: Collaborative reasoning
In the second stage, the mentor stops narrating their own process and starts working through problems alongside the mentee, asking questions rather than providing frameworks. “How are you thinking about this?” rather than “here is how I think about this.”
The mentor’s judgment is still present. They will catch structural errors and surface missing considerations. But the mentee is now doing the primary reasoning work, and the mentor’s role is calibration and quality control, not generation.
Stage 3: Supported independence
The mentee now makes decisions and brings them to the mentor for review rather than for input. The sequence has reversed: decision first, then review. That is fundamentally different from seeking guidance before acting.
The mentor’s value in this stage is increasingly specific: flagging blind spots, stress-testing assumptions, providing organizational context the mentee may lack. The general judgment belongs to the mentee now.
Stage 4: Exit
The final stage of effective mentorship is the mentor’s deliberate withdrawal from the active relationship. Not abandonment, since access can remain, but the removal of the regular touch point that signals the mentee still needs ongoing support.
Most mentors resist this stage. The relationship carries genuine meaning, and ending it can feel like loss. But its value is in what it produced, not in its continuation. A mentee who no longer needs the mentor is the goal. That is what multiplication looks like.
The Legacy Connection
The Lead. Don’t Bleed.™ method treats mentorship not as a leadership virtue but as a succession mechanism. The question it asks is not “are you developing people?” but “what would those people be able to do if you were not here?” Mentorship that leaves dependency is, in the doctrine’s terms, one of the five ways leaders bleed capacity: it keeps load flowing back to the leader instead of building it into the team.
That reframes mentorship as a design problem, consistent with the broader work of designing what you leave behind. The leaders developed through genuine capacity-building mentorship are the most durable part of any leader’s legacy. They carry the doctrine forward, apply it in contexts the mentor will never see, and develop their own people the same way.
This is why the metaphor of multiplication is precise rather than aspirational. One leader who mentors three, each of whom mentors three more, with each relationship structured around capacity rather than dependency, produces organizational and field-level impact that no individual leader can generate alone. It is the mechanism behind healthy succession outcomes after a leader is gone.
Mentorship and Succession: The Timing Problem
Most organizations begin thinking seriously about succession too late to do the development work well. Succession planning initiated twelve months before a planned departure leaves inadequate time for the four-stage structure above. Two to three years is the minimum for meaningful capacity transfer at the senior level, a timeline consistent with the Center for Creative Leadership’s research on developing leaders.
The practical implication: if you are within three years of any planned or plausible transition, the time to begin or accelerate mentorship relationships is now, not when the transition is announced.
The final 90 days of a leadership handoff matter far less than the three years that precede them. What the final 90 days can do is transfer operational knowledge, relationships, and context. What they cannot do is develop judgment. That work only happens over time, in the four-stage structure above, with a mentor willing to make themselves redundant.
That willingness is the most important thing a mentor can offer. The full framework for building it is available at leaddontbleed.com/products.
Key Takeaways
- The honest test of mentorship is what the mentee can do when the mentor is unavailable.
- Advice-based mentorship creates a ceiling set by the mentor’s availability; capacity-building mentorship removes that ceiling.
- Real development moves through four explicit stages: modeling with narration, collaborative reasoning, supported independence, and exit.
- Mentorship is a succession mechanism, not just a virtue; the question is what people could do if you were gone.
- Meaningful capacity transfer at senior levels takes two to three years, so start well before any transition is announced.
FAQ
What is the difference between mentorship that builds capacity and mentorship that creates dependency?
Capacity-building mentorship transfers frameworks, judgment, and the authority to use them independently. Dependency-creating mentorship keeps the mentor at the center of decisions; the mentee learns how the mentor would handle things rather than developing their own reliable judgment. The difference shows up clearly when the mentor is unavailable.
How should senior leaders structure mentorship relationships?
Effective executive mentorship is structured around progressive authority transfer. The mentor begins by modeling decision-making, then invites the mentee into the process, then steps back to a review role, then exits entirely. Each stage is explicit. The goal is the mentor’s own redundancy in the mentee’s development.
Can mentorship be part of a formal succession plan?
Yes, and ideally it is. The most effective succession plans identify high-potential leaders two to three levels below the departing executive and design mentorship relationships that systematically close the gap between current capability and succession-ready capability. These relationships typically span two to four years, not months.
How long does capacity-building mentorship take?
Meaningful judgment transfer at the senior level takes a minimum of two to three years, because judgment develops through repeated reasoning under real stakes. Operational knowledge and relationships can move faster, but they are not a substitute for developed judgment.