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 |  Operations 5 Whys |  Architecture Request for Comments |
|---|---|---|---|---|
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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-45 min | 15-30 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 1-3 | 2-6 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving | ArchitectureDecisionAsyncGovernance |