View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategic, Tactical and Operational PlanningFailure Mode and Effects AnalysisStrategy Execution Loop
| Criterion |  Architecture Architecture Decision Record |  Business Strategy Strategic, Tactical and Operational Planning |  Operations Failure Mode and Effects Analysis |  Business Strategy Strategy Execution Loop |
|---|---|---|---|---|
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. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 15-45 min | 90-180 min | 2-6 h | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 1-3 | 4-12 | 3-10 | 5-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | FMEA Table, Risk Priority, Mitigation Actions | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution | RiskQualityOperationsRoot cause | ExecutionCadenceLearningGovernance |