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 | ![]() Architecture Architecture Communication Canvas | ![]() Product Discovery Smoke 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 60-120 min | 1-5 Tage | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | Nutzertraffic | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation |



