Why Developing Others Is a Leadership Responsibility, Not a Nice-to-Have
The leader who focuses exclusively on task accomplishment and results delivery without investing in the development of their team members is consuming the team’s capability rather than building it. The people in their team remain static in capability; the leader remains the bottleneck for any work that requires more than the team’s current capability; and when those people move on, the leader must replace experienced capability rather than promoting developed talent. The leader who develops their people is building capability that compounds: each person who grows becomes more capable of delivering more complex results, of developing others in turn, and of producing the succession depth that allows the leader to be promoted without leaving a capability hole.
Peter Drucker’s observation — ‘leadership is not rank, privilege, or power. It is responsibility’ — applies directly to the development responsibility: the leader who has more experience, skill, and capability than their team members has the responsibility to share that in ways that grow the team. The accumulation of experience without sharing it with the people whose growth it could accelerate is the leadership equivalent of hoarding.
Mentoring vs Coaching: Understanding the Difference
Mentoring and coaching are often used interchangeably but describe fundamentally different types of developmental relationships. A mentor is someone with more experience in a domain who shares that experience, provides guidance based on their own journey, offers perspective from a position of having navigated similar situations, and advocates for the mentee’s career interests. A mentor tells you what they did and why, and what they’d do if they were in your position.
A coach helps the person being coached find their own answers rather than providing answers from the coach’s experience. Effective coaching is not primarily about the coach’s expertise in the topic being addressed — it’s about the coach’s skill in asking questions that help the person think more clearly, consider perspectives they hadn’t considered, and identify the actions that follow from their own values and goals. The manager who coaches their direct reports is helping them develop their own problem-solving and decision-making capability; the one who always advises is making the direct report dependent on the manager’s input rather than developing independent capability.
The Coaching Conversation That Develops Capability
The coaching conversation structure that most effectively develops the coached person’s capability: opening with the topic and the person’s ownership of it (what do you want to think through, and what outcome would be useful from this conversation?), exploring the situation and the person’s thinking (what’s the situation, what have you considered so far, what’s getting in the way?), challenging assumptions and expanding perspective (what are you assuming here, have you considered X perspective, what would your most thoughtful colleague say about this?), and supporting the identification of next steps (what are you taking away from this, what specifically will you do, how will you know if it’s working?).
The coaching mindset that makes conversations developmental rather than directive: genuine curiosity about the other person’s thinking rather than patience while waiting to give your own answer, trust that the person being coached can find good answers with the right support, and restraint from the natural impulse to solve the problem rather than developing the person’s capacity to solve it. The manager who says ‘here’s what I’d do’ is often helpful in the moment and less helpful over time; the one who says ‘what do you think you should do, and why?’ is building capability that pays back over every subsequent similar situation.
Creating Mentoring Relationships That Actually Help
The mentoring relationship that produces the most development: one that’s specific enough to be useful (the mentor who has genuine relevant experience in the mentee’s specific development area rather than just general seniority), characterised by genuine mutual investment (the mentor who is interested in the mentee’s success as an end in itself rather than as a means to something else), and structured enough to produce consistent contact and follow-through (a regular meeting cadence, agreed focus areas, accountability for actions between sessions).
The mentoring relationship formation mistakes that produce nominal relationships without development: the formal mentoring programme match that pairs people by demographic similarity or seniority without regard for relevant experience alignment, the relationship that’s agreed but never developed into regular contact because neither party prioritised the scheduling, and the mentoring relationship where the mentee comes with vague aspirations rather than specific development goals (which gives the mentor nothing specific to help with). The mentee who comes with specific questions, specific challenges, and specific goals gets more from mentoring than the one who comes hoping the mentor will figure out what they need.
Building a Development Culture as a Leader
The leadership legacy that matters most for long-term organisational health: the people who were developed during the leader’s tenure, and the development culture those people carry forward. The leader whose team consistently produces people who go on to lead effectively has created something that outlasts their specific contributions; the one who’s produced results through individual excellence without developing others has created capability that ends when their tenure ends.
The development culture signals that indicate a leader is genuinely committed to others’ growth: the promotion decisions that advance people who’ve grown under the leader’s management (versus only advancing people who came in ready), the time investment in one-on-one development conversations that isn’t sacrificed under workload pressure, the explicit advocacy for team members’ opportunities and advancement with the leader’s peers and supervisors, and the patience with the early-stage mistakes that development requires (the person developing a new skill makes mistakes that an experienced person doesn’t — the leader who reacts to those mistakes with impatience is telling the team that development is a theory rather than a practice).