If It Breaks When You Leave, You Never Built It
- 3 days ago
- 3 min read
By Bill Flynn
When I became a sales manager for the first time, I was one of the top sales reps in high-tech. I assumed the new job was the same, just multiplied. Step in, show the team how it’s done, handle the hard ones, repeat. For a while, that worked. My number looked fine. The team’s numbers did not.
The moment I remember most clearly wasn’t dramatic. I was sitting with a team member who had a problem I had already solved in my head. I opened my mouth. And then I stopped.
I realized I was about to take away his chance to figure it out. Not maliciously. Helpfully. Which made it worse.
That was the moment I became a different kind of leader.
I gave the team two rules: be honest and be responsible, to yourself, the client, and the company. That was it. How each person did their work was up to them. We built a shared framework for diagnosing where things actually stood, and every team meeting had one learning element, including how I’d used neuroscience to become the top performer at every company I’d worked for.
I realized I had been operating as a Controller. The leader who stays indispensable by solving problems directly. What I needed to become was a Builder, someone who develops the capacity of others to solve problems themselves. The two rules and the shared framework did something more important than any technique I could share. Honesty and responsibility gave the team guardrails to act without intervention. The framework gave them a shared language for diagnosing their own work. Together, they made me progressively less necessary, which turned out to be exactly the point.
That shift, from Controller to Builder, was the first graduation. The second came later. The framework turned out to be more than a tool. It was something the team could run without me, and it made the whole operation predictable enough that I stopped needing to be inside every decision. When I started designing systems that didn’t require me in the room, I realized I had already been doing it. Decision frameworks. Operating rhythms. People who could sense what was wrong before I named it. That’s the Architect.
Values were part of that design.
They don’t travel through mission statements. They travel through decisions - the visible choices leaders make when short-term pressure is high. The guardrails I gave that first team weren’t rules about sales technique. They were rules about character. That distinction is what makes values survive a leadership transition. When those structures exist, the culture outlasts the person who created it. When they don’t, each new leader reinterprets everything from scratch.
That’s not a people problem. It’s a design problem. Deming argued that most performance failures are system failures. Most succession failures are the same.
I have come to believe that great leaders build organizations that don’t require great leaders to thrive.
Mine wasn't, early on. I was the system. Fast, effective, and completely unscalable.
Most organizations don’t fail from bad intentions. They fail from default settings - from what no one decided. Design beats default. The organizations that sustain performance across leadership generations do so because someone deliberately built them that way. The same is true whether you’re running a company of 500 or a team of 5.
The question worth asking isn't whether your successor is ready. It's whether what you've built is ready for a successor. Those are different questions. They tend to have different answers.
Connect With Bill
Comments