When something goes wrong, start with the system, not the practice.
This system pattern shows:
how to systematically assess where an issue sits by distinguishing between:
- system design
- system application
- practice delivery
and how multiple factors often combine to shape outcomes.
How the system behaves over time
In a well used system:
When an issue or unintended outcome occurs:
- operating standards and procedures are checked first
- their sufficiency is assessed, not just their use
- practice standards and judgement are then considered
Over time:
- root causes are identified more accurately
- system design improves based on real events
- practice is strengthened through learning
- accountability is clearer and more balanced
- improvement becomes continuous and embedded
In a poorly used system:
When something goes wrong:
- focus quickly shifts to who made the mistake
- assessment stops at whether procedures were followed
- system design and context are under examined
Over time:
- the same issues repeat
- fixes are local and short term
- practitioners become risk averse or defensive
- learning is limited
- system weaknesses remain hidden
What is really going on
Issues and incidents are rarely caused by a single factor.
They usually sit across a combination of:
- system design (were the standards and procedures right?)
- system application (were they implemented effectively?)
- practice delivery (how was judgement applied in the moment?)
But systems often default to:
- attributing issues to individual error
- prioritising visible causes over underlying ones
This creates a bias towards:
- blame over understanding
- correction over learning
The purpose of this pathway is to rebalance that.
Why this is hard to shift
Most organisations are designed around accountability to individuals.
That leads to:
- a focus on compliance with procedures
- pressure to identify a clear point of failure
- limited time and space to explore broader causes
At the same time:
- system design issues are harder to see and harder to fix
- multiple contributing factors are more complex to explain
So over time:
- investigation narrows too quickly
- system level issues are normalised
- practice is scrutinised more than design
What helps shift the pattern
- Start with whether standards and procedures were followed
- Then assess whether they were sufficient
- Distinguish clearly between design, application, and practice
- Look for multiple contributing factors, not a single cause
- Treat incidents as inputs to system improvement
- Create space for reflective, not just corrective, review
- Strengthen feedback loops between practice and system design
Consistent use of a structured pathway builds a more accurate understanding of how outcomes are produced.
Reflection questions
- When something goes wrong, where do we start our assessment?
- How often do we examine system design as well as practice?
- Do we distinguish between non compliance and system limitations?
- What patterns are repeating, and what does that tell us about the system?
- How well do we capture and use learning from real events?
- What would change if we focused first on causes, not individuals?