Loading content
Wicked problems are complex, ill-defined issues with conflicting requirements, shifting constraints, and no single correct solution. They arise in social, organizational, and product contexts and require iterative inquiry, systemic framing, cross-functional stakeholder alignment and adaptive governance. The emphasis is on continuous learning, reframing and c…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Wicked problems are complex issues with conflicting requirements whose solution cannot be determined uniquely.
The term wicked problem comes from Horst Rittel and Melvin Webber, who introduced it in planning theory in 1973 for societal problems that keep changing as perspectives and conditions change.
In a wicked problem, understanding and attempted solutions influence each other. Each intervention can reveal new conflicts, so people learn, negotiate and adjust incrementally.
The problem has no conclusively correct solution.
Understanding and attempted solutions continually evolve together.
Iterative learning and negotiation replace linear planning.
Wicked problems help teams plan realistically when goals are uncertain and many people are affected.
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.