What makes a leadership program actually stick?

Nearly every leader has watched it happen. A team goes away for a day, comes back lit up, and within a week the old patterns have quietly closed back over the top. The energy was genuine. It just had nowhere to go.

After enough of these, a fair question follows: what separates the programs a team still talks about a year later from the ones that fade by Friday? The answer has less to do with the content on the screen than most people expect, and more to do with how the work is built. A few things tend to be true of the programs that hold.

The lesson has to be lived, not told

You cannot lecture a team into seeing its own patterns. A group can nod along to a model of how it should communicate and then walk out and communicate exactly as it always has. What changes people is watching themselves do the thing. When a team has to make a real decision together, under real constraints, the way it actually coordinates becomes visible to everyone in the room, including the people who created the pattern in the first place.

An unfamiliar place lowers the usual defenses

Back at the office, everyone knows their part. Titles, routines, and the seating chart do a lot of quiet work, and most of it keeps people in character. Move the same group somewhere they have never been, hand them a problem the setting itself supplies, and a good deal of that scaffolding falls away. People respond more as themselves and less as their role, which is the only place honest change can start.

The debrief is where the value is made

This is the part that gets rushed, and rushing it is how a strong day turns into a nice memory. The experience is raw material. On its own it proves nothing. The value comes from sitting with what happened and connecting it, out loud and specifically, to the work waiting on Monday. A team that names its own pattern and decides together what to do differently has done something a slide could never do for it.

A team that names its own pattern, in its own words, has done something no framework can do for it.

One event is a start, not a finish

Even a program that lands will not survive on its own. What carries it forward is something to hold on to afterward: a shared phrase the team actually uses, a small set of commitments, a reason to check back in. When the day gives a group a common language for a problem it faces every week, the language keeps working long after the day is over. When it does not, the memory fades on schedule.

The short version

The programs that stick are lived rather than lectured, set somewhere that changes how people show up, closed with a debrief that does the real work, and built to leave something behind. None of that is exotic. It is just harder than making good slides, which is exactly why so much training skips it.

This is how we think about the work at Morrison Alley. If your team has a pattern it keeps running into, that is usually the right place to start a conversation.

← All field notes