View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture C4 Model |  Decision Making Cynefin Workshop |  Innovation Design Thinking |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | High | Low | Medium | High |
Timedifferent | Mehrere Wochen | 1-4 h | 60-180 min | 1 Tag bis mehrere Wochen |
Participantsdifferent | 2-6 researchers plus sample | 1-5 | 4-20 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context Diagram, Container Diagram, Component Diagram | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureCommunicationVisualization | ComplexitySensemakingDecision | InnovationPrototypeResearch |