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 | ![]() Product Discovery MVP Test Matrix | ![]() Decision Making Assumption Surfacing | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|---|
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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-180 min | 45-75 min | 45-90 min | 30-60 min |
Participantsdifferent | 1-6 | 2-8 | 2-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Test Matrix, Test Plan | Assumption List, Critical Assumptions, Learning Plan | Completed Experiment Canvas, Success Metric |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ExperimentsValidationDiscoveryOptions | AssumptionsRiskDecisionDiscovery | ExperimentsValidationDiscoveryHypothesis |



