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 Architecture Decision Record |  Systems Thinking Intervention Mapping |  Systems Thinking Evaporating Cloud |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | 1-5 Tage | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 4-12 | 2-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureDecisionAsyncGovernance |