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 Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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 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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowLowMedium
Timedifferent
Multiple workshops over several weeksHalf day initial, dann laufend45-90 min1-2 h
Participantsdifferent
2-8Ein Team plus Stakeholder3-124-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkTeam API DocumentExpectation Map, Alignment Notes, AgreementsAlignment Map, Open Issues, Decision Questions
Tagsno overlap
GrowthBehaviorRetention
TeamAlignmentCommunicationService
AlignmentStakeholdersTeam
AlignmentStakeholdersStrategyFacilitation
Add more methods