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
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Flywheel.
Growth
Flywheel
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
0.5-2 TageMultiple workshops over several weeks60-120 min2-6 h
Participantsdifferent
6-122-83-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapHooked loop, Trigger map, Reward design, Ethics checkFlywheel Map, Friction Points, Growth Levers, Experiment BacklogEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
Service designOperationsJourneyBlueprint
GrowthBehaviorRetention
GrowthRetentionConversion
EventsBlueprintDomain-Driven DesignBehavior
Add more methods