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

Criterion	Business Strategy Strategic, Tactical and Operational Planning	Architecture Request for Comments	Business Strategy Strategy Execution Loop	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.	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.	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	High	Low
Timedifferent	90-180 min	1-3 Wochen vom Draft bis zur Entscheidung	Initial 3-6 h, then monthly or quarterly reviews	15-45 min
Participantsdifferent	4-12	3-20 Reviewer	5-12	1-3
Formatdifferent	Workshop	Async	Workshop + async	Async
Outputdifferent	Planning Levels Map, Cadence Model, Planning Artifact Inventory	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Execution Loop, Review Cadence, Strategic Learning Log	ADR File, Decision Log, Rationale
Tags1 shared	CadenceGovernanceExecution	ArchitectureDecisionAsyncGovernance	ExecutionCadenceLearningGovernance	ArchitectureRationaleDocumentationGovernance

Add more methods