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 |  Delivery RAID Log |  Agile Specification by Example |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 60-90 min pro Feature | 1-2 h |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 | 1-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source | Example Table, Acceptance Tests | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance | AgileRequirementsExamplesBehavior-Driven Development | KnowledgeConceptsMappingSensemaking |