Operational strategy is the plan for how the work actually gets done: capacity, process, systems, suppliers and the sequence. Business strategy decides where to compete. Operational strategy decides whether you can deliver on that decision.
Most plans that fail do not fail at the choosing. They fail at the handover between those two, where a commitment is made and nobody checks whether the business can do it.
The three levels, and which one this is
| Level | The question it answers | Typical horizon |
|---|---|---|
| Corporate strategy | What businesses should we be in | Three to five years |
| Business strategy | Where do we compete, and how do we win there | One to three years |
| Operational strategy | How does the work get done, and can we do it | Quarterly to annual |
Operational strategy is the bottom row, and it is the row that touches reality. It is where "move upmarket" becomes "we need two more implementation people by March or the onboarding queue hits six weeks", which is a sentence somebody can act on.
What it actually covers
Capacity. How much you can deliver, by when, with what you have. This is the constraint that quietly decides most plans. A growth target that implies a third more delivery with the same team is not a stretch goal, it is an arithmetic error, and the only question is which quarter it surfaces in.
Process. How standardised the work is. Bespoke work scales with headcount. Standard work scales with volume. Choosing between them is a strategic decision with a cost attached either way, and it is usually made by accident.
Systems. What the work runs on, and where the record lives. Worth naming explicitly, because an operational plan that depends on information nobody can find is a plan that will be delivered late and reported optimistically.
Supply. Who you depend on, and what happens when one of them fails. Single points of failure are cheap right up until the week they are not.
Sequence. The order things happen in. Two initiatives that are both sensible can be impossible together if they need the same people in the same month. Sequencing is the least glamorous part of operational strategy and the part that most often saves a year.
Where it goes wrong
The gap is almost never a missing document. It is that the operational plan and the business plan are owned by different people, reviewed in different meetings, and written in different units. One is in markets and segments. The other is in headcount and weeks. Nobody converts between them, so the first time anyone notices they disagree is when a date is missed.
The research people reach for here is usually Sull, Homkes and Sull in Harvard Business Review, 2015, who found that the common failure is not a lack of alignment up and down the hierarchy but a lack of coordination across it. Operational strategy is where that shows: the capacity to deliver a commitment usually sits in a different team from the one that made it.
Making it something you can run
Three things make an operational strategy real rather than filed.
One named owner per commitment, not a function. "Operations" cannot be asked how it is going. A person can.
A measure that can go down. Cycle time, queue length, cost to serve, utilisation against a sensible ceiling. If every measure on the plan only improves when you work harder, it is an activity report.
A review interval set before the target. Decide when you will look at it while you still have no stake in the answer. Deciding afterwards means you look when it feels safe to look.
Empiraa GPS is a strategy and accountability platform that helps businesses deliver their priorities without chasing updates across spreadsheets and meetings. The operational plan and the business plan sit in the same place, with the same owners and the same measures, so the handover between them is visible rather than assumed.
Related reading: what market presence is, and how to measure it, and why strategy execution fails.
Operational strategy has a definition on this site, and strategy execution best practices covers the operating rhythm around it.
