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 HEART Framework with its method-specific working model.
UX Research
HEART Framework
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h120 min initial, dann laufend1-2 h1-2 h
Participantsdifferent
3-103-63-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesHEART-GSM Table, DashboardInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
JourneyCustomerService designCanvas
MetricsUX researchMeasurementSatisfaction
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods