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 Strategy Lean Canvas |  Business Strategy Business Model Stress 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. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | Half day | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 3-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Lean Canvas, Core Assumptions, Experiment Backlog | Stress Test Report, Action Plan per Scenario | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | StartupLeanAssumptionsBusiness model | StrategyBusiness modelRiskDiagnosis | AssumptionsRiskExperimentsValidation |