
Date:
001
People act on what is reinforced
A regional manager once said something to me I have never quite stopped thinking about. We were talking through a new strategic priority her organisation had launched with real fanfare, town halls, a slick video, posters in every break room. I asked how it was landing on the floor. She smiled, not unkindly, and said, "I believe in it. I just can't afford to act on it before eleven, when my roster numbers get checked."
That single sentence explained more than any engagement survey I have read.
Leadership teams tend to assume that when a strategy fails to take hold, the problem sits somewhere in communication, that the message was not clear enough, repeated enough, or believed enough. So the instinct, understandably, is to communicate harder. More sessions. More materials. More conviction from the top. And still, months later, very little on the ground has actually changed, even though almost everyone, if asked, can describe the new priority accurately.
Across the organisations we've worked inside, a more reliable explanation keeps surfacing, and it has little to do with belief. People do not act on what they are told. They act on what they are measured against, day to day, by the system directly in front of them. A frontline team hearing a new strategic priority from head office is also, simultaneously, being rostered, scored, and incentivised by a much older, much more immediate system. One that was rarely updated when the new strategy was announced. When the two disagree, the immediate system wins almost every time, not because people are indifferent to the strategy, but because they are behaving entirely rationally within the system that actually governs their day.
We saw this with unusual clarity inside a large, multi-site, consumer-facing organisation shortly after it launched a significant new priority. The rollout, by every conventional measure, had been done well, extensive communication, strong training, high recall among frontline staff. And yet behaviour on the ground had barely shifted.


002
How we worked
Three things distinguished this engagement from a conventional strategy rollout.
1. We started on the floor, not in head office. Before running a single diagnostic session, we spent time in offices, on shifts, alongside team leads, simply observing a normal working day against the new priority, without asking anyone to explain or defend it. We wanted to see the gap before anyone tried to talk us out of it.
2. We diagnosed the system, not the message. The KLAR diagnostic laid the strategic priority side by side with everything actually shaping frontline behaviour that day: local KPIs, rostering rules, bonus structures, and the informal metrics team leads were held to by their own managers. The gap was stark and specific. The local metrics driving daily decisions had never been touched since the new priority launched. The strategy hadn't failed to arrive. It had arrived, and quietly lost, every single day, to a system nobody had told it was supposed to change too.
3. We redesigned the handful of measures that mattered, then tracked behaviour, not sentiment. Working directly with operations leadership and the team leads who would have to defend any change on the floor, we realigned the specific local metrics and rostering incentives in conflict with the strategy, a targeted correction, not a wholesale overhaul. Over the following two quarters, we tracked how frontline decisions actually shifted once the metrics stopped contradicting the strategy, and adjusted the settings twice more as real patterns emerged that the first pass hadn't anticipated.
Nobody needed the strategy explained to them again. They needed the system underneath it to stop quietly arguing against it, and once it did, behaviour moved without another town hall.

003
A SkyKlar Reflection
We have stopped believing that strategy fails for lack of understanding. In almost every case we have seen, people understand it perfectly well.
What we ask leadership teams now is what their organisation actually rewards, every single day, regardless of what the strategy says. Most have never measured the distance between the two, and it is usually larger than they expect.




