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 arc42 Strategy Execution Loop

Criterion	Architecture Request for Comments	Business Strategy Strategic, Tactical and Operational Planning	Architecture arc42	Business Strategy Strategy Execution Loop
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.	arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.	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	Medium	Low	High
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	90-180 min	1-2 Tage	Initial 3-6 h, then monthly or quarterly reviews
Participantsdifferent	3-20 Reviewer	4-12	1-4	5-12
Formatdifferent	Async	Workshop	Workshop + async	Workshop + async
Outputdifferent	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Planning Levels Map, Cadence Model, Planning Artifact Inventory	Architecture Document, Context View, Runtime View, Deployment View	Execution Loop, Review Cadence, Strategic Learning Log
Tagsno overlap	ArchitectureDecisionAsyncGovernance	CadenceGovernanceExecution	ArchitectureDocumentationCommunication	ExecutionCadenceLearningGovernance

Add more methods