Build the Leadership Pipeline and Then Test It

This is the full playbook from “Build Leaders Who Don’t Wait for You.” The book prints a shorter version at the end of that chapter, and this page keeps every step and every example.

The Leadership Pipeline Roadmap builds a pipeline and then tests it. Intention alone builds nothing.

1. Name your bench. List everyone on your team who has shown at least one of the three signals in “Build Leaders Who Don’t Wait for You”: independent resolution of ambiguity, principled disagreement with someone senior, or a measurable effect on the people around them. Don’t filter by title or tenure. An empty list is the finding, and it’s a pipeline failure rather than a data-collection failure.
2. For each name, write down the last real decision you let that person make without your input, and the result. If you can’t name one, you’ve found why the person develops slowly: not a lack of potential, but a lack of exposure to consequences. Schedule one specific decision in the next thirty days that belongs to them.
3. Audit your calendar for single points of failure. List every recurring meeting or process where only you make the final call. Name someone who could take each one over within two quarters, and write down what that person needs to do it credibly: context, authority, or a documented standard.
4. Schedule a controlled absence. Pick a real block in the next two quarters, one week minimum, two better, fully offline. Don’t leave a detailed list of instructions; instructions defeat the test. Debrief honestly when you return: which decisions the team made well, which ones stopped and waited for you, and which were poor but survived. All three results are useful. Only the second tells you the pipeline isn’t real yet.
5. Write down what you transfer, not just who you develop. Take your top two people from Step 1 and name one piece of judgment you’ll teach each of them this quarter: a standard, a decision heuristic, or a piece of reasoning you carry and have never written down. The roadmap gate from “Build the Vision on Your Company’s Native Alpha,” whether a piece of work strengthens an advantage competitors cannot copy, is a good first candidate; it is exactly the kind of judgment that has to outlive you. Then write down how you’ll know the transfer worked. If you can’t state what you’re passing on beyond “more experience,” you’re hoping, not coaching.

Try this with AI.

“Pick a decision I make on instinct and interrogate me until the rule behind it is written down in plain language. Then tell me which parts of that rule a senior engineer could apply without me in the room.”

Build the roadmap now and revisit it in six months. Success is what happens the next time you’re unreachable: the decisions made without you look like the ones you’d have made, and not because anyone guessed what you wanted.

All of the playbooks are listed on the playbooks page.