What happens when we look more closely?
Transformation usually begins with a description of the problem.
A customer experience needs improving. A process needs digitising. Innovation needs accelerating. A new capability needs building. The brief creates a useful boundary around the work and gives people something they can begin to act upon.
Then the work begins, and quite often, the problem changes.
Not because the original brief was necessarily wrong, but because getting closer reveals more of the system around it. A technology problem becomes a question about behaviour. Resistance reveals organisational memory. An inefficient workaround turns out to be keeping something important functioning. A design challenge exposes an organisational constraint that no amount of redesign will solve.
These moments have shaped our practice.
Across transformation and innovation programmes, we have learned to pay particular attention to the point where the original explanation stops being sufficient. Not to make the work unnecessarily complicated, but because what becomes visible at that moment can materially change what happens next.
The examples below are drawn from that experience.
They are not intended as templates for how another organisation should transform. Every situation is different.
They show what can happen when we stay attentive long enough for the work to tell us something we did not already know.