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 KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
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.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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.
Complexitydifferent
HighMediumLowMedium
Timedifferent
0.5-2 Tage90-180 min initial, dann laufend60–90 min90-180 min
Participantsdifferent
6-123-82-83-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapKPI Tree, Owner ListStakeholder Map, Engagement Plan, Risk NotesGQM Table, Metric Profiles
Tagsno overlap
Service designOperationsJourneyBlueprint
MetricsStrategyAlignmentMeasurement
StakeholdersAlignmentFacilitationChange
MetricsMeasurementEngineeringAlignment
Add more methods