View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsStrategic, Tactical and Operational PlanningCounter MetricsArchitecture Decision Record
| Criterion |  Architecture Request for Comments |  Business Strategy Strategic, Tactical and Operational Planning |  Product Strategy Counter Metrics |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 30-60 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 2-6 | 1-3 |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Counter Metric List, Guardrail Definitions | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CadenceGovernanceExecution | MetricsMeasurementStrategyExperiments | ArchitectureRationaleDocumentationGovernance |