View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingAssumption SurfacingARID (Active Reviews for Intermediate Designs)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Decision Making Assumption Surfacing |  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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 |
Timedifferent | 30-240 min | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-6 | 2-8 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Assumption List, Critical Assumptions, Learning Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AssumptionsRiskDecisionDiscovery | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
