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 Research HEART Framework |  Architecture arc42 |  Growth Pirate Metrics AARRR |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks. | 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 Tage | 1-2 h Setup, laufend | 60-120 min |
Participantsdifferent | 3-6 | 1-4 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HEART-GSM Table, Dashboard | Architecture Document, Context View, Runtime View, Deployment View | AARRR funnel, Metric baseline, Experiment backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | ArchitectureDocumentationCommunication | GrowthMetricsExperiments | ArchitectureCommunicationStakeholdersCanvas |