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 |  Knowledge Modeling PARA Method |  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 PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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 | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 h Setup, laufend | 45-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 | 2-8 |
Formatdifferent | Async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | PARA Structure, Project Notes, Knowledge Archive | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskTrackingStakeholdersGovernance | KnowledgeProductivityOrganization | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
