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
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
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
Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.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
MediumMediumHighHigh
Timedifferent
1-2 h1-3 h Setup, laufendSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
1-81Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsPARA Structure, Project Notes, Knowledge ArchivePrioritized 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
KnowledgeConceptsMappingSensemaking
KnowledgeProductivityOrganization
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Add more methods