View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopForce Field AnalysisRequest for CommentsArchitecture Decision Record
| Criterion |  Business Strategy Strategy Execution Loop |  Decision Making Force Field Analysis |  Architecture Request for Comments |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 5-12 | 3-12 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Force Field Map, Change Levers, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | ChangeDecisionStrategy | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |