View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Decision Making Risk Matrix |  Product Discovery Assumption Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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 a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 30-180 min | 30-60 min | 45-60 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-6 | 3-10 | 2-8 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Risk Matrix, Top Risk List | Assumption map, Test backlog, Risk ranking | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | TroubleshootingDiagnosisEngineering | RiskDecisionPrioritizationAssessment | AssumptionsRiskExperimentsValidation | ArchitectureEngineeringFeedbackValidationTasks |