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 |  Knowledge Modeling Concept Mapping |  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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | 1-2 h | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 1-8 | 3-15 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Concept Map, Relationship Labels, Knowledge Gaps | ROAM Board, Owner List |
Tagsno overlap | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | KnowledgeConceptsMappingSensemaking | RiskAgileTrackingAlignment |