How Do You Define Initiatives and the Assumptions Underneath Them?
You define initiatives by translating each prioritized strategy lever into a specific, sequenced piece of work chosen on its contribution to the goals and time to value — then surfacing the assumptions each initiative depends on and ranking them by likelihood and impact. Initiatives are how a lever becomes executable; assumptions are how you'll later know whether the plan still holds.
Translate levers into concrete initiatives. Each selected lever needs to become specific work with a clear owner and outcome, chosen on criteria that matter to the planning horizon — how much it moves the goals and how quickly it delivers value. Vague levers don't execute; defined initiatives with owners and timelines do.
Sequence them deliberately, because order of operations determines whether the plan compounds or stalls. Some initiatives unlock others; some depend on capability or capital that arrives later. Sequencing the initiatives so each builds on what precedes it is what lets value compound over time rather than dissipate across simultaneous, competing efforts.
Then surface the assumptions each initiative rests on. Every initiative depends on things that must be true for it to succeed — about the market, the customer, the team, the timing. Naming these assumptions explicitly, and ranking them by how likely they are and how much impact they carry if wrong, is what makes the plan testable rather than a leap of faith.
The payoff of explicit assumptions comes later in the planning horizon. When conditions shift — and across a multi-year hold they will — a plan with named assumptions lets you check exactly which premises still hold and which have broken, so you can adjust the affected initiatives rather than discovering failure at a board meeting. Defining initiatives with their assumptions turns the strategic plan into something you can pressure-test and steer, not just launch and hope.
← Back to Topic 3 — Strategic Plan