View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Expectation Mapping | ![]() Facilitation Stakeholder Salience Model | ![]() Product Discovery Smoke Test | ![]() Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Low | Medium | Low | High |
Timedifferent | 45-90 min | 60-90 min | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-12 | 3-6 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop | Async | Async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |



