View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Delivery RAID Log |  Knowledge Modeling Knowledge Mapping |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | RAID Log, Status Report Source | Knowledge Map, Critical Knowledge Areas, Transfer Plan | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingMappingBoundariesChange | RiskTrackingStakeholdersGovernance | KnowledgeMappingRisk | Systems thinkingFramingStakeholders |