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 | ![]() Systems Thinking Evaporating Cloud | ![]() Product Discovery Smoke Test | ![]() Product Discovery Fake Door 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h Setup, laufend | 60-120 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 1 | 2-8 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Async | Workshop | Async | Async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | KnowledgeProductivityOrganization | Theory of ConstraintsAssumptionsSystems thinking | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |



