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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumHighMedium
Timedifferent
30-240 minSeveral meetings plus preparation and analysis; total effort depends on scope2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-6Evaluation team, architects, and relevant stakeholdersDesigners, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureEngineeringFeedbackValidationTasks
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Fault Isolation.
Engineering
Fault Isolation
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving