View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Architecture Request for Comments |  Decision Making Cynefin Workshop |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 1 Tag bis mehrere Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 60-180 min | 90-180 min |
Participantsdifferent | 4-10 | 3-20 Reviewer | 4-20 | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Problem Statement, Prototype, Test Learnings | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Decision Rights Matrix, Agreement |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureDecisionAsyncGovernance | ComplexitySensemakingDecision | DecisionGovernanceAlignmentResponsibility |