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 |  Product Discovery Smoke Test |  Operations 5 Whys |  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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-5 Tage | 15-30 min | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Nutzertraffic | 2-6 | 2-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Interest Metrics, Conversion Signal, Learning Note | Root cause notes, Countermeasures | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandGrowth | Root causeIncidentLeanProblem solving | AssumptionsRiskExperimentsValidation |