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 Argument Mapping Strategy Execution Loop

Criterion	Architecture Request for Comments	Business Strategy Strategic, Tactical and Operational Planning	Decision Making Argument Mapping	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.	When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.	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	Medium	High
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	90-180 min	1-3 h	Initial 3-6 h, then monthly or quarterly reviews
Participantsdifferent	3-20 Reviewer	4-12	1-8	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	Argument Map, Evidence Gaps, Decision Rationale	Execution Loop, Review Cadence, Strategic Learning Log
Tagsno overlap	ArchitectureDecisionAsyncGovernance	CadenceGovernanceExecution	SensemakingDecisionRationale	ExecutionCadenceLearningGovernance

Add more methods