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 |  Architecture Request for Comments |  Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-60 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureDecisionAsyncGovernance | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
