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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.
Complexitydifferent
HighLowMediumLow
Timedifferent
45-90 min15-45 min1-4 h30-60 min
Participantsdifferent
3-101-33-81-6
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsADR File, Decision Log, RationaleProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPareto Chart, Top Causes, Focus List
Tagsno overlap
LeanEconomicsSequencePrioritization
ArchitectureRationaleDocumentationGovernance
Root causeProblem solvingQualityIncident
PrioritizationQualityFocusRoot cause
Add more methods