Operations Plan

An operations plan is the document that translates strategic direction into specific operational commitments: org structure, processes, systems, milestones, and resource allocation. Typically built annually alongside the financial budget and updated as conditions change, the plan is the connective tissue between strategy and execution. Strategy without an operations plan is aspiration; operations plan without strategy is busywork. The combination is execution.

The standard components:

Org structure:

• Current state: existing teams and reporting.
• Future state: planned teams, new functions, reporting evolution.
• Hiring plan tied to org structure.

Processes and rituals:

• How decisions get made.
• Meeting cadences (1:1s, team meetings, exec meetings, all-hands).
• Performance management cycles.
• Communication norms.

Systems and infrastructure:

• Tooling stack (CRM, ERP, HR, finance, engineering, marketing).
• Data and analytics infrastructure.
• Security and compliance systems.
• Office and remote work infrastructure.

Milestones and timeline:

• Major initiatives with target completion dates.
• Dependencies between initiatives.
• Risk and contingency planning.

Resource allocation:

• Budget by department.
• Headcount by team.
• Capital investment priorities.

How operations plans differ by stage:

Early-stage: minimal formal operations plan. Founders adjust as they go. Hiring plan is the primary planning artifact.

Series A-B: light operations plan, mostly focused on hiring and key system investments. Annual cadence starting.

Growth stage: deliberate operations plan with cross-functional sections (engineering, sales, marketing, customer success, finance, ops). Annual creation, quarterly updates.

Mature: institutionalized operations planning with dedicated business operations team. Multi-year operations roadmaps.

The connection to other planning artifacts:

Strategic plan: tells you what we'll do at strategic level.

Annual plan: integrates strategy + finance + ops + hiring into yearly view.

Operations plan: the operational detail of the annual plan.

OKRs: the quarterly execution layer.

Hiring plan: the people layer of operations.

Budget: the financial layer of operations.

Common operations plan failures:

Disconnected from strategy: operational decisions made without strategic context.

No milestones: operations plan that doesn't specify what gets done by when.

Static: built once, not updated as conditions change.

Over-detailed: every operational nuance documented, nothing prioritized.

Under-detailed: high-level only, no operational specifics.

What founders get wrong: Building strategic plans and budgets without an operations plan tying them together, then being surprised when execution doesn't match strategy. The right discipline: explicit operations plan with milestones, dependencies, resource allocation. Updated as conditions change. Connects strategy to execution.

Related: Annual Planning · Strategic Planning · Hiring Plan · Expense Budget · OKRs

FAQ

What is an operations plan?
A document translating strategic direction into specific operational commitments: org structure, processes, systems, milestones, and resource allocation. Typically built annually alongside the financial budget. The connective tissue between strategy and execution.

How is operations plan different from strategic plan?
Strategic plan: what we'll do at strategic level. Operations plan: how we'll actually do it operationally. Strategy without ops plan is aspiration; ops plan without strategy is busywork. Combination is execution.

When does operations planning become important?
Light operations planning starts at Series A-B (focused on hiring and key system investments). Deliberate operations planning at growth stage (cross-functional sections, annual creation, quarterly updates). Institutionalized at mature stage with dedicated business operations team.