Home/What we do/Implementation
Towards actionImplementation Strategy
A practical path from a decision to work on the ground — owners, sequence, and the first moves.
Overview
A strategy that cannot become next week’s work is unfinished. Implementation strategy is the conversion of a decision into owners, sequence, and a first move that is small enough to be real.
We do not confuse a roadmap with a path. A path has names, dependencies, and a way to tell whether the first step worked.
Four stages before a path is treated as settled.
Each stage leaves an artefact you can challenge. Nothing is carried forward on confidence alone.
- 01
Understand
Study the work, the systems, the people, and the constraints as they are.
- 02
Define
Name the actual problem. Write the non-goals.
- 03
Explore
Hold more than one credible path long enough to compare them.
- 04
Structure
Turn the choice into architecture, owners, and sequence.
Inside implementation.
First moves
Define the smallest action that makes the strategy real.
Ownership
Put names against decisions, not only against tasks.
Dependency order
Stop later work waiting on unnamed earlier work.
Pilot to scale
Design the jump from a contained trial to day-to-day use.
Vendor direction
Brief partners so they implement the intended design.
Review rhythm
Set how progress is judged before the work drifts.
The terms of the work.
A working note.
The kind of thing this work produces — inspectable, arguable, and short enough to be read.
WEEK 1 Maya freeze unplanned tool requests Jon list intake fields that are actually used Priya write non-goals for the board pack SUCCESS The unofficial spreadsheet has an end date. The join has an owner. Leadership can repeat the problem in one sentence.
When this usually appears
- Strategies that never leave the slide
- Programmes with too many workstreams
- Handover from strategy to delivery teams
- Internal teams that need a clearer brief
Implementation, asked directly.
Frequently asked questions
Do you run the delivery team?
We can stay close to direction. Day-to-day build can sit with your team or a partner.
What if the first move fails?
Then we learned something cheaply. That is the point of starting small.
Adjacent work.
Bring the situation as it is.
You do not need a polished brief to start. A conversation is usually enough to name the problem and decide whether there is work here at all.