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 |  Product Strategy Counter Metrics |  Decision Making Decision Rights Mapping |  Engineering Goal Question Metric |
|---|---|---|---|---|
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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 90-180 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 2-6 | 4-12 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Counter Metric List, Guardrail Definitions | Decision Rights Matrix, Agreement | GQM Table, Metric Profiles |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | MetricsMeasurementStrategyExperiments | DecisionGovernanceAlignmentResponsibility | MetricsMeasurementEngineeringAlignment |