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 IBIS |  Team Design Team Topologies Interaction Modes |  Architecture Architecture Decision Record |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | Half day | 15-45 min | 30-60 min |
Participantsdifferent | 2-8 | Team-Leads plus Architecture | 1-3 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Interaction Heat Map, Agreements per Pair | ADR File, Decision Log, Rationale | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | RationaleKnowledgeDecision | TeamAlignmentCollaborationOrganization | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernanceAlignment |