Development Is Not a Program

Most leadership teams say they care about developing people.

Very few do it in a way that actually changes performance.

The assumption is that development comes from resources—programs, content, access. If those exist, progress should follow.

It doesn’t.

Development is not a program. It’s a set of decisions about where leaders invest time, what gets reinforced, and what gets tolerated.

That’s what shapes capability over time.

In most organizations, those decisions aren’t made deliberately. They’re made implicitly, through pressure, priorities, and habit. That’s where the gap shows up.

High performers are promoted without support. New leaders are expected to figure it out. Transitions are treated as events instead of inflection points.

Nothing breaks immediately. But over time, performance becomes uneven. Alignment weakens. Decisions carry more weight than they should.

This is where most organizations misdiagnose the problem.

They respond by adding more—more programs, more content, more structure.

But the constraint isn’t access.

It’s discipline.

The discipline to slow down at the right moment and ask what this person actually needs to be effective here, where they will struggle even if they’re capable, and what support will make the difference over the next 90 days.

Those are not HR questions. They’re leadership decisions.

And they show up most clearly during transitions.

If you want to understand how seriously an organization takes development, don’t look at what they offer. Look at what happens when someone steps into a new role.

That’s where the system either supports performance or exposes its gaps.

If development isn’t changing how people operate under pressure, it isn’t working.

And that’s where the real work begins.

‍