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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1 |
Formatdifferent | Workshop + async | Workshop + async | Async |
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 |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureQualityRiskTradeoffsStakeholders | ProductivityExecutionPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
