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 Systems Mapping |  Decision Making Force Field Analysis |  Architecture arc42 |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 1-2 Tage |
Participantsdifferent | 3-12 | 3-12 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ChangeDecisionStrategy | ArchitectureDocumentationCommunication |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
