View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Product Strategy DIBB |  Facilitation Stakeholder Salience Model |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 1-2 Tage | 1-2 h | 60-90 min | 30-60 min |
Participantsdifferent | 1-4 | 2-8 | 3-6 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | DIBB document, Belief list, Bet list, Learning report | Salience Diagram, Strategy per Class | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDocumentationCommunication | StrategyDecisionAssumptionsHypothesis | StakeholdersFacilitationAlignmentGovernance | DecisionRolesGovernanceAlignment |