What I’m still learning about why some leadership development changes behavior and most of it doesn’t.
I’ve been in and out of a lot of leadership development work this year, and I keep noticing the same thing about the efforts that go somewhere. It isn’t the frameworks. I’ve used the same frameworks in rooms where nothing changed. What’s different in the rooms where something does change is harder to put your finger on, and it has very little to do with the content. It has to do with whether the organization treats this as a commitment or as a program.
I’m still working out how to say that distinction cleanly, but I know what it looks like from the inside.
Most organizations approach leadership development the way they approach professional development. They send people to a conference. They bring in a speaker for the all-staff. They run a workshop on feedback, or time management, or emotional intelligence. Any one of those can be good. I’ve sat in good ones. The problem is that they don’t talk to each other, and they seldom connect to the actual pressures the organization is under that quarter. So people have a nice day, and then they go back to work, and nothing about how they lead is any different.
The places where it works tend to start somewhere uncomfortable. The senior team does its own work first. Before they ask anybody below them to get developed, they turn toward themselves: here’s how I lead, here’s what I do under pressure that I’m not proud of, here’s what I want to practice. I used to think the sequence was a nice-to-have. I’ve now come to think it’s the essential process. People can smell it when leadership is prescribing growth from which they’ve exempted themselves. Development doesn’t run down an org chart. It runs on whether the people at the top are visibly in it, too.
And the work itself, when it’s good, isn’t about skills. It’s about identity. Who you are when you’re leading. What shows up when you’re at your best, and what shows up when you’re cornered. And how the people who report to you experience all of that, which is usually not how you imagine they do.
Those are not fun questions to sit with. I’ve watched very accomplished people get quiet when they land. But the discomfort tends to be the tell that you’ve finally gotten to something real.
Here’s the part that matters most. How fast people drop their guard once they believe the room is developmental and not evaluative. I don’t think that’s a soft distinction; I think it’s the distinction. If you suspect what you say is going to end up in a performance review, you manage your image. If you trust that what you say will be met with help, you tell the truth, and then you can work on something. Everything about how you design these spaces is just protecting that one condition. Get it wrong and people perform for you all year.
The thing I’m still chewing on is coherence, and it’s the hardest to do well. A single great workshop doesn’t change much. What seems to move people is when everything points in the same direction: the workshop, the coaching conversation, the way their manager runs the Monday meeting, the language everyone’s using. When a leader can feel the line between what they reflected on two weeks ago and a decision they’re making right now. That’s rare. Most organizations are running too many disconnected things to get there.
And coherence costs something, which is the part nobody likes. It means cutting the standalone workshop people enjoyed because it doesn’t connect to anything. It means the people running teams must adopt language they didn’t pick and might privately find a little corny. It means slowing down, because you can’t bolt a fresh initiative onto the calendar every quarter and still expect the last one to have taken root. I’ve sat with senior teams while that tradeoff lands on them, the realization that doing fewer things well is going to look, from the outside, like doing fewer things. Some of them flinch and add the new thing anyway. The ones who hold the line understood going in that coherence isn’t a messaging problem you fix with a good slide. It’s a long series of decisions about what you’re willing to stop doing.
I want to be careful here, because I don’t want to make it sound like I’ve got this solved. I don’t. The hardest part is always still out in front of us, and it’s the part I can’t engineer: whether any of this survives contact with an ordinary Tuesday. Whether the insight a leader had in a structured session shows up in a hallway, in how they handle a direct report who’s struggling, in how they sit in a disagreement they’d rather avoid. That’s the test, and it happens when I’m not in the room.
What I can say is that I’m more convinced than I was a year ago. The organizations treating this as a system instead of a string of events seem to be building something that holds. I’m still learning exactly why. But I’ve seen enough now to stop calling it a coincidence.
