View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategic, Tactical and Operational PlanningForce Field Analysisarc42
| Criterion |  Architecture Architecture Decision Record |  Business Strategy Strategic, Tactical and Operational Planning |  Decision Making Force Field Analysis |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 90-180 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 1-3 | 4-12 | 3-12 | 1-4 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution | ChangeDecisionStrategy | ArchitectureDocumentationCommunication |