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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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 goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-3 h30-120 min45-90 min
Participantsdifferent
2-82-82-63-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeGap Matrix, Action Plan, Risk NotesObservation Notes, Improvement IdeasImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
StrategyAnalysisPlanning
LeanObservationProcessOperations
OutcomesStrategyBehaviorPlanning
Add more methods