Building Leaders Who Don’t Need You: The Art of Developing the Next Layer
The goal of leadership development is a team that makes high-quality decisions without escalating. When the team's independence makes the leader optional in day-to-day operations, the development work is complete.
The best manager I ever had was the one who made herself unnecessary. Every decision she made was designed to build my capacity to make it myself. At the time, I didn’t fully appreciate it. Looking back, it was the most profound act of leadership I’ve ever witnessed.
She never solved problems for me when I came to her. She asked questions until I solved them myself, then reflected back what she observed in how I got there. It felt frustrating in the moment — I wanted answers, not Socratic dialogue. But six months into that role, I noticed something strange: I had stopped needing to go to her. Not because she had withdrawn, but because she had built something in me. That is the whole point.
The Multiplication Principle
John Maxwell’s Law of the Lid holds that your organization can only grow as tall as your own leadership capacity allows. It is a useful frame. But there is a corollary that I find even more interesting: the most powerful thing a leader can do is raise the lid for others. Developing one leader who can then develop three more is not linear arithmetic — it is exponential leverage. The compounding effect of leadership development is one of the most undervalued assets in any growing organization.
Jim Collins wrote in Good to Great that Level 5 leaders — the ones who build genuinely enduring organizations — consistently develop successors who outperform them. That is not modesty. That is intentionality. They define their success not by what they achieve personally, but by what the organization can achieve without them. In a region like Southeast Asia, where fast growth often concentrates decision-making at the top, this is a counterintuitive discipline. But it is the one that determines whether a business survives its founders.
I’ve seen the alternative play out too many times: the brilliant operator who builds a team of executors, not thinkers. The business scales to a point, then hits a ceiling that looks like a market problem but is actually a leadership density problem. There are not enough people in the organization who can think at the next level because no one ever developed them to.
High-Potential vs. High-Performer
These are not the same category, and conflating them is one of the most expensive mistakes a growing company can make. High performers deliver results — they hit their targets, execute well, and make your life easier. High potentials build systems — they think about how work gets done, not just whether it gets done. They are the ones who quietly document a process without being asked, who notice that a recurring problem has a structural cause, who ask “why do we do it this way?” rather than “what do I need to do today?”
The classic mistake is promoting your best individual contributor into a management role. You lose a high performer. You gain, more often than not, a struggling manager — someone who was never developed for that work, who defaults to doing rather than coaching, and who carries the resentment of a role they did not truly want or were not ready for. I have made this mistake myself. It is painful on both sides.
Identify potential early by watching for different signals. Who asks questions about the system, not just the task in front of them? Who teaches others without being asked, and does it naturally rather than performatively? Who comes to you not just with problems but with a read on the problem — some attempt at a framework, even if imperfect? These are the people worth investing in deliberately, long before a promotion is on the table.
- Delivers exceptional individual results
- Asks “How do I solve this task?”
- Optimizes their own output
- Succeeds through personal skill
- Valuable — hard to replace in their role
- Multiplies results through others
- Asks “How does the system work?”
- Optimizes the team’s output
- Succeeds through developing others
- Invaluable — creates more leaders
The Coaching Conversation
A leader’s instinct is to solve. You see the problem, you know the answer, the fastest path is to just tell them. And it is. In the short term. But every time you solve instead of coach, you are making an implicit trade: short-term efficiency for long-term dependency. You are training the person across from you to bring you problems rather than build the capability to resolve them.
The developer’s approach is to ask. “What would you do if I wasn’t here?” is one of the most clarifying questions in leadership. It surfaces what the person already knows but has not given themselves permission to act on. It shifts the locus of authority from you to them, and it does so without abandoning them — you are still in the room, still a resource, but you are no longer the answer.
The GROW model gives this a useful structure. Start with the Goal: what are we actually trying to achieve here? Move to Reality: what is the current situation, honestly assessed? Open up Options: what are all the ways this could be approached? Close with Will: what will you actually do, and when? It sounds mechanical on paper. In practice, a well-run GROW conversation builds more capability in thirty minutes than a year of advice-giving. It forces the person to think, not just receive.
I use this framework in almost every substantive one-on-one now. Not as a rigid script, but as a reminder to stay curious rather than directive. The leaders on my team who have internalized this approach have started running their own one-on-ones the same way. That is the replication effect — and it is exactly what you are building toward.
The leaders you develop will outlast your tenure, your title, and your strategy. That is the legacy worth building. Not the market share you captured or the revenue you grew, but the people who carry forward the capacity to lead well long after you have moved on. When I think about the leaders who shaped me most, none of them gave me answers. They gave me the tools to find my own — and then trusted me to use them.
← The Feedback Paradox: Why Leaders Fear the Conversations That Matter Most
