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 |  Agile Starfish Retrospective |  Product Discovery Assumption Mapping |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 45-60 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-12 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Starfish Board, Practice Changes, Experiments | Assumption map, Test backlog, Risk ranking | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementExperimentsTeam | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryAssumptions |