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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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
MediumLowLowMedium
Timedifferent
1-3 h15-30 min30-120 min1-4 h
Participantsdifferent
3-82-62-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesRoot cause notes, CountermeasuresObservation Notes, Improvement IdeasProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Root causeProblem solvingQualityIncident
Add more methods