## Implementation ConditionsWhat must be true for structural change to hold — and what will cause it to fail.---Most operational improvements fail not because the idea is wrong, but because the conditions required for it to hold are not present.Structural change does not occur in isolation. It is constrained by the environment it is introduced into.The following conditions determine whether any intervention will stabilise or degrade under pressure.---### 1. Load is visible and boundedWork must be observable at the point it is created and as it moves through the system.If load is hidden, deferred, or redistributed informally:* bottlenecks cannot be identified
* pressure accumulates unevenly
* local optimisation creates system-wide instabilityWithout bounded load, stability is temporary.---### 2. Decision rights are clear under pressureIt must be unambiguous who can decide, override, and prioritise when time compresses.If decision rights shift informally under pressure:* escalation replaces structure
* work is re-routed inconsistently
* accountability becomes unclearWithout stable decision rights, systems fragment.---### 3. Feedback loops are short enough to matterThe system must surface the consequences of actions quickly enough to influence behaviour.If feedback is delayed or filtered:* errors persist
* rework increases
* adjustments occur too late to stabilise performanceWithout timely feedback, learning does not occur.---### 4. Workarounds are constrained, not relied uponAll systems develop informal workarounds. The issue is whether they are contained or become the system.If workarounds are required for normal operation:* formal structure becomes irrelevant
* variability increases
* failure modes multiply under pressureWithout constraint, workarounds replace design.---### 5. Interdependencies are acknowledged and managedWhere multiple functions interact, coordination must be explicit.If interdependencies are assumed rather than managed:* delays propagate across functions
* local changes create unintended consequences
* system behaviour becomes unpredictable under loadWithout managed interdependence, stability cannot scale.---### 6. Capacity is aligned to variation, not averagesDesign must account for fluctuation, not steady-state assumptions.If capacity is set to average demand:* peaks create failure conditions
* recovery consumes future capacity
* instability becomes cyclicalWithout alignment to variation, performance oscillates.---### 7. Constraints are explicit and respectedEvery system operates within limits. These must be visible and enforced.If constraints are ignored or overridden:* short-term gains create long-term degradation
* pressure is displaced rather than resolved
* system behaviour diverges from designWithout explicit constraints, structure erodes.---### SequenceThese conditions are not independent.Failure in any one condition will degrade the others over time.Attempting structural change without these conditions in place produces temporary improvement and long-term instability.---Where these conditions are met:* effort reduces
* rework declines
* predictability increases
* performance stabilisesWhere they are not:* effort escalates
* variation increases
* workarounds multiply
* failure becomes systemic---Start here only after Diagnostic and Rules That Hold have been established.Skipping sequence produces the appearance of progress without structural change.