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

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

Add more methods