Most customer health programs don't fail when they're designed. They fail a few months later, when it's time to run them at scale.
I've watched this pattern play out with clients more than once. The build takes real work. Together we define what customer health means, build the scoring model, and design the customer methodology. The team is engaged. The working sessions go well.
Then the work shifts from building to running. And running is a grind.
Every week: update scores, review which accounts moved, determine actions to accounts that slipped, ensure last week's actions happened.
None of it is urgent. Important work whispers. So it slips, quietly replaced by whatever escalation showed up that morning.
I've written before about health scores going stale. This is the step after, and it's more dangerous. The score is current. Everyone can see it. Nobody acts on it.
In my experience, the rhythm often loses its footing at the leadership level.
Not out of neglect. Often the leaders who sponsor it weren't there while it was built. The report doesn't speak their language, and their attention moves on.
And leaders don't all listen the same way. Some are wired for risk: what revenue is exposed, how much, how soon. Many more are wired for opportunity: where does the next dollar of growth come from?
A lot of health reporting only speaks to risk. Risk-minded leaders lean in. Opportunity-minded leaders decide it's a CS problem.
But health can tell you both. The same model that flags exposure shows which customers are healthy, getting value, and ready for more. Leave that out and you lose half your audience, along with the sponsorship that keeps the grind alive.
Leadership also needs to see execution, not just scores.
"Three accounts went red" is information. "Three went red, and two have defined action plans" is accountability.
"Eight accounts are green" is nice. "Eight are green, and five have a growth conversation scheduled" is a plan.
Leadership sets the tone: this matters, we'll ask every time, and we'll clear the path when an action needs help beyond CS.
When that conversation happens, focus follows. The work gets done before the meeting, leaders stay engaged, and effort goes where it has the most impact.
When it doesn't, both sides drift. CS stops scoring because no one is asking. Leadership assumes things are fine because no one is telling them otherwise.
Health programs don't fail in the working sessions. They fail the first month the health conversation between CS and leadership gets skipped, and nobody on either side asks where it went.