View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Engineering Fault Isolation |  Engineering Hypothesis-Driven Troubleshooting |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 60-90 min | 30-180 min | 30-240 min | Half day |
Participantsdifferent | 4-12 | 1-6 | 1-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | RiskArchitectureWorkshopValidation | TroubleshootingDiagnosisEngineering | TroubleshootingProblem solvingDiagnosis | StrategyBusiness modelRiskDiagnosis |