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 | ![]() Facilitation Stakeholder Mapping | ![]() Architecture Architecture Decision Record | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 60–90 min | 15-45 min | 60-90 min |
Participantsdifferent | 2-8 | 2-8 | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Stakeholder Map, Engagement Plan, Risk Notes | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class |
Tagsno overlap | RationaleKnowledgeDecision | StakeholdersAlignmentFacilitationChange | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance |



