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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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
LowLowMediumMedium
Timedifferent
15-45 min15-30 min3–4 h for initial assessment; preparation and deeper analysis additional1-4 h
Participantsdifferent
1-32-61 or a small team; particularly suitable for 3–4 people3-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleRoot cause notes, CountermeasuresLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskAssessmentLean
Root causeProblem solvingQualityIncident
Add more methods