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 Hypothesis-Driven Troubleshooting |  Architecture Risk Storming |  Decision Making Assumption Surfacing |  Facilitation Decision Jam |
|---|---|---|---|---|
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. | 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. | 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. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-240 min | 60-90 min | 45-90 min | 60-90 min |
Participantsdifferent | 1-6 | 4-12 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption List, Critical Assumptions, Learning Plan | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | RiskArchitectureWorkshopValidation | AssumptionsRiskDecisionDiscovery | FacilitationDecisionProblem solvingWorkshop |