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
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.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.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
1 Tag bis mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional30-180 min30-240 min
Participantsdifferent
4-10Designers, developers as users, and facilitation1-61-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsPrioritized 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
InnovationPrototypeResearch
ArchitectureEngineeringFeedbackValidationTasks
TroubleshootingDiagnosisEngineering
TroubleshootingProblem solvingDiagnosis
Add more methods