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 Execution Loop |  Architecture Request for Comments |  Decision Making Force Field Analysis |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | 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. | 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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | Halber Tag bis mehrere Wochen |
Participantsdifferent | 5-12 | 3-20 Reviewer | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | StrategyMetricsExecution |