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 |  Knowledge Modeling Concept Mapping |  Facilitation Consensus Workshop |  Facilitation Dot Voting |
|---|---|---|---|---|
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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-240 min | 1-2 h | 1-3 h | 5-15 min |
Participantsdifferent | 1-6 | 1-8 | 5-30 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Concept Map, Relationship Labels, Knowledge Gaps | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | KnowledgeConceptsMappingSensemaking | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |