From Ideation to Action: Crossing A Difficult Gap in Transformation
Transformation rarely fails because organisations cannot generate ideas.
Most programmes begin with no shortage of ambition, vision, opportunities and potential solutions.
The challenge comes later.
Transformation can fail 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 the real challenge sits in making the transition between the two.
Some organisations remain in ideation for too long. Ideas are expanded, challenged, refined and revisited until progress slows under the weight of endless possibility.
Others make the opposite mistake. They move rapidly into delivery before assumptions have been tested, before implications have been understood, or before enough thinking has taken place.
Neither creates successful transformation.
The transition from ideation to action does not happen when you have a perfect idea. It happens when an idea becomes usable. Crossing this threshold means you stop adding ideas and start shaping constraints, dependencies, risks etc.
All of this feels like limitation to many, but in reality, it is what makes action possible.
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
Many teams try to reach a decision while they are still exploring. This comes from the desire to look like progress is being made.
Instead, 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 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
Jumping straight from ideas to to‑do lists is a common mistake. 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 is what gives delivery a viable foundation.
Without it, programmes frequently discover fundamental issues after implementation has begun, when the cost of change is significantly higher.
Output for this stage: a coherent solution
Delivery
Executing. Progress requires enough clarity to 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 rarely crossed in a single leap. It 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.