View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Customer Journey Canvas |  UX Research HEART Framework |  Architecture Software Architecture Canvas |  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. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 120 min initial, dann laufend | 1-2 h | 90-180 min |
Participantsdifferent | 3-10 | 3-6 | 3-10 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | HEART-GSM Table, Dashboard | Architecture Canvas, Goals, Constraints, Quality Attributes | GQM Table, Metric Profiles |
Tagsno overlap | JourneyCustomerService designCanvas | MetricsUX researchMeasurementSatisfaction | CanvasArchitectureAlignmentWorkshop | MetricsMeasurementEngineeringAlignment |