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
Paper illustration of Product Kata with its method-specific working model.
Product Discovery
Product Kata
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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-2 Wochen je Loop2-6 h1-3 h1-3 h
Participantsdifferent
3-102-82-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Direction, Current metric, Target metric, Experiment note, Learning reportEvent Model, UI Flow, Commands, Read ModelsGap Matrix, Action Plan, Risk NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
OutcomesDiscoveryLearningIterationCoaching
EventsBlueprintDomain-Driven DesignBehavior
StrategyAnalysisPlanning
Domain-Driven DesignBoundariesStrategy
Add more methods