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 of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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 a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowHighLowMedium
Timedifferent
60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope15-30 min1-4 h
Participantsdifferent
4-10Evaluation team, architects, and relevant stakeholders2-63-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
ArchitectureQualityRiskTradeoffsStakeholders
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods