Why Leadership Development Fails Founders

The good programs solve a real, specific problem: turning strong individual contributors into capable people-managers inside a structured organization. Every model assumes stability, clear roles, support infrastructure, and a timeline measured in quarters.

A founder has none of those conditions, so the program doesn't fail because the content is wrong. It fails because the context it assumes doesn't exist. Take the popular 70/20/10 model. The 70% "learn on the job" piece assumes a supportive environment where mistakes are buffered by the organization. For a founder, on-the-job learning is reactive crisis management at full speed. The 20% "social learning" piece assumes mentors and peers at your level. Most founders at this stage are the most senior person in the room. The feedback loop the model needs isn't there.

The research on this is not flattering, and it's worth being honest about. McKinsey's own paper puts global spend on leadership training at over $50 billion a year. And the return is poor. In their own global survey, only 11% of executives believed their leadership-development efforts produced the results they wanted, and a Fortune survey cited in the same paper found just 7% of CEOs think their organizations develop leaders effectively. The sales-training research suggests much of what's taught is forgotten within weeks of the workshop.

For a founder, the decay is faster because the environment they return to is higher friction and higher cognitive load than the corporate manager the program was built for. The workshop gets erased by Tuesday afternoon, not because the founder is weak but because nothing in their week is built to reinforce it.

Here's the part every leadership program skips. A founder turning up to a development session on three nights of broken sleep, elevated cortisol from a difficult client, and a declining HRV trend is not in a state to absorb or apply anything taught that day.

HRV, sleep quality, and blood markers shape the capacity for complex decisions and long-range thinking. Exactly the capacities the program is trying to build. Skip that layer and you're building on sand. The biomarkers I track for founder stamina connect directly: sleep debt produces measurable drops in mental control the next day, and it compounds across a week. None of that shows up in a 360-degree feedback report. It shows up as slower decisions and a flatness in strategic thinking that gets misread as a competency gap.

Teaching a depleted founder better decision frameworks is like teaching posture to someone with a herniated disc. The framework isn't the fix. The thing underneath it is.

There's a second problem competency models miss. At €5M, many founders are still running on the self-concept and risk tolerance they built when the company was a fraction of the size. They tolerate the wrong clients. They hold onto operational tasks they should have handed off two years ago. They quietly cap their own authority at a level that fit an earlier version of the business.

Scaling requires a real shift from operator to architect, and that shift is psychological as much as operational. Most programs don't have a module for it, because it requires individual diagnosis rather than group curriculum. Every misaligned client and inherited process sitting on the calendar is consuming cognitive load, and that load surfaces as slower decisions in the conversations that matter most.

Decision fatigue degrades the judgment quality that leadership programs assume is already intact. When the prefrontal cortex is depleted, the founder doesn't lack frameworks. They lack the biological state to use them.

The alternative starts with measurement, not curriculum. A biological baseline: HRV trends over time, sleep quality, relevant blood markers, and a calendar audit that maps where cognitive load is actually going across the week. That picture surfaces the performance leaks no workshop would catch. Chronic sympathetic activation from sleep debt, a calendar full of the wrong commitments, and the physiological footprint of months of decision fatigue.

From there the work is individual, built on the founder's own data rather than a shared syllabus, and sequenced deliberately – foundation first. What separates this from a program is integration. A blood-marker pattern gets tied to a calendar habit, and that gets tied to a real business outcome. The chain has to be built around the specific founder, and it's hard to replicate in a cohort.

The clearest one is a pattern. You invest in a program, feel a short lift, and slide back to the same plateau within weeks. If that's happened more than twice, the issue isn't program quality. The category of help is wrong for the problem.

The others: slower decisions despite better frameworks, and physical depletion that persists no matter how you manage your time. Underneath both is a growing sense that the company has outpaced the version of you currently running it.

None of those get solved in a training room. They get solved by starting with the biology and building a system that runs in your actual week.