View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Weekly Review |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 1-2 h |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Updated Task System, Weekly Focus, Next Actions | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureQualityRiskTradeoffsStakeholders | ProductivityExecutionPlanning | AlignmentStakeholdersStrategyFacilitation |