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 Concept Mapping | ![]() Decision Making Cynefin Workshop | ![]() Decision Making DACI |
|---|---|---|---|---|
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. | 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. | 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 Wochen vom Draft bis zur Entscheidung | 1-2 h | 60-180 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 4-20 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Concept Map, Relationship Labels, Knowledge Gaps | Cynefin Map, Domain-specific Actions, Sensemaking Notes | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | KnowledgeConceptsMappingSensemaking | ComplexitySensemakingDecision | DecisionRolesGovernanceAlignment |



