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 |  Delivery RAID Log |  Facilitation Team Charter |  Agile ROAM Board |
|---|---|---|---|---|
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. | 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 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 2-4 h | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-12 | 3-15 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Team Charter, Working Norms, Role Notes | ROAM Board, Owner List |
Tagsno overlap | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaboration | RiskAgileTrackingAlignment |