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 Contradiction Analysis |  Innovation Brainstorming |
|---|---|---|---|
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. | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-240 min | 60-120 min | 30-60 min |
Participantsdifferent | 1-6 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ContradictionsInnovationProblem solving | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
