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 Expectation Mapping | ![]() Facilitation Team Charter | ![]() Delivery RAID Log | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 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 | 45-90 min | 2-4 h | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | 3-12 | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Team Charter, Working Norms, Role Notes | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCollaboration | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation |



