View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Leverage PointsSAAM (Software Architecture Analysis Method)ARID (Active Reviews for Intermediate Designs)Force Field Analysis
| Criterion |  Systems Thinking Leverage Points |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | High | High | Medium | Low |
Timedifferent | Half day | Preparation, scenario analysis, and findings review; effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | Designers, developers as users, and facilitation | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Leverage Map, Action Strategy | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Systems thinkingChangeStrategy | ArchitectureChangeAnalysisComparisonQuality | ArchitectureEngineeringFeedbackValidationTasks | ChangeDecisionStrategy |