View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Systems Thinking Soft Systems Methodology |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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 | Low | High | High |
Timedifferent | 20-60 min | 0.5-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-4 | 5-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | 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 | OperationsReliabilityDocumentation | Soft systemsComplexitySensemakingSystems thinking | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
