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 | ![]() Architecture Architecture Decision Record | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
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. | 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 change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 15-45 min | 45-90 min |
Participantsdifferent | 2-8 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






