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
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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.When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.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.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
MediumLowLowMedium
Timedifferent
1-3 h30-60 min1-2 h90-180 min
Participantsdifferent
3-102-63-103-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesCounter Metric List, Guardrail DefinitionsArchitecture Canvas, Goals, Constraints, Quality AttributesGQM Table, Metric Profiles
Tagsno overlap
JourneyCustomerService designCanvas
MetricsMeasurementStrategyExperiments
CanvasArchitectureAlignmentWorkshop
MetricsMeasurementEngineeringAlignment
Add more methods