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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-6 h90-180 min initial, dann laufend120 min initial, dann laufend1-2 h
Participantsdifferent
2-83-83-64-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsKPI Tree, Owner ListHEART-GSM Table, DashboardAlignment Map, Open Issues, Decision Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
MetricsStrategyAlignmentMeasurement
MetricsUX researchMeasurementSatisfaction
AlignmentStakeholdersStrategyFacilitation
Add more methods