View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Sprint |  Product Discovery Solution Interview |  Facilitation Stakeholder Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | High | Medium | Low | Medium |
Timedifferent | 4-5 Tage | 30-60 min je Interview | 60–90 min | 60-90 min |
Participantsdifferent | 5-8 | 5-10 Interviews | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prototype, Test Findings, Decision Rationale | Solution Feedback, Objection List, Validation Notes | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | Design sprintPrototypeValidationInnovation | ValidationInterviewsPrototype | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |