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 a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
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.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.GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list.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
45-90 min1-3 hWochen bis Monate je Goal1-3 h
Participantsdifferent
3-82-83-103-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsContext Map, Integration Patterns, Boundary NotesGoals, Idea bank, Step-project list, Tasks, Learning reportsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
OutcomesStrategyBehaviorPlanning
Domain-Driven DesignBoundariesStrategy
RoadmapOutcomesPlanningExperiments
Domain-Driven DesignContextBoundaries
Add more methods