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 |  Innovation TRIZ |  Innovation Design Charrette |
|---|---|---|---|
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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 30-240 min | 1-4 h | Halber Tag bis mehrere Tage |
Participantsdifferent | 1-6 | 2-8 | 10-50 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Contradiction Statement, Inventive Principles, Solution Concepts | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | InnovationProblem solvingContradictionsCreativity | BrainstormingWorkshopCollaborationIdeation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
