Every October and November, senior leadership teams across mid-market Canada go through the same ritual. The CFO sends a template. Division heads fill in their numbers. A series of meetings are held where every department defends its budget request. The CEO synthesizes the result into something that can be presented to the board. A strategy document is written — sometimes before the budget, sometimes after, sometimes never — and by January 15th, everyone is back to running the business the way they were running it in August. The annual planning process, as most organizations practice it, is a tremendous investment of time that produces a plan nobody follows. This post is about why that happens, and what the organizations that actually execute against their plans do differently.

Why the standard process fails: a structural diagnosis

The broken annual planning process shares three structural characteristics that appear consistently across mid-market organizations, regardless of industry.

First, it starts with the budget. When finance drives the calendar — which is the default in most organizations — the planning sequence is: set a revenue target, establish a cost envelope, allocate that envelope across departments, and then ask each department to articulate what they will do with their allocation. This sequence feels like planning. It is not. It is resource rationing with a strategy narrative attached afterward. The result is that every department optimizes for its share of a fixed pool, which is a fundamentally different objective than allocating resources toward a defined strategic outcome.

Second, the strategy process runs on a parallel track. In organizations we work with, it is common to find a strategy document and a financial plan that were developed by different teams, on different timelines, using different assumptions. The strategy document describes where the organization wants to go. The financial plan describes what the organization can afford. These two things are rarely reconciled in a structured way. The consequence is predictable: when resource constraints create trade-offs, the financial plan wins by default because it is the document that controls actual spending authority.

Third, there is no governance mechanism to keep the plan current. The annual plan is built on assumptions about the market, the competitive environment, customer behavior, and organizational capacity. Many of those assumptions will be wrong within 90 days of the plan being finalized. Organizations that do not have a structured mechanism for revisiting and adjusting those assumptions do not adapt — they drift. By mid-year, the annual plan has become a historical artifact that nobody references because referencing it would require acknowledging how far the business has moved from its stated priorities.

The sequence that high-growth companies use

Organizations that consistently execute against their plans — and in our experience, this group skews heavily toward companies in the $50M to $500M revenue range that have made a deliberate investment in their operating model — follow a different sequence. The difference is not complexity. It is order of operations.

The sequence is: Strategic clarity → OKR cascade → Resource allocation → Rolling forecast integration → Governance cadence.

Each step is load-bearing. Skipping or compressing any one of them degrades the entire system.

Step one: strategic clarity before any numbers

The planning cycle begins with a structured offsite or working session — typically in August or September for a January fiscal year start — where the senior leadership team answers a small number of high-stakes questions: What are the two or three things this organization must be better at in 18 months than it is today? What markets, customer segments, or capabilities are we explicitly choosing not to pursue in the planning period? What would have to be true for us to consider this year a success?

These are not easy questions, and the answers are not obvious. Organizations that shortcut this step — that treat it as a box to check before getting to the real work of building the financial model — produce strategy statements that are so broadly worded that they are consistent with almost any resource allocation decision. A strategy that says “we will grow our core business while selectively investing in adjacent opportunities” is not a strategy. It is a permission slip for everyone to do what they were already planning to do.

What distinguishes high-growth companies at this stage is their willingness to make explicit trade-offs. If investing in a new customer segment means under-resourcing the existing sales team for 18 months, that trade-off needs to be named and accepted before any budget is built. Organizations that cannot make explicit trade-offs at the strategic level will have those trade-offs made implicitly at the budget level, typically in favor of whoever has the most political capital.

Step two: the OKR cascade as a translation mechanism

Once strategic priorities are clear, they need to be translated into organizational objectives before they can be resourced. This is where OKRs (Objectives and Key Results) serve their most important function — not as a performance management tool, but as a translation mechanism between strategic intent and operational planning.

The cascade works as follows. The leadership team defines three to five company-level objectives for the planning period, each with two to four measurable key results. Division and department leaders then define their own objectives and key results that demonstrate their contribution to the company-level outcomes. This cascade makes the connection between individual team priorities and organizational strategy explicit and testable.

Critically, the OKR cascade must be completed before the budget is built. Each team’s objectives define what they need to accomplish. The budget question is then: what resources are required to accomplish those objectives? This is a fundamentally different conversation than “how much did you spend last year, and what percentage increase do you need?” The former grounds resource allocation in strategic outcomes. The latter grounds it in historical patterns that may or may not be relevant to the current strategy.

Step three: resource allocation tied to strategic outcomes

With OKRs established, the budget process becomes a resource allocation exercise against defined outcomes rather than a political negotiation over cost envelopes. Each team brings forward a resource request that is explicitly tied to their key results. Finance evaluates requests against organizational constraints and strategic priority — initiatives that directly support high-priority company-level OKRs receive preferential allocation.

This approach does not eliminate difficult trade-offs, but it changes the basis on which those trade-offs are made. Instead of departments competing for budget based on their internal lobbying effectiveness, resource allocation decisions are visible and traceable to strategic priorities. When a department is under-resourced, it is possible to have an honest conversation about which key results will be deprioritized as a consequence — rather than pretending that the same outcomes can be achieved with less.

Rolling forecasts: replacing the static budget as the operating mechanism

The static annual budget is the wrong tool for a dynamic operating environment. Built on point-in-time assumptions, it becomes increasingly unreliable as the year progresses. Organizations that cling to the annual budget as their primary financial operating mechanism face a recurring problem: by Q3, the budget has diverged sufficiently from current reality that it is no longer useful for decision-making, but it is also still the document that formally governs spending authority. The result is a shadow financial process — informal resource reallocation that happens outside the official budget — combined with continued reporting against a plan that nobody believes.

The alternative is a rolling forecast — typically a 12- to 18-month forward view that is updated quarterly. The rolling forecast does not replace the annual plan; it operationalizes it. The annual plan establishes the strategic direction and the resource envelope. The rolling forecast provides the current best estimate of where the business will land given actual performance to date and updated assumptions about the remainder of the period.

In mid-market organizations, the practical transition to rolling forecasts typically involves three changes to the finance operating model:

• Quarterly reforecasting cycles: Finance runs a structured reforecast at the end of each quarter that incorporates actual results, updated pipeline and demand assumptions, and any changes to the cost structure. This replaces the informal mid-year budget revision process that most organizations already run informally.
• Driver-based models: Rolling forecasts are only tractable if the financial model is built on business drivers — unit economics, headcount productivity, customer acquisition rates — rather than line-item historical actuals. Building driver-based models is a meaningful investment, but it is what makes the forecast update process scalable.
• Separation of target and forecast: One of the most common mistakes in rolling forecast implementations is conflating the financial target (what we are trying to achieve) with the forecast (our best estimate of what we will achieve). These are different things. Conflating them creates pressure to produce optimistic forecasts rather than accurate ones, which defeats the purpose of the tool.

The governance model: what keeps the plan alive past February

In our experience, the most common reason annual plans fail is not that they are poorly constructed. It is that there is no structured mechanism for holding the organization accountable to them between January and December. Without that mechanism, the plan is effectively optional. And when competing pressures emerge — a large customer opportunity that falls outside the strategic focus, an operational crisis that consumes leadership attention, a market shift that makes certain assumptions obsolete — the plan loses to immediate priorities every time.

The governance model that keeps a plan alive has three components.

Quarterly Business Reviews (QBRs) tied to the plan. A QBR is not a financial reporting meeting. It is a structured session where the leadership team reviews progress against OKRs, updates the rolling forecast, and makes explicit resource reallocation decisions based on current performance. The agenda is structured around strategic priorities, not departmental updates. Each division leader presents their key result progress and identifies the top risk to achieving their objectives in the next quarter. The output of the QBR is a set of decisions, not a set of presentations.

A single owner for the planning process. In most mid-market organizations, nobody owns the annual plan after it is published. Finance owns the budget. The CEO owns the strategy. Department heads own their OKRs. Nobody owns the connection between these things. High-growth organizations assign a Chief of Staff, a VP of Strategy, or an empowered VP of Operations to own the integrity of the planning process — to ensure that QBRs happen, that OKRs are current, and that resource allocation decisions are being made in reference to the strategic plan rather than in spite of it.

A visible scoreboard. Organizational priorities that are not measured are not real. The annual plan needs to be translated into a monthly or bi-weekly leadership dashboard that shows progress against company-level OKRs, current rolling forecast versus target, and the top five risks to plan execution. This dashboard does not need to be sophisticated — in fact, simpler is better — but it needs to be reviewed consistently and used to drive decisions rather than filed after each review cycle.

Where to start: a practical sequence for organizations redesigning their planning process

For organizations that recognize the broken pattern and want to move toward the approach described above, the sequence matters. Attempting to implement everything simultaneously — OKR cascades, rolling forecasts, QBR governance — creates change fatigue and increases the risk that none of the changes take hold.

1. Start with the sequence, not the tools. Before changing any tools or templates, change the order in which planning happens. Run a strategy clarity session before the budget process opens. Make the output of that session the explicit input to the budget — even if the budget process itself is unchanged. This single adjustment has a disproportionate impact on the quality of resource allocation decisions.
2. Establish the QBR cadence in year one. Before investing in OKRs or rolling forecasts, create a structured quarterly business review process. The QBR is the governance mechanism that holds everything else together. Organizations that implement OKRs without a QBR cadence typically see OKR adoption collapse by Q2.
3. Pilot rolling forecasts in a single business unit. Rolling forecast implementations require meaningful changes to the financial model and the finance team’s operating calendar. Piloting in one division before rolling out organization-wide allows the organization to work out the mechanics without disrupting the entire planning process.
4. Connect OKRs to the budget in year two. Once the strategy-first sequence and the QBR cadence are established, the OKR cascade can be connected to the resource allocation process in a way that is meaningful rather than decorative.

Frequently asked questions

How long should the annual planning process take?

For a mid-market organization with a January fiscal year start, the planning process should run from approximately early September through late November — roughly 12 weeks. The strategy clarity phase should take two to three weeks, including a facilitated offsite and a follow-up session to finalize priorities. The OKR cascade should take three to four weeks, with one round of leadership review and one reconciliation pass. The budget build should take four to six weeks. Organizations that try to compress the process into six weeks almost always compress the strategy and OKR phases to protect the budget timeline, which reproduces the budget-first failure mode.

What is the right number of company-level OKRs for a mid-market organization?

Three to five company-level objectives is the right range for most organizations in the 100-to-2000 employee range. Fewer than three often signals that the organization has not disaggregated its strategic priorities meaningfully. More than five almost always signals that the leadership team has not made the trade-offs required to define a real strategy — it has instead listed everything that matters, which is a different thing. Each objective should have no more than four key results. A common mistake is writing key results that are actually activities (“launch new product line”) rather than outcomes (“achieve $2M ARR from new product line within 12 months”).

How do rolling forecasts interact with the board-approved annual budget?

This is a practical governance question that most organizations navigate by maintaining both documents with clearly defined purposes. The annual budget, once board-approved, remains the formal spending authority document. The rolling forecast is an operational planning tool that reflects the organization’s current best estimate of where it will land. When the rolling forecast diverges materially from the board-approved budget — typically by more than 5 to 10 percent on key metrics — it triggers a structured board conversation about whether the budget needs to be formally revised or whether the organization should make operational changes to close the gap. The two documents serve different masters: the budget serves the board; the forecast serves the management team.

Our executive team has very little patience for OKR frameworks. How do we get buy-in?

Executive resistance to OKRs is almost always resistance to how OKRs have been implemented in the past — or observed at other organizations — rather than resistance to the underlying principle of connecting priorities to measurable outcomes. In our experience, the most effective approach is to introduce the mechanics without the terminology. Run a session where the leadership team defines the top three organizational priorities for the year and agrees on how they will know, 12 months from now, whether each priority was achieved. That is an OKR. Once the leadership team has experienced the clarity that comes from that exercise, the formal OKR structure can be introduced as a way to extend the same logic through the rest of the organization.

How do we prevent the QBR from becoming just another status update meeting?

The most reliable way to prevent QBR decay is to make the meeting explicitly decision-focused rather than presentation-focused. Before each QBR, the meeting owner collects a small number of pending decisions that require leadership alignment — typically two to four — and structures the meeting agenda around those decisions. Progress updates against OKRs are circulated in advance as pre-read material, not presented in the meeting. The meeting itself is reserved for discussion, debate, and decisions. Organizations that allow QBRs to become presentation sessions typically see attendance drop within two quarters, which signals that the meeting is not seen as worth the time investment of senior leaders.

Annual Planning Process: How Growing Companies Do It Differently From Stalling Ones

Most senior operations directors and CFOs at mid-market companies invest significant time in the annual planning process but end up with a plan that loses relevance before the fiscal year is half complete. This post lays out the structural reasons that happens and the specific sequence — strategy-first, OKR cascade, rolling forecast, governance cadence — that organizations consistently executing against their plans use instead.