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 | ![]() Systems Thinking Futures Wheel | ![]() Architecture Request for Comments | ![]() 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. | The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Low |
Timedifferent | 1-3 h | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 2-8 | 3-10 | 3-20 Reviewer | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Futures Wheel, Consequence Chains, Strategic Signals | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | RationaleKnowledgeDecision | ForesightSystems thinkingSignals | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |



