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

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

Add more methods