View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsArgument MappingStrategic, Tactical and Operational PlanningCynefin Workshop
| Criterion | ![]() Architecture Request for Comments | ![]() Decision Making Argument Mapping | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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 | 90-180 min | 60-180 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 4-12 | 4-20 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | CadenceGovernanceExecution | ComplexitySensemakingDecision |



