View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategic, Tactical and Operational PlanningAfter-Action ReviewATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Operations After-Action Review |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 90-180 min | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-12 | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Lessons learned, Action items, Event summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | CadenceGovernanceExecution | LearningOperationsImprovement | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
