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 Problem Framing Workshop |  Engineering Goal Question Metric |
|---|---|---|---|
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 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-180 min | 60-120 min | 90-180 min |
Participantsdifferent | 1-6 | 4-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | GQM Table, Metric Profiles |
Tagsno overlap | TroubleshootingDiagnosisEngineering | FacilitationAlignmentDiscovery | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
