View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:HEART FrameworkSoftware Architecture CanvasGoal Question MetricArchitecture Communication Canvas
| Criterion | ![]() UX Research HEART Framework | ![]() Architecture Software Architecture Canvas | ![]() Engineering Goal Question Metric | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 120 min initial, dann laufend | 1-2 h | 90-180 min | 60-120 min |
Participantsdifferent | 3-6 | 3-10 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | HEART-GSM Table, Dashboard | Architecture Canvas, Goals, Constraints, Quality Attributes | GQM Table, Metric Profiles | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | CanvasArchitectureAlignmentWorkshop | MetricsMeasurementEngineeringAlignment | ArchitectureCommunicationStakeholdersCanvas |



