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 |  Delivery RAID Log |  Product Discovery Fake Door Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-5 Tage | 45-60 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | Nutzertraffic | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |