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:Request for Comments Strategic, Tactical and Operational Planning Strategy Execution Loop Architecture Decision Record

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

Add more methods