Compare

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 Planning Architecture Decision Record Request for Comments Strategy Execution Loop

Criterion	Business Strategy Strategic, Tactical and Operational Planning	Architecture Architecture Decision Record	Architecture Request for Comments	Business Strategy Strategy Execution Loop
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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.	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	Medium	Low	Medium	High
Timedifferent	90-180 min	15-45 min	1-3 Wochen vom Draft bis zur Entscheidung	Initial 3-6 h, then monthly or quarterly reviews
Participantsdifferent	4-12	1-3	3-20 Reviewer	5-12
Formatdifferent	Workshop	Async	Async	Workshop + async
Outputdifferent	Planning Levels Map, Cadence Model, Planning Artifact Inventory	ADR File, Decision Log, Rationale	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Execution Loop, Review Cadence, Strategic Learning Log
Tags1 shared	CadenceGovernanceExecution	ArchitectureRationaleDocumentationGovernance	ArchitectureDecisionAsyncGovernance	ExecutionCadenceLearningGovernance

Add more methods