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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-6 h20-60 min45-90 min30-120 min
Participantsdifferent
2-81-42-52-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRunbook, Checklist, Escalation PathA3 Report, Action Plan, Root Cause AnalysisObservation Notes, Improvement Ideas
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
OperationsReliabilityDocumentation
LeanProblem solvingCoachingOperations
LeanObservationProcessOperations
Add more methods