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 Spotify Model Mapping |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 2-8 | 5-15 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Spotify Model Map, Action List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | RationaleKnowledgeDecision | TeamOrganizationAlignmentDiagnosis | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |