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 Architecture Decision Record |  Product Strategy KPI Tree |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 90-180 min initial, dann laufend | 45-90 min |
Participantsdifferent | 1-3 | 3-8 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | KPI Tree, Owner List | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsStrategyAlignmentMeasurement | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
