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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Fault Isolation.
Engineering
Fault Isolation
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.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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
30-240 min2–4 h review as a planning range; preparation and evaluation additional1-2 h30-180 min
Participantsdifferent
1-6Designers, developers as users, and facilitation3-101-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsArchitecture Canvas, Goals, Constraints, Quality AttributesFault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ArchitectureEngineeringFeedbackValidationTasks
CanvasArchitectureAlignmentWorkshop
TroubleshootingDiagnosisEngineering
Add more methods