Good systems do not replace judgement. They support it.
This system pattern shows:
how clarity, or lack of clarity, between different types of standards shapes:
- how work is done
- how decisions are made
- how much cognitive load sits with practitioners
and ultimately, how well a system supports judgement in practice.
How the system behaves over time
In a well structured system:
- operating standards define what must be achieved
- operating procedures define what must be done
- practice standards guide what must be considered
- practice delivery applies judgement in real situations
Over time:
- expectations become clear and consistent
- cognitive load is reduced
- practitioners focus on high value decisions
- judgement is strengthened through use
- the system supports both consistency and adaptability
In a poorly differentiated system:
- standards, procedures, and practice expectations are blurred
- too much is either prescribed or left undefined
- practitioners compensate for gaps and inconsistencies
Over time:
- cognitive load increases
- workarounds become normal
- variability appears where consistency is needed
- rigidity appears where judgement is needed
- effort increases to achieve the same outcomes
What is really going on
This is not about how much is documented.
It is about how clearly different types of expectations are defined and how well they work together.
Systems need to do two things at once:
- create clear, reliable guardrails
- leave space for professional judgement
When operating standards, procedures, and practice standards are not clearly separated:
- guardrails weaken or become overbearing
- judgement is either constrained or unsupported
The goal is not to control practice.
It is to create a clear runway for it.
Why this is hard to shift
Most organisations are designed for clarity, control, and accountability.
That often leads to:
- over specification of activity
- reliance on procedures to manage risk
- limited distinction between repeatable work and judgement based work
At the same time:
- skilled professionals resist having their work overly prescribed
- leaders are cautious about reducing control
This creates tension:
- too much control constrains practice
- too little clarity leaves people exposed
Over time, systems drift into a mix of both.
What helps shift the pattern
- Clearly distinguish between operating and practice domains
- Define non negotiables explicitly (safety, compliance, minimum expectations)
- Design procedures for repeatable activity only
- Use practice standards to guide, not prescribe, judgement
- Treat cognitive load as a core design consideration
- Test whether the system supports good decisions in real conditions
- Strengthen the connection between standards and lived practice
Small improvements in how these elements are defined and connected can significantly strengthen both consistency and judgement.
Reflection questions
- Where are your operating standards, procedures, and practice expectations blurred?
- What is currently over specified, and what is under defined?
- Where are practitioners carrying unnecessary cognitive load?
- Which decisions should be supported by judgement, but are being constrained?
- Which expectations should be non negotiable, but are currently unclear?
- How well does the system support good decisions in real conditions?