View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Goal Question Metric |  Architecture Request for Comments |  Product Strategy KPI Tree |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min initial, dann laufend | 1-2 h |
Participantsdifferent | 3-6 | 3-20 Reviewer | 3-8 | 4-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | GQM Table, Metric Profiles | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | KPI Tree, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | ArchitectureDecisionAsyncGovernance | MetricsStrategyAlignmentMeasurement | AlignmentStakeholdersStrategyFacilitation |