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 | ![]() Business Strategy Strategy Execution Loop | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. |
Complexitydifferent | Low | High | Low |
Timedifferent | 15-45 min | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min |
Participantsdifferent | 1-3 | 5-12 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Execution Loop, Review Cadence, Strategic Learning Log | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ExecutionCadenceLearningGovernance | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






