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 arc42 | ![]() Decision Making Argument Mapping | ![]() Decision Making Cynefin Workshop |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Mehrere Wochen | 1-2 Tage | 1-3 h | 60-180 min |
Participantsdifferent | 2-6 researchers plus sample | 1-4 | 1-8 | 4-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Argument Map, Evidence Gaps, Decision Rationale | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication | SensemakingDecisionRationale | ComplexitySensemakingDecision |



