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 Sailboat Retrospective |  Agile Starfish Retrospective |  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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 45-90 min | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-12 | 4-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | AssumptionsRiskExperimentsValidation |