View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling IBIS |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Power Interest Grid |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 30-240 min | 30-60 min | 60-90 min |
Participantsdifferent | 2-8 | 1-6 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Power Interest Grid, Strategy per Stakeholder | Salience Diagram, Strategy per Class |
Tagsno overlap | RationaleKnowledgeDecision | TroubleshootingProblem solvingDiagnosis | StakeholdersFacilitationAlignmentPlanning | StakeholdersFacilitationAlignmentGovernance |