View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling PARA Method | ![]() Agile Starfish Retrospective | ![]() Product Discovery Assumption Mapping | ![]() Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
Purposedifferent | 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 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 45-60 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 1 | 4-12 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Assumption map, Test backlog, Risk ranking | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryAssumptions |



