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 |  Knowledge Modeling Feynman Technique |  Knowledge Modeling Concept Mapping |  Agile ROAM Board |
|---|---|---|---|---|
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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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 | 30 min Setup, dann laufend | 20-60 min | 1-2 h | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 | 1-8 | 3-15 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Plain-language Explanation, Knowledge Gaps, Study Notes | Concept Map, Relationship Labels, Knowledge Gaps | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | LearningKnowledgeUnderstanding | KnowledgeConceptsMappingSensemaking | RiskAgileTrackingAlignment |