Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Knowledge Mapping ATAM (Architecture Tradeoff Analysis Method)Fake Door Test Assumption Mapping

Criterion	Knowledge Modeling Knowledge Mapping	Architecture ATAM (Architecture Tradeoff Analysis Method)	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.	ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.	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	High	Medium	Medium
Timedifferent	1-3 h	Several meetings plus preparation and analysis; total effort depends on scope	1-5 Tage	45-60 min
Participantsdifferent	3-12	Evaluation team, architects, and relevant stakeholders	Nutzertraffic	2-8
Formatdifferent	Workshop	Workshop + async	Async	Workshop + async
Outputdifferent	Knowledge Map, Critical Knowledge Areas, Transfer Plan	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Click Data, Interest Signal, Learning Decision	Assumption map, Test backlog, Risk ranking
Tagsno overlap	KnowledgeMappingRisk	ArchitectureQualityRiskTradeoffsStakeholders	ValidationExperimentsDemandDiscovery	AssumptionsRiskExperimentsValidation

Add more methods