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 Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Purposedifferent
When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.
Complexitysame
MediumMediumMedium
Timedifferent
1-2 Tage2-6 h1-3 h
Participantsdifferent
10-502-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Kano Matrix, Feature Classes, Priority ThemesEvent Model, UI Flow, Commands, Read ModelsGap Matrix, Action Plan, Risk Notes
Tagsno overlap
SatisfactionPrioritizationCustomer
EventsBlueprintDomain-Driven DesignBehavior
StrategyAnalysisPlanning
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis