Implementation Conditions

Most operational improvements appear to work.
Then fail under pressure.Not because the idea is wrong —
but because the conditions required for it to hold are not present.

These conditions are usually invisible during normal operation.
They only become visible when the system is under load.Structural change does not occur in isolation.
It is constrained by the environment it is introduced into.

1. Load is visible and bounded

Work 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 instability

Without bounded load, stability is temporary.

2. Decision rights are clear under pressure

It 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 unclear

Without stable decision rights, systems fragment.

3. Feedback loops are short enough to matter

The 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 performance

Without timely feedback, learning does not occur.

4. Workarounds are constrained, not relied upon

All 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 pressure

Without constraint, workarounds replace design.

5. Interdependencies are acknowledged and managed

Where 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 load

Without managed interdependence, stability cannot scale.

6. Capacity is aligned to variation, not averages

Design 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 cyclical

Without alignment to variation, performance oscillates.

7. Constraints are explicit and respected

Every 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 design

Without explicit constraints, structure erodes.

Sequence

These conditions do not operate independently.
Weakness in one will degrade the others.Attempting change without them:

produces temporary improvement
then system reversion

Outcome

Where these conditions are present:

effort reduces
rework declines
predictability increases
performance stabilises

Where they are not:

effort escalates
variation increases
workarounds multiply
failure becomes systemic

Where to go nextWithout these conditions, improvement will not hold.