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 arc42 Strategic, Tactical and Operational Planning Strategy Execution Loop

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

Add more methods