The Initiatives That Cost You Nothing Are the Ones Your Team Learns to Wait Out

I spent years hunting for something solid on real management and leadership, and I kept coming up short. I could not have told you exactly what was missing. I only knew something obvious was, and I could not name it, which is its own specific, grinding kind of frustration.

In the middle of that search, a former employer put me through an official leadership training program built around personality assessments: colors, quadrants, a type. It was a real corporate initiative, not a fringe activity, run by a company that did plenty of good work otherwise. I went in expecting it to change something about how I led.

The assessment produced a label and stopped there: never revisited, never tied to a development plan, never checked against what actually happened on my team six months later. The one thing that mattered was not the training content. It was an offhand introduction to a set of authors writing about management outside the academic track I had been reading. Years later, one idea out of that introduction became what I now call The Primary Span, live in my own published work today. The training program itself produced nothing that survived it.

Conventional wisdom says management is inherently faddish. Servant leadership, stack ranking, OKRs, endless agile ceremonies, and now managers rushing back to writing code because AI made it easy again: each wave gets adopted with real enthusiasm, then quietly dropped a few years later when the next one arrives. Every technical leader who has sat through one of these rollouts has felt the particular cynicism that settles into a room by the third one, and almost none of them says it out loud in the room where it would matter. The usual conclusion is that management itself is fashion, chasing whatever is current instead of resting on anything real.

Here is what actually happens. An organization adopts a management approach as a practice: a training rollout, an all-hands announcement, a new set of behaviors people are told to perform. That practice has no load-bearing connection to anything else in the system, not to how decisions get made, how promotion works, or how a person's actual job depends on it. So when leadership changes, or the next fashionable thing arrives, removing it costs nothing, because nothing was ever resting on it.

The organization reads that as proof the practice failed: we tried it, and it did not stick. The actual finding is narrower and less comfortable. Whatever was tried was never connected to anything real, so of course it detached cleanly the moment nobody was actively pushing it. The team draws its own, more accurate conclusion: new initiatives can simply be weathered. Wait long enough, give the appearance of being on board, and it will eventually be dropped, and every initiative after that starts from a smaller reserve of good faith than the one before it.

None of this means the leaders who get it right have some trick the rest do not. They stopped launching the version of the initiative that costs them nothing. A management approach only survives the next reorg if adopting it required changing something already load-bearing: a decision boundary somebody already depended on, a promotion criterion, a budget line another team was already counting on. The initiative that is easy to launch is easy to launch precisely because the leader is not the one who has to give anything up for it. The version that actually holds costs the leader something first, before it ever asks anything of the team.

Look at the last management initiative you rolled out. What did you personally give up, change, or put at risk to make it stick: a decision right you used to hold alone, a process you used to own, a budget line you used to control? If the honest answer is nothing, that is not evidence the initiative failed. It is evidence it was never architecture to begin with.

LeadershipOS™ has the full architecture for building a management system that survives the next reorg, not just this one test for whether your last attempt ever had a chance: http://TheLeadershipOSBook.com

TeamOS™ has the step-by-step version, the actual sequence I use for installing this with a real team, ending in a Team Working Agreement that documents what changes and holds everyone to it.