From ideation to action: crossing a difficult gap in transformation
Most transformation programmes begin with no shortage of ideas, ambition, vision, opportunities and potential solutions - but transformation can falter because its difficult to bridge the gap between thinking and doing.
Ideation is often framed as the exciting part, action as the disciplined part, but being able to make regular transitions between the two is a hard challenge.
Some organisations remain in ideation for too long. Ideas are expanded, challenged, refined and revisited until progress slows under the weight of endless possibility. People can remain in a world of exploration without commitment, where every avenue remains open and every question leads to another.
Others move into delivery too quickly. Before enough exploration has taken place, attention shifts towards planning, sequencing and execution. The focus becomes making an idea work, rather than considering alternative ideas altogether. As a result, people can become constrained by the first logically coherent path they identify, limiting experimentation and reducing the opportunity to discover better options.
In one case, progress is delayed because nothing is chosen. In the other, progress follows a path that was chosen before enough alternatives had been explored.
Neither creates successful transformation.
The distance between an idea and an outcome is not crossed in a single leap, and the most effective transition keeps the thinking alive while giving the doing a plan.
There are 4 stages, as I see it:
Exploration
Don’t attempt to reach a decision while still exploring; this comes from the desire to look like progress is being made.
Allow ideation its own container, but make it time‑bound and purpose‑bound.
What could we do?
What opportunities exist?
What if we tried...?
Output for this stage: options
Decision Making
Shift explicitly into decision mode. Which of our ideas are the strongest and why?
Which idea are we pursuing?
Which are we abandoning?
What are the trade-offs?
Why this and not that?
Output for this stage: a commitment to an idea
Design, Not Tasks
Translate that decision into something deliverable.
What problem is this solving?
What outcome are we moving towards?
What resources are we allocating to this?
What changes for customers, staff, or systems?
What boundaries do we work within?
What dependencies exist?
What constraints exist?
What principles guide trade‑offs?
What are our measures of success?
What is explicitly out of scope?
Design-thinking here is about making action coherent. Some who “come up with the ideas” feel this is nit-picking, while those focused on delivery may perceive it as slowing momentum. Design-thinking will give delivery a viable foundation, and often avoids fundamental issues after implementation has begun, when the cost of change is significantly higher.
Output for this stage: a coherent solution
Delivery
Executing. Establish direction, while accepting that many details will emerge through learning and execution.
How do we implement?
In what order?
Who does what?
How do we monitor progress?
How do we adapt?
Detail can be added iteratively, while but some direction must exist at the start. When direction is missing, teams fill the gap with assumptions, priorities fragment, decision-making slows, and programme energy dissipates.
Output for this stage: realised outputs and outcomes
The distance between an idea and a realised outcome is crossed through a series of deliberate transitions, from possibility to decision, from decision to design, and from design to action. And in most transformations, managing those transitions is every bit as important as generating the original idea.