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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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 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.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.
Complexitysame
MediumMediumMedium
Timedifferent
2-6 h45-90 min0.5-5 Tage
Participantsdifferent
2-82-54-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsA3 Report, Action Plan, Root Cause AnalysisKaizen Charter, Waste List, Improvement Experiments, Standard Work Update
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
LeanProblem solvingCoachingOperations
LeanContinuous improvementOperations
Add more methods

Often compared together

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

EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe