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 Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-2 h2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min
Participantsdifferent
3-123-10Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsFMEA Table, Risk Priority, Mitigation ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Systems thinkingTradeoffsLeadership
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Root causeQualityOperations
Add more methods