Ideate, Plan & Deliver method guide
Idea Cloud
Idea Cloud supports fast idea capture, clustering, sensemaking and selection before deeper analysis.
Beginner-friendly guide · 4 min read
What Idea Cloud does
Idea Cloud supports fast idea capture, clustering, sensemaking and selection before deeper analysis.
An idea cloud gives a group a fast, shared place to generate and organise possible responses to a challenge. It supports divergent thinking first, then clustering and selection when the team is ready to converge.
The cloud is not a popularity contest or a finished portfolio. A useful session begins with a clear prompt, preserves the origin and meaning of contributions, and routes selected ideas into evidence, prioritisation or planning.
Innovation processes often separate divergent exploration from convergent definition and development. The tool preserves fast contribution while making later curation and handoff explicit.[1][2]
Divergence and convergence are different modes. Do not evaluate so early that the idea set narrows prematurely.
1Frame2Generate3Cluster4Name themes5Select next steps
InnovationFlow explanatory schematic, synthesised from the method sources[1][2].
Understand the method
The parts in plain language
When to use it
- During workshops that need broad participation and visible clustering.
- When ideas arrive from several sources and need a shared review surface.
A practical workflow
- 1
Frame the challenge and contribution prompt.
- 2
Capture ideas without premature evaluation.
- 3
Cluster, merge and name themes while retaining source context.
- 4
Select ideas for prioritisation, assumption testing or roadmap work.
Fictional worked example
Example: reducing factory peak demand
This example is illustrative rather than a reported case. A cross-functional workshop generates options for a strategic energy challenge.
Observation:Ideas include scheduling, storage, pricing, controls and behaviour.
Implication:Breadth reveals several intervention types.
Observation:Many ideas address timing rather than total energy use.
Implication:Name the pattern and keep different mechanisms separate.
Observation:Three themes have plausible value but weak evidence.
Implication:Move them to prioritisation and assumption tests, not straight to delivery.
From analysis to decision
How to interpret the result
- 1Separate contribution volume from quality.
- 2Keep minority ideas visible when they represent a distinct mechanism.
- 3Give every selected idea an explicit next tool or owner.
The interpretation guidance is an InnovationFlow synthesis of[1][2].
What a useful output looks like
Common pitfalls
- Do not confuse number of ideas with quality of insight.
- Avoid clustering so aggressively that distinct assumptions disappear.
References and method basis
- [1]Design Council (2004). The Double Diamond. Design Council. Source ↗Originating institution
- [2]Delbecq, A.L. and Van de Ven, A.H. (1971). A Group Process Model for Problem Identification and Program Planning. The Journal of Applied Behavioral Science, 7(4), 466-492. Source ↗Peer-reviewed research
This guide synthesises the named sources into practical questions for strategy and innovation work. It does not claim that using a tool by itself produces a successful decision.