If improvement only happens through transformation, the system is standing still.
This system pattern shows:
two different approaches to system improvement:
- revolutionary change: periodic, large scale, programme led
- evolutionary change: continuous, embedded, system led
and how each shapes performance, capability, identity, and outcomes.
How the system behaves over time
In a revolutionary system design loop:
- improvement is triggered by significant issues or investment opportunities
- change is led by specialists, often outside the system
- direction is set by a small group of leaders
- activity is organised into programmes and business cases
Over time:
- progress comes in large steps rather than continuous movement
- productivity often dips during design and implementation
- capability is built temporarily, not always sustained
- identity shifts are required quickly and can be disruptive
- the system improves, but is dependent on investment cycles
In an evolutionary system design loop:
- observation and improvement are part of everyday work
- issues and opportunities are identified continuously
- teams contribute to shaping and improving the system
- larger investments are informed by ongoing learning
Over time:
- improvement is continuous and embedded
- capability is built within the system
- identity evolves gradually through participation
- adaptation becomes normal, not disruptive
- the system becomes more responsive and resilient
What is really going on
This is not an either or.
Most systems rely heavily on revolutionary change and end up waiting:
- waiting for a business case
- waiting for a mandate
- waiting for a programme
In that waiting, the system continues to operate with known constraints.
An evolutionary approach does not remove the need for investment or large scale change.
It strengthens the system between those moments.
It allows:
- learning to accumulate
- capability to build
- identity to evolve
So when larger change happens, it builds on something already moving.
Why this is hard to shift
Most organisations are set up to manage large scale change:
- funding models favour defined programmes
- governance is structured around major decisions
- improvement is often separated from day to day work
At the same time:
- continuous improvement can feel less visible
- ownership of improvement is diffused
- people may not feel empowered to act
So over time:
- improvement becomes something we plan for
- rather than something we do
What helps shift the pattern
- Treat improvement as part of everyday (but still managed) work, not a separate activity
- Create regular observation and feedback loops within teams
- Involve more people in identifying and acting on improvement opportunities
- Build capability for problem solving and adaptation across the system
- Connect continuous improvement with larger investment decisions
- Make constraints visible and part of shared understanding
- Recognise and value small, cumulative improvements
Small, consistent improvements strengthen the system and make larger change more effective when it is needed.
Reflection questions
- Where does improvement sit in your system today?
- What currently triggers change?
- How much improvement happens between major programmes?
- Who is involved in identifying and acting on opportunities?
- What capability exists to support continuous improvement?
- Where are you waiting for change that could begin now?
- How well does your system balance immediate improvement and long term investment?