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 |  Facilitation Expectation Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 60–90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Expectation Map, Alignment Notes, Agreements | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersTeam | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
