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 Leverage Points |  Architecture Request for Comments |  Decision Making Force Field Analysis |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Half day | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 15-45 min |
Participantsdifferent | 3-12 | 3-20 Reviewer | 3-12 | 1-3 |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Leverage Map, Action Strategy | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingChangeStrategy | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance |