View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-120 min | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 2-8 | 4-12 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery |