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
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Purposedifferent
CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
45-90 min60-180 minSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
3-83-10Evaluation team, architects, and relevant stakeholders3-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
Systems thinkingFramingStakeholders
IncidentTimelineSite Reliability Engineering
ArchitectureQualityRiskTradeoffsStakeholders
CausalityIncidentRoot causeTimeline
Add more methods