RULES THAT HOLD
Most operations do not lack rules.They lack rules that hold under pressure.Used to understand why rules fail under pressure — even when they appear clear and agreed.
In normal conditions:
processes are followed
expectations are clear
decisions appear consistent
Under pressure:
rules are bent
exceptions increase
decisions shift
outcomes depend on who is present
What is written and what actually happens begin to separate.
The problemA rule that does not hold under pressure is not a rule.It is a preference.And preferences collapse when:
time compresses
volume increases
consequences become immediate
What this work focuses onThis work examines what makes a rule:
real
enforceable
and stable under pressure
It focuses on:
where boundaries actually exist
what prevents work from reopening
how decisions are held or deferred
why systems drift back to tolerated behaviour
In practiceIn most environments:
rules exist on paper
enforcement depends on individuals
exceptions become routine
ownership becomes unclear
The system continues to operate —
but stability does not form.
Core principleA rule only exists if:the system cannot proceed without it.If work can continue while ignoring the rule:
the rule is optional
and will be treated as such
What causes rules to failRules fail when:
authority is unclear
boundaries can be reopened
consequences do not land where decisions are made
exceptions are easier than compliance
Under these conditions:the system defaults to what it tolerates, not what it states
What this changesWhen rules hold:
decisions stop being revisited
work stops reopening
exceptions reduce
effort is no longer required to maintain basic performance
The system becomes predictable.
Important constraintRules do not create authority.They depend on it.Where authority does not exist:
rules will be negotiated
boundaries will collapse
and enforcement will move to individuals
What this is notThis is not:
a management system
a rollout model
a set of best practices
It does not attempt to impose rules.
What this doesIt describes:
what makes a rule hold
what prevents it from holding
how systems behave when rules are optional
what becomes possible when they are not
When this becomes relevant
rules are announced but not followed
decisions are revisited repeatedly
exceptions become normal
outcomes depend on specific individuals
BoundaryThis work does not assign authority or justify enforcement.It describes the conditions under which rules can hold.
Black Sheep Solutions
Independent publishing imprint
Ireland© Black Sheep Solutions
blacksheepsolutions.ie