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 | ![]() Systems Thinking Soft Systems Methodology | ![]() 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. | 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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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 | High | Low |
Timedifferent | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 0.5-3 Tage | 45-90 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 5-15 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureDecisionAsyncGovernance | Soft systemsComplexitySensemakingSystems thinking | AssumptionsRiskDecisionDiscovery |



