Small steps, little leaps and giant strides are all required to navigate the terrain.
We invest heavily in programmes designed to move from a current state to a desired future state.
We plan them, fund them, and lock them in.
Big transformations take years.
But our context does not stand still.
While we are transforming:
- technology is evolving
- expectations are changing
- priorities are shifting
- new capability is emerging
By the time we get close to what was planned, the future state has already moved.
At the same time, we often wait for transformation programmes to improve how we operate.
If there is no programme, we wait:
- for a business case
- for a mandate
- for the next transformation
What this misses is that how we operate matters just as much in the steady state.
How often are we accommodating friction, workarounds, and constraints?
How often are we missing the opportunity to strengthen how the system works?
I am often asked if “change” is my focus.
But formal transformation is just one catalyst for redesigning how work happens.
In reality, change is constant.
So the shift may not be about doing transformation better.
It may be this:
Treat transformation as one part of an ongoing drive for excellent systems and high performance, where:
- we are always learning
- we are always improving
- we are always anticipating what is coming next
When a larger change is needed, we are building on something already evolving, not trying to reset everything at once.
The goal is not to arrive at a fixed future state.
It is to foresee, adapt, and keep moving as the future changes.