Implementation Is a Learning Process, Not a Rollout
From Strategy to Implementation: 3 of 3
Strategies often describe implementation in relatively linear terms. Actions are identified, responsibilities assigned, timelines established and progress monitored.
This creates an understandable picture: once the strategy is adopted, the task is to progressively roll it out.
But implementation rarely takes place under the same conditions in which a strategy was developed. Circumstances change. New information becomes available. Constraints emerge. Opportunities appear. Actions interact with other parts of the organisation in ways that weren't anticipated.
Implementation therefore isn't simply the delivery of a strategy. It is also a process through which the organisation learns how the strategy works in practice.
The problem with thinking in terms of rollout
The idea of rollout works well when the destination and pathway are relatively predictable. Develop something, introduce it across the organisation, monitor delivery and address problems as they arise.
But many organisational strategies deal with challenges that are less predictable. Climate adaptation, community resilience, preparedness and long-term organisational change all unfold within systems that continue changing while implementation is underway.
A five-year strategy is not being implemented into a world frozen at the moment the strategy was written.
Treating implementation purely as rollout can therefore create an unintended assumption: that the main task is to remain faithful to the original pathway.
Sometimes the more important task is recognising when that pathway needs to change.
Implementation changes the system
Implementation is not something that happens to an organisation without affecting it. A new initiative can change workloads, relationships or expectations. A partnership can create connections that didn't previously exist. One team's action can increase demand somewhere else. A new process might solve one problem while creating another. Communities, partners and other stakeholders also respond.
This means the environment in which the next decision is made may already be different because of the actions taken before it.
Implementation itself becomes part of the system it is trying to influence. Recognising this makes it difficult to think of implementation as simply progressing through a predetermined list.
New information emerges through action
Planning can tell us a great deal, but some things only become visible once we begin.
We discover how people respond to an initiative. We learn whether different teams can coordinate as expected. We encounter dependencies that weren't obvious during planning. We find that an existing relationship is more valuable than anticipated, or that a seemingly minor constraint has much wider implications.
This information is not separate from implementation. It is one of its outputs. The question is whether the organisation is able to notice and use it.
If implementation is judged primarily by whether actions were completed, important information about how implementation is unfolding can easily be overlooked.
What worked on paper may work differently in practice
There is nothing unusual about this. Strategies are developed using the best information available at the time. They necessarily simplify complex environments enough to establish direction and make decisions.
Practice introduces complexity again.
An action that appeared straightforward might rely on several other teams. A proposed approach may work well for one community but poorly for another. An external partner's capacity may change. A new technology might create an option that wasn't available when the strategy was developed.
None of these necessarily mean the strategy was wrong. They mean implementation is producing a more detailed understanding of the environment in which the strategy has to work.
Learning is part of implementation, not something that happens afterwards
Organisational learning is often associated with evaluation: looking back after a project or strategy period and asking what worked, what didn't and what should be done differently next time.
That is valuable, but for long-term strategies it can also be too late. If useful information emerges in year one, an organisation should not need to wait until year five to learn from it.
Learning can happen alongside implementation.
What are we noticing?
What is working differently than expected?
Where are new barriers appearing?
What opportunities are emerging?
What are we learning from the people doing the work?
These kinds of questions allow implementation experience to inform what happens next.
Adapt the pathway without losing the direction
This does not mean strategies should constantly change whenever something becomes difficult. Adaptability without direction can become drift.
The distinction is between the strategic outcome an organisation is trying to achieve and the pathway it originally expected would get it there. The direction may remain clear even when the pathway changes.
If evidence suggests an approach is ineffective, circumstances have changed or a better opportunity has emerged, adapting how the organisation proceeds may strengthen its commitment to the strategy rather than weaken it.
Staying committed to an action is not always the same as staying committed to an outcome.
Building learning into implementation
The challenge, then, is not simply to implement and later evaluate. It is to create enough space during implementation for people to notice what is happening, share what they are learning and consider whether that learning should influence what happens next.
This doesn't replace accountability, milestones or monitoring. Organisations still need to know whether commitments are being delivered.
But alongside the question:
Are we doing what we said we would do?
there is another worth asking:
What are we learning from doing it?
Implementation viewed this way becomes more than the rollout of a strategy. It becomes an ongoing process of moving towards a desired direction, learning from experience and adjusting the pathway as the organisation - and the world around it - continues to change.