View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Communication Plan | ![]() Delivery RAID Log | ![]() Product Discovery Smoke Test | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 2-6 | 1-3 maintaining, briefing for everyone | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | RAID Log, Status Report Source | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |



