View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Mind Mapping | ![]() Decision Making Cynefin Workshop | ![]() Architecture Architecture Decision Record | ![]() Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | When a topic is still unclear and too many thoughts surface at once, Mind Mapping creates an open surface for ordering them. It makes connections, subtopics, and starting points visible without fixing them too early. | 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. | 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. | 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 | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 60-180 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-10 | 4-20 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Mind Map, Topic Clusters, Open Questions | Cynefin Map, Domain-specific Actions, Sensemaking Notes | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | BrainstormingIdeasMappingStructureFacilitation | ComplexitySensemakingDecision | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |



