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 Request for Comments |  Knowledge Modeling IBIS |  Knowledge Modeling Concept Mapping |  Decision Making Cynefin Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-2 h | 60-180 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-8 | 4-20 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | ComplexitySensemakingDecision |