View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Innovation Reverse Brainstorming |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | 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 | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 30-60 min | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-6 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Reverse Ideas, Risk Themes, Solution Ideas | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | BrainstormingIdeationCreativityRisk | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
