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 Request for Comments |  Business Strategy Balanced Scorecard |  Decision Making Force Field Analysis |  Product Strategy Counter Metrics |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Wochen | 45-90 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 3-12 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Balanced Scorecard, Strategic Measures, Initiative Map | Force Field Map, Change Levers, Risk Notes | Counter Metric List, Guardrail Definitions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StrategyMetricsExecution | ChangeDecisionStrategy | MetricsMeasurementStrategyExperiments |