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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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 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
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h1-3 h45-90 min
Participantsdifferent
2-83-102-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeDomain Context Map, Boundary Notes, Ownership MapGap Matrix, Action Plan, Risk NotesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignContextBoundaries
StrategyAnalysisPlanning
OutcomesStrategyBehaviorPlanning
Add more methods