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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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
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.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.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-2 Wochen je Loop1-3 h1-3 h45-90 min
Participantsdifferent
3-103-102-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Direction, Current metric, Target metric, Experiment note, Learning reportDomain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary NotesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
OutcomesDiscoveryLearningIterationCoaching
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
OutcomesStrategyBehaviorPlanning
Add more methods