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 Architecture Communication Canvas | ![]() Product Discovery Smoke Test | ![]() Growth A/B Testing |
|---|---|---|---|---|
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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 120 min initial, dann laufend | 60-120 min | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-6 | 2-8 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | HEART-GSM Table, Dashboard | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | ArchitectureCommunicationStakeholdersCanvas | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |



