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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Empathy Mapping
UX Research
Empathy Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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 lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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
MediumMediumLowMedium
Timedifferent
2-6 h1-3 h30–60 min1-3 h
Participantsdifferent
2-82-84-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsGap Matrix, Action Plan, Risk NotesEmpathy Map, Assumptions List, Research GapsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
StrategyAnalysisPlanning
SynthesisQualitativeWorkshop
Domain-Driven DesignBoundariesStrategy
Add more methods