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.

Selected:5 Whysarc42
Criterion
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitysame
LowLow
Timedifferent
15-30 min1-2 Tage
Participantsdifferent
2-61-4
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Root causeIncidentLeanProblem solving
ArchitectureDocumentationCommunication
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas