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 Knowledge Mapping | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Fake Door Test | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 15-45 min | 1-5 Tage | 45-60 min |
Participantsdifferent | 3-12 | 1-3 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | ADR File, Decision Log, Rationale | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | KnowledgeMappingRisk | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |



