← Back to ACI
Article · 5 min read

From change to capacity: a systems perspective.

Change only becomes capacity when the system around it can hold. When strategy and workforce fall out of sync, the missing link is almost always the layer between them - the HR system that is supposed to translate intent into behaviour.

ACI Article · Dalla & Partners

Change is an input. Capacity is the output.

Organisations are rich in change and poor in capacity. Strategies are refreshed, programmes launched, tools deployed - and yet the ability to actually do more, better, next quarter often does not move. The systems view explains the gap: change only converts into capacity when three levels stay in sync. Where they drift apart, the change is real but the capacity never arrives.

The three levels, and the layer that translates

Strategy sets the intent. The workforce is where intent has to become behaviour. Between them sits the HR system - roles, incentives, capability-building, the practices that decide whether a new demand is something people are equipped to meet or simply told to absorb. When strategy accelerates and the HR system doesn't move with it, the workforce is left carrying a gap it did not create. That gap is where change stops converting into capacity.

"Employee well-being is not a wellness programme running alongside the roadmap - it is the boundary condition that determines whether the roadmap's gains persist."

Giugula & Dinu (2026), Strategic Change

Why the failure is systemic, not individual

When a transformation stalls, the instinct is to look for the weak team or the resistant manager. The systems view relocates the problem: the failure usually lives in the relationships between levels, not inside any one of them. A workforce that looks disengaged is often a workforce responding rationally to an HR system that never caught up with the strategy. Fix the individual and the pattern returns; close the gap between the levels and it resolves.

Measuring the sync, not just the parts

This is why ACI measures cross-level drift rather than reporting three isolated scores. The scores tell you how each level is doing; the drift tells you whether they can act as one system. A programme designed to build capacity should watch that number above all - because capacity is precisely what a coherent system produces and an incoherent one consumes.

Where is your system out of sync?

See which level is lagging and how far - the gap that decides whether change becomes capacity.

Related: The coherence advantage · AI adoption has a well-being bill · The peer-reviewed framework →