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 |  Engineering Kanban |  Decision Making Three-Point Estimation |
|---|---|---|---|
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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | Ongoing | 10-30 min je Item |
Participantsdifferent | 1-3 | 2-12 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Kanban board, WIP policies, Flow metrics | Three-Point Estimate, Risk Range, Assumption Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | FlowVisual managementDelivery | EstimationUncertaintyForecasting |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
