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
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
Paper illustration for Domain Context Map
Domain Modeling
Domain 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.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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-2 Wochen je Loop1-3 h1-3 h1-3 h
Participantsdifferent
3-102-82-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Direction, Current metric, Target metric, Experiment note, Learning reportGap Matrix, Action Plan, Risk NotesContext Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
OutcomesDiscoveryLearningIterationCoaching
StrategyAnalysisPlanning
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
Add more methods