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:PARA Method Bottleneck Analysis ATAM (Architecture Tradeoff Analysis Method)Knowledge Mapping

Criterion	Knowledge Modeling PARA Method	Operations Bottleneck Analysis	Architecture ATAM (Architecture Tradeoff Analysis Method)	Knowledge Modeling Knowledge Mapping
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.	For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.	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.	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.
Complexitydifferent	Medium	Medium	High	Medium
Timedifferent	1-3 h Setup, laufend	1-3 h	Several meetings plus preparation and analysis; total effort depends on scope	1-3 h
Participantsdifferent	1	3-8	Evaluation team, architects, and relevant stakeholders	3-12
Formatdifferent	Async	Workshop + async	Workshop + async	Workshop
Outputdifferent	PARA Structure, Project Notes, Knowledge Archive	Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Knowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap	KnowledgeProductivityOrganization	FlowMeasurementConstraints	ArchitectureQualityRiskTradeoffsStakeholders	KnowledgeMappingRisk

Add more methods