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 Runbook ATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis

Criterion	Knowledge Modeling PARA Method	Operations Runbook	Architecture ATAM (Architecture Tradeoff Analysis Method)	Operations Failure Mode and Effects Analysis
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 recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.	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.	For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent	Medium	Low	High	High
Timedifferent	1-3 h Setup, laufend	20-60 min	Several meetings plus preparation and analysis; total effort depends on scope	2-6 h
Participantsdifferent	1	1-4	Evaluation team, architects, and relevant stakeholders	3-10
Formatdifferent	Async	Async	Workshop + async	Workshop
Outputdifferent	PARA Structure, Project Notes, Knowledge Archive	Runbook, Checklist, Escalation Path	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	FMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap	KnowledgeProductivityOrganization	OperationsReliabilityDocumentation	ArchitectureQualityRiskTradeoffsStakeholders	RiskQualityOperationsRoot cause

Add more methods