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 Architecture Decision Record | ![]() Agile NoEstimates | ![]() Decision Making Argument Mapping | ![]() Decision Making Cynefin Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | laufend | 1-3 h | 60-180 min |
Participantsdifferent | 1-3 | 2-12 | 1-8 | 4-20 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Throughput Data, Flow Forecast, Slicing Rules | Argument Map, Evidence Gaps, Decision Rationale | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationForecastingFlow | SensemakingDecisionRationale | ComplexitySensemakingDecision |



