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 Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Purposedifferent
When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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 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
MediumLowMediumMedium
Timedifferent
1-3 h1-2 h90-180 min initial, dann laufend90-180 min
Participantsdifferent
3-103-103-83-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesArchitecture Canvas, Goals, Constraints, Quality AttributesKPI Tree, Owner ListGQM Table, Metric Profiles
Tagsno overlap
JourneyCustomerService designCanvas
CanvasArchitectureAlignmentWorkshop
MetricsStrategyAlignmentMeasurement
MetricsMeasurementEngineeringAlignment
Add more methods