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

Criterion	Architecture arc42	Business Strategy Strategic, Tactical and Operational Planning	Architecture Request for Comments	Business Strategy Strategy Execution Loop
Purposedifferent	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.	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.
Complexitydifferent	Low	Medium	Medium	High
Timedifferent	1-2 Tage	90-180 min	1-3 Wochen vom Draft bis zur Entscheidung	Initial 3-6 h, then monthly or quarterly reviews
Participantsdifferent	1-4	4-12	3-20 Reviewer	5-12
Formatdifferent	Workshop + async	Workshop	Async	Workshop + async
Outputdifferent	Architecture Document, Context View, Runtime View, Deployment View	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
Tagsno overlap	ArchitectureDocumentationCommunication	CadenceGovernanceExecution	ArchitectureDecisionAsyncGovernance	ExecutionCadenceLearningGovernance

Add more methods