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 |  Engineering Goal Question Metric |  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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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 | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Wochen | 90-180 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 3-6 | 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 | GQM Table, Metric Profiles | Counter Metric List, Guardrail Definitions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StrategyMetricsExecution | MetricsMeasurementEngineeringAlignment | MetricsMeasurementStrategyExperiments |