methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Risk Storming.
Architecture
Risk Storming
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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
MediumLowMediumHigh
Timedifferent
30-90 min60-90 minOngoingSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-124-122-20Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineAnnotated Diagram, Prioritized Risk List, Action BacklogChat Transcript, Action Log, AutomationsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RiskArchitectureWorkshopValidation
CollaborationEngineeringIncident
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods