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
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
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
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 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.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h45-90 min1-3 h
Participantsdifferent
2-82-83-82-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeGap Matrix, Action Plan, Risk NotesImpact Map, Outcome Hypotheses, Delivery OptionsPESTLE Map, External Risks, Strategic Questions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
StrategyAnalysisPlanning
OutcomesStrategyBehaviorPlanning
StrategyMarketAnalysis
Add more methods