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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-3 h30-120 min1-3 h
Participantsdifferent
2-82-82-62-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeGap Matrix, Action Plan, Risk NotesObservation Notes, Improvement IdeasContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
StrategyAnalysisPlanning
LeanObservationProcessOperations
Domain-Driven DesignBoundariesStrategy
Add more methods