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 RecordRAID LogStrategic, Tactical and Operational PlanningViews and Beyond
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Delivery RAID Log | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 90-180 min | 1-3 Tage |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 4-12 | 1-4 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | CadenceGovernanceExecution | DocumentationStakeholdersArchitecture |



