What a Failed Culture Program Costs the Person Who Championed It

She had presented the program to the board herself. Eighteen months of planning, a named vendor, a rollout calendar, a slide with a projected engagement lift she had been careful to hedge and the board had quoted back to her anyway, without the hedge.

Fourteen months later, a board member asked, in the middle of an otherwise unrelated meeting, "Whatever happened to that engagement program?" She did not have a good answer. It had not been cancelled. It had simply stopped being anything anyone did.

The direct financial cost was easy to state. Vendor fees, facilitator days, the hours her own team had spent building the rollout. She could have written that number on a whiteboard in thirty seconds.

The cost she had not priced was what happened to her the next time she stood up in that same boardroom with a new proposal.

The credibility that does not show up on any invoice

A leader who champions an initiative is making an implicit claim every time she presents it: I understand this well enough to predict that it will work. When the initiative quietly fails, the board does not usually revisit the specific reasons. It updates a broader, less articulated model of how much weight to put on her next recommendation.

This is not unfair. It is how organizations calibrate trust over time, and it happens whether or not anyone says it out loud. The next time she proposed something with real budget attached, she noticed the questions were sharper, the follow-ups more numerous, the default assumption slightly more skeptical than it had been eighteen months earlier.

She had lost something that does not appear on a P&L and is far more expensive to rebuild than a line item. The board's willingness to take her word for it on the next thing.

How much is one unresolved conflict really costing your company?

What she found when she went back and looked

She went back and diagnosed why the program had actually died, since nobody, including her, had done that at the time. The program had trained managers on frameworks in a single offsite and then handed the rollout to each manager's own discretion, with no structure for practicing the behavior inside a real meeting afterward.

It had failed for the same reason most programs like it fail. It taught a concept and assumed the concept would translate into behavior under pressure, without ever rehearsing the specific moment where the behavior was supposed to show up. Behavior under pressure lives in the nervous system, not in the slide deck that described it. She recognized, reading her own old proposal, that she had built exactly the kind of program Doug Noll's research warns against, one that installs knowledge instead of a reflex.

Doug Noll's new book Empathy Leadership: The Powerful Skill That Drives Winning Results lays out the difference between a program that teaches a concept and one that installs a working reflex. See it here.

What she did differently the second time

Her next proposal to the board was smaller, narrower, and included a specific measurement point at ninety days tied to an observed behavior, not a survey score. She told the board, in the room, that this was a direct correction of the last program's design flaw, not a rebrand of it.

The board approved a fraction of the previous budget. Ninety days in, she had a real number to bring back, not a hedge. It was the first time in two years she had walked into that room and felt the room's trust move back toward her instead of away.

‍