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 Polarity Mapping |  Systems Thinking Leverage Points |  Architecture Architecture Decision Record |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-2 h | Half day | 15-45 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 1-3 | 3-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Leverage Map, Action Strategy | ADR File, Decision Log, Rationale | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Systems thinkingTradeoffsLeadership | Systems thinkingChangeStrategy | ArchitectureRationaleDocumentationGovernance | ChangeDecisionStrategy |