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 Knowledge Mapping | ![]() Knowledge Modeling IBIS | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 1-3 h | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 2-8 | 1-3 |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | KnowledgeMappingRisk | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance |



