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