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 SAAM (Software Architecture Analysis Method) |  Operations Time Blocking |  Business Strategy GAP Analysis |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 | Low | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min Planung, laufend | 1-3 h | 45-90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | 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 | Blocked Calendar, Capacity View, Focus Plan | Gap Matrix, Action Plan, Risk Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | PlanningTime managementFocus | StrategyAnalysisPlanning | ChangeDecisionStrategy |