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

Criterion	Business Strategy Strategic, Tactical and Operational Planning	Architecture Request for Comments	Decision Making Force Field Analysis	Business Strategy Strategy Execution Loop
Purposedifferent	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.	In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.	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	Low	High
Timedifferent	90-180 min	1-3 Wochen vom Draft bis zur Entscheidung	45-90 min	Initial 3-6 h, then monthly or quarterly reviews
Participantsdifferent	4-12	3-20 Reviewer	3-12	5-12
Formatdifferent	Workshop	Async	Workshop	Workshop + async
Outputdifferent	Planning Levels Map, Cadence Model, Planning Artifact Inventory	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Force Field Map, Change Levers, Risk Notes	Execution Loop, Review Cadence, Strategic Learning Log
Tagsno overlap	CadenceGovernanceExecution	ArchitectureDecisionAsyncGovernance	ChangeDecisionStrategy	ExecutionCadenceLearningGovernance

Add more methods