methodatlas
Compare

View methods side by side.

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

Criterion
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
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.The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.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
MediumLowHighHigh
Timedifferent
1-3 h Setup, laufend20-60 minSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
11Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchivePlain-language Explanation, Knowledge Gaps, Study NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
KnowledgeProductivityOrganization
LearningKnowledgeUnderstanding
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Add more methods