The engagement crisis

Employee Engagement Is a Readout, Not a Target

Engagement sits at historic lows. The global figures hover around a quarter of the workforce genuinely engaged, with some regions well below that, and the costs are real: lower productivity, higher turnover, a steady leak of the discretionary effort that innovation depends on.
The response, almost everywhere, is to treat engagement as a number to be raised – survey it, benchmark it, set a target, launch initiatives, survey again.

That response is the problem, not the cure. Because engagement was never a thing you could install, train, or chase directly. It’s a readout, a symptom of whether the structure people work inside gives them anything worth being engaged about. And the moment you make the readout itself the target, you stop fixing the thing it was measuring and start managing the measurement.

Why chasing the score fails

This is the trap most engagement programmes walk straight into. Engagement scores are a proxy, a stand-in for something real: whether people have meaningful work, genuine ownership, and a structure where their contribution actually counts.
The instant that the proxy becomes the goal, the organisation optimises the proxy.
It runs the survey, sees a low number, and launches interventions aimed at the number, the perks, the recognition programmes, the engagement campaigns, rather than at the structural conditions the number was quietly reporting on.

The result is predictable, and most leaders have seen it: the score nudges up for a quarter, then settles back, because nothing structural changed.
Worse, people learn what the survey rewards and answer accordingly, so the metric improves while the reality it was supposed to track stays flat.
The organisation ends up managing its engagement score while the engagement itself, the thing the score was a proxy for, keeps draining away.
Chasing the readout doesn’t fix the system. It just teaches the system to produce a better readout.

What engagement is actually reading

Disengagement isn’t a mood that better messaging or more perks can lift. It’s people responding rationally to a structure that gives them little worth engaging with.
The KPI-and-target machinery most organisations run on is a large part of this: when performance is reduced to hitting assigned numbers, work narrows to compliance, the metric replaces the purpose it stood for, and contribution gets stripped down to whether you cleared your target. People don’t disengage because they lack drive.
They disengage because the architecture has made a meaningful contribution structurally beside the point, and they’re reading that accurately.

So engagement is reading the architecture.
It’s high where the structure gives people real decision rights over their own work, where their contribution visibly affects an outcome they care about, where the incentives reward the actual job rather than a proxy for it, and where saying something true doesn’t cost them.
It’s low where the structure does the opposite, and no amount of culture-talk or recognition programming raises it, because those operate on the surface while the cause sits in the structure.

Why “build a culture of trust” isn’t the answer either

The usual correction to metric-chasing is to say engagement comes from culture, build a culture of trust, respect, and empowerment, and engagement follows.
The instinct is right, but it skips the layer that does the work.
Culture is the foundation, but you don’t build a foundation by exhorting it into being, and “trust” and “respect” aren’t things a leader can install by deciding to. They’re outputs of the architecture built on that foundation. People trust a system that’s predictable and where candour is safe. People feel respected where the structure gives them genuine ownership rather than monitored compliance. People feel empowered when they actually hold the decision rights to act.

So “build a culture of trust” collapses into the same un-actionable advice as “raise engagement.” It names a foundation and an outcome and skips the architecture in between, which is the only layer a leader can actually change. Trust, respect, and engagement are all outputs of the same structural choices. You don’t will them into being directly. You build the architecture that produces them.

What the architecture actually has to do

If engagement is the readout of whether people have meaningful work, ownership, and a structure where contribution counts, then the work is structural and specific.

It means giving people real decision rights over their own work, rather than tasks handed down with the judgement removed, because ownership is the difference between work you’re invested in and work you merely execute.
It means designing performance systems that reward genuine contribution and improvement rather than compliance with a target, so that the rational thing to do and the meaningful thing to do are the same.
It means connecting individual work visibly to an outcome that matters, so the proxy doesn’t have to stand in for a purpose people can actually see.
And it means a structure where raising a problem or challenging a plan is safe, because disengagement is often just the quiet form of having learned that speaking up costs more than staying silent.

Do those, and engagement rises as a byproduct so reliably that you barely need to measure it, because you can see it in how people actually work. Leave them undone, and every engagement initiative is an effort spent on the readout while the system it is reading stays broken.

The actual question

So the leadership question isn’t “how do we raise our engagement scores?”
That question guarantees you’ll manage the metric instead of the cause.
It isn’t even “how do we build a culture where engagement thrives?”
That one skips the only layer you can act on.
The question is: What is our architecture actually giving people to be engaged about, and where it is giving them nothing, so what in the structure do we need to change?

Engagement was never a target to chase or a culture to proclaim.
It’s what people do when the architecture gives them real ownership of meaningful work and a structure where contribution pays off.
Stop measuring the symptom and managing the number.

Build the structure that makes the symptom healthy, and the number takes care of itself.

Arrange a meeting/callback