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 |  Facilitation Consensus Workshop |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Dot Voting |
|---|---|---|---|---|
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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-180 min | 1-3 h | 30-240 min | 5-15 min |
Participantsdifferent | 1-6 | 5-30 | 1-6 | 3-20 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Consensus Clusters, Theme Titles, Priority Areas | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | TroubleshootingDiagnosisEngineering | FacilitationConsensusWorkshopAlignment | TroubleshootingProblem solvingDiagnosis | FacilitationVotingConsensusPrioritization |