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 | ![]() Growth Funnel Analysis | ![]() Facilitation Stakeholder Mapping | ![]() 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. | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | 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 | Low | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 60–90 min | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-5 | 2-8 | 3-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Funnel report, Drop-off analysis, Optimization hypotheses | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AnalyticsConversionGrowth | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |



