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 RAID Log | ![]() UX Design Lean UX Canvas | ![]() Product Discovery Fake Door Test | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment. | 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 | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 2-3 h | 1-5 Tage | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | Nutzertraffic | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Completed Lean UX Canvas, Hypothesis list, First experiment | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | CanvasHypothesisOutcomesDiscovery | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |



