View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Decision Making Decision Rights Mapping |  Facilitation Expectation Mapping |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 90-180 min | 45-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-12 | 4-12 | 3-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Workshop | Async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Decision Rights Matrix, Agreement | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source |
Tagsno overlap | KnowledgeMappingRisk | DecisionGovernanceAlignmentResponsibility | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance |