Loading content
Ideation is a structured method for generating, expanding, and evaluating ideas during early product discovery or problem-definition phases. It combines divergent creativity techniques with later convergence to select viable concepts. Ideation helps teams create variety, test assumptions, and produce prioritized solution candidates.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Ideation is a structured phase of creative work in which a team develops many possible responses to a problem space.
The practice grew from creativity research, design, and innovation work because teams needed more varied options than spontaneous ideas alone could provide. Design-thinking teaching material such as the d.school Bootcamp Bootleg helped spread related exercises.
Ideation works like a funnel in reverse order: first the team opens the space and collects diverse ideas without early judgment. It then narrows proposals using shared criteria until a few options remain for prototyping or testing.
A clear starting question gives the work direction without prescribing a solution.
During expansion, variety matters and evaluation is deliberately deferred.
During narrowing, ideas are selected and developed using explicit criteria.
Ideation is useful when a team needs several options for a product, service, or organizational question. It does not replace problem understanding or feasibility checks; time pressure, group dynamics, and premature judgment can reduce variety.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.