View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Systems Thinking Evaporating Cloud |  Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 45-60 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
