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

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

Add more methods