View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Architecture Architecture Decision Record |  Architecture C4 Model |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Low | Low |
Timedifferent | 2-4 h workshop plus review | 15-45 min | 1-4 h | 30-60 min |
Participantsdifferent | 4-10 | 1-3 | 1-5 | 2-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | AlignmentExecutionGoalsCausality | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | DecisionRolesGovernanceAlignment |