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 | ![]() Product Discovery Smoke Test | ![]() Delivery RAID Log |
|---|---|---|---|
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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 1-5 Tage | 30 min Setup, dann laufend |
Participantsdifferent | 3-12 | Nutzertraffic | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Interest Metrics, Conversion Signal, Learning Note | RAID Log, Status Report Source |
Tagsno overlap | AlignmentStakeholdersTeam | ValidationExperimentsDemandGrowth | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






