The ultimate test of change is not enthusiasm. It is invisibility. When change becomes infrastructure, it no longer feels like change. It becomes the way work happens.
What infrastructure actually means
Infrastructure is not a system or a tool. It is the alignment of decision rights, incentives, measurement, authority, operating model, and practitioner stance. When these elements reinforce the same behavioural expectation, the organisation does not need constant reinforcement. Behaviour stabilises. Energy shifts from correction to execution.
Why most change remains temporary
Many initiatives succeed at mobilisation. They generate attention, align stakeholders temporarily, and produce visible progress. But if governance, operating design, and measurement remain partially inconsistent, stabilisation depends on continued effort. Change remains active. Active change consumes attention. Eventually, attention moves elsewhere, and behaviour reverts or fragments.1
If integration instability is repeatedly corrected behaviourally rather than structurally, confidence declines, change fatigue accumulates, and practitioners are asked to re-mobilise energy.2 The organisation becomes skilled at launching. Less skilled at embedding.
Each new initiative begins with residual scepticism — because prior changes required sustained correction rather than convergent design.
What convergence looks like
Convergence occurs when strategic priorities are explicit and sequenced, operating model design reflects those priorities, incentives reinforce expected behaviour, measurement clarifies tension rather than conceals it, and practitioners name structural contradictions rather than softening them.3
In that environment, behaviour aligns without constant facilitation. Reinforcement becomes lighter. Governance becomes anticipatory. Change becomes infrastructure.
The P-series has explored diagnostic integrity, sponsorship architecture, measurement interpretation, operating model boundaries, practitioner stance, and strategic coherence. All of those layers converge here.
When design and behaviour reinforce one another, instability does not disappear entirely — but it no longer circulates. It is corrected at the appropriate layer. And when that occurs consistently, change ceases to be episodic. It becomes embedded. That is the difference between initiative success and organisational maturity.4
-
Kotter, J. P. (1996). Leading Change. Harvard Business School Press. Kotter identifies declaring victory too early as one of the most common causes of change failure: once leadership believes the change has succeeded, the investment of attention and governance that produced the initial mobilisation withdraws, and the structural conditions that weren’t yet fully anchored reassert themselves. The initiatives that produce visible progress but leave governance, operating design, and measurement partially inconsistent have succeeded at mobilisation — Kotter’s first five stages — but not at anchoring, which is his final stage. Without that anchoring, stabilisation remains dependent on continued effort rather than on embedded design. ↩︎
-
Maslach, C., & Leiter, M. P. (1997). The Truth About Burnout: How Organizations Cause Personal Stress and What to Do About It. Jossey-Bass. Maslach and Leiter establish that burnout and change fatigue originate not in the amount of work but in chronic mismatches between the formal demands placed on people and the structural conditions — workload, control, reward, fairness — under which those demands are made. Repeated behavioural correction of integration instability represents precisely this mismatch: people are asked to sustain alignment and compliance against structural conditions that continuously reassert prior patterns. The exhaustion accumulates because the structural source of the demand is never removed; it is only repeatedly managed. ↩︎
-
Beer, M., Eisenstat, R. A., & Spector, B. (1990). “Why Change Programs Don’t Produce Change.” Harvard Business Review, 68(6), 158–166. Beer and colleagues demonstrate that durable change occurs through unit-level redesign of tasks, coordination, commitment, competence, and management — not through top-down programmes. Convergence, in their model, is the product of concurrent alignment at the unit level across all of these dimensions. The list of conditions here — explicit priorities, aligned operating model, reinforcing incentives, clarifying measurement, honest practitioner stance — maps directly to this framework: each element is a dimension of unit-level alignment that, when present simultaneously, creates the structural conditions for behavioural stabilisation. ↩︎
-
Senge, P. M. (1990). The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday. Senge’s distinction between symptomatic and fundamental solutions provides the conceptual basis for what “corrected at the appropriate layer” means. A symptomatic solution addresses the visible manifestation of instability without changing the structural condition that produces it; a fundamental solution addresses the structural condition itself. Organisational maturity — the transition from initiative-by-initiative episodic change to embedded capability — is the state in which fundamental solutions are routinely applied rather than symptomatic ones. Instability is not eliminated; it is redirected to the structural layer where it can be corrected permanently rather than managed repeatedly. ↩︎