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 Assumption Surfacing |  Facilitation Consensus Workshop |  Facilitation Problem Framing Workshop |
|---|---|---|---|---|
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. | 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 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 a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-180 min | 45-90 min | 1-3 h | 60-120 min |
Participantsdifferent | 1-6 | 2-8 | 5-30 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Assumption List, Critical Assumptions, Learning Plan | Consensus Clusters, Theme Titles, Priority Areas | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | TroubleshootingDiagnosisEngineering | AssumptionsRiskDecisionDiscovery | FacilitationConsensusWorkshopAlignment | FacilitationAlignmentDiscovery |