Performance and commitment

Purpose without structure is a poster on a wall, and posters do not execute strategy.

Most organisations treat purpose as a branding exercise. The why on the website, the values statement in the annual report. In execution it does something else entirely. It is the mechanism through which people decide whether to bring discretionary effort, whether to push through when the work gets hard, and whether to make the call that serves the strategy rather than the task in front of them.

So this is not only a motivation question. It is a decision-making question. When people cannot see the line between their work and why the organisation exists, they default to local priorities. The quality of thousands of daily decisions depends on whether that connection is visible.

There is a second trap, and it catches the organisations that care most. Purpose gets asked to carry weight that performance systems, recognition and leadership design should be sharing. One leader put it plainly: we use purpose as a primary driver for our people, even though it means we need to work even harder. Purpose-driven organisations that rely on purpose alone are not building commitment. They are running on goodwill, and goodwill has a shelf life.

Purpose is also not sustained through communication. It is sustained through leader behaviour. What leaders prioritise, protect and reinforce tells people what actually matters, whatever the values statement says. When those signals are misaligned, people learn fast. They comply. They do not commit.

If every team in your organisation cannot articulate how their work connects to strategic outcomes, the purpose gap is not a communications problem. It is a leadership design problem.

The biggest risk to your strategy execution is not what people say. It is what they do not.

Think about your last leadership meeting. A decision was made and everyone nodded. Then three people had a different conversation in the corridor afterwards, about what they actually thought, about the risk they could see, about what they would have said if it felt safe to. That corridor conversation is where the real information lives, and it never made it into the room where the decision was made.

Most people hear psychological safety and think it means being nice to each other. It is not that. In execution it is about one thing: the quality of information flowing through the organisation. When it is low, leaders are making decisions on half the picture.

I have watched this play out more times than I can count. A risk is spotted on the frontline. It gets softened by the time it reaches a team lead, reframed as a minor concern by the time it reaches senior leadership, and by the time it reaches the executive table it has disappeared. Nobody lied. Nobody hid anything deliberately. The system taught people, through a thousand small signals, what was safe to raise and what was not.

One respondent in my research described it bluntly: psychological safety did not exist in the business, there was not the full liberty to disagree and carry on, it had a political impact. That word matters. Political. People were not staying quiet because they were weak. They were staying quiet because they were smart. They had learned what happened when someone spoke up, and adjusted accordingly.

Are your leaders making decisions based on what people actually think, or based on what people think is safe to say? The gap between those two is where execution risk hides.

A senior leader in my research said something I keep coming back to: empowerment equals accountability, but accountability does not mean abandonment.

That line captures what I see in organisation after organisation. Leaders delegate the outcome, then walk away. The person left holding it has no authority to act, no context behind the strategy, and no cover when it goes wrong. They are not empowered. They are exposed.

And they learn fast. They stop taking initiative. They execute the task rather than the outcome. Leadership then reads that as a capability problem rather than a design problem.

Delegation says this is yours. Empowerment means someone has the authority, the context and the support to make it work. Most organisations confuse the two, then wonder why people deliver exactly what was asked and nothing more.

Ownership comes from four things, and most organisations design all four poorly: context, authority, support and visibility. Miss any one of them and you get accountability without influence, which is the fastest way to teach a capable person to wait to be told.

If your strategy depends on people owning outcomes, the question is whether your system actually allows them to. Ask five people whether they experience ownership or accountability without influence. If they answer differently from each other, that gap is the conversation worth having.

When I was researching strategy execution in large organisations, I asked a senior leader why their teams were not collaborating across functions. Her answer was simple: you cannot give away all your resources if you are being rewarded with individual objectives, people are competing.

The strategy needed collective action. The performance system rewarded self-preservation. People were not being difficult. They were being rational.

That is the execution contradiction. Your strategy says one thing and your performance system rewards another, and people will always optimise for what gets measured. Strategy demands collective ownership of outcomes, long-term value creation, cross-functional collaboration, shared resources and trade-offs, and adaptability. Most systems reward individual KPIs, short-term milestones, functional competition, protecting your own budget, and sticking to the original plan.

The gap here is not motivation. It is infrastructure. Most organisations have no performance infrastructure designed for how strategy is actually delivered, so purpose and intrinsic motivation end up carrying weight the performance system should be sharing.

The fix is not better individual KPIs. It is redesigning what gets rewarded, funding that redesign in the same room as the strategy, and updating it at the same pace the strategy changes.

Take the list of what your strategy demands and the list of what your system rewards, and put them side by side. For each row, ask whether your system rewards what your strategy actually needs.

There is a moment in every high-performing team where something shifts. People stop delivering their part and start delivering together. They challenge each other, not because someone told them to, but because they care about the outcome. They close gaps nobody assigned them.

That is collective commitment, and in execution it is everything, because the governance system will never catch everything that falls between functions.

It is also not what engagement surveys measure. Look at what the major instruments actually ask. Culture Amp measures pride, motivation, recommendation, present and future commitment. Gallup's Q12 asks about expectations, materials, recognition and development. Every question is framed around the individual. None of them measure whether peers hold each other to account, whether people own outcomes beyond their scope, or whether commitment sustains through difficulty. Collective commitment to execution is unmeasured, and that is the gap.

The good news is that it is observable. You do not need an instrument. You need to know what to look for, and to be honest about the difference between commitment and compliance dressed up as commitment.

What builds it is not team building days, engagement surveys, values workshops or recognition programmes, useful as some of those are. It is leaders modelling collective behaviour, work structured so people genuinely need each other, belonging that comes from what the organisation stands for rather than what it offers, and peer accountability that emerges from shared investment rather than being enforced.

One respondent said it simply: engagement is an outcome, you cannot buy it off the shelf.