View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Alignment Mapping | ![]() Delivery RAID Log | ![]() Facilitation Expectation Mapping | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 45-90 min | 60–90 min |
Participantsdifferent | 4-12 | 1-3 maintaining, briefing for everyone | 3-12 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Alignment Map, Open Issues, Decision Questions | RAID Log, Status Report Source | Expectation Map, Alignment Notes, Agreements | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | AlignmentStakeholdersStrategyFacilitation | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersTeam | StakeholdersAlignmentFacilitationChange |



