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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Fault Isolation.
Engineering
Fault Isolation
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Purposedifferent
For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.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.When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.
Complexitysame
MediumMediumMediumMedium
Timedifferent
45-90 min2–4 h review as a planning range; preparation and evaluation additional30-180 min30-240 min
Participantsdifferent
2-5Designers, developers as users, and facilitation1-61-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsFault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaHypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary
Tagsno overlap
LeanProblem solvingCoachingOperations
ArchitectureEngineeringFeedbackValidationTasks
TroubleshootingDiagnosisEngineering
TroubleshootingProblem solvingDiagnosis
Add more methods