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 GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
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
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitydifferent
MediumLowMediumLow
Timedifferent
Wochen bis Monate je GoalHalf day initial, dann laufend45-90 min45-90 min
Participantsdifferent
3-10Ein Team plus Stakeholder3-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Goals, Idea bank, Step-project list, Tasks, Learning reportsTeam API DocumentImpact Map, Outcome Hypotheses, Delivery OptionsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
RoadmapOutcomesPlanningExperiments
TeamAlignmentCommunicationService
OutcomesStrategyBehaviorPlanning
AlignmentStakeholdersTeam
Add more methods