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 |  Business Strategy McKinsey 7S |  Facilitation Expectation Mapping |  Facilitation Alignment 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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. | 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 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 2-4 h | 45-90 min | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | 7S Assessment, Alignment Gaps, Change Actions | Expectation Map, Alignment Notes, Agreements | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OrganizationStrategyAlignmentChange | AlignmentStakeholdersTeam | AlignmentStakeholdersStrategyFacilitation |