View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Force Field AnalysisRequest for CommentsStrategic, Tactical and Operational PlanningArchitecture Decision Record
| Criterion |  Decision Making Force Field Analysis |  Architecture Request for Comments |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 15-45 min |
Participantsdifferent | 3-12 | 3-20 Reviewer | 4-12 | 1-3 |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Planning Levels Map, Cadence Model, Planning Artifact Inventory | ADR File, Decision Log, Rationale |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureDecisionAsyncGovernance | CadenceGovernanceExecution | ArchitectureRationaleDocumentationGovernance |