When Should a Leadership Team Change the Plan Mid-Year?

A leadership team should not change its annual plan simply because execution becomes difficult.

It also should not keep following a plan that reality has proven wrong.

The challenge is knowing the difference.

That is one of the primary reasons organizations need an operating rhythm.

A plan represents the team's best understanding of where it intends to go based on the information available when the plan is created. But companies do not stop learning after the planning session. Customers respond. Markets change. KPIs produce new information. Teams discover capacity constraints. Product assumptions are tested. Competitors move. New opportunities appear. Execution itself teaches the organization what is and is not working.

A strong operating rhythm creates deliberate points where the team steps out of execution, compares the plan with reality, learns, and decides what should happen next.

Sometimes the plan should change.

Often the destination remains right and the organization simply needs a better way to get there.

That distinction is critical.

The purpose of operating rhythm is not to protect the plan from change. It is to create a disciplined system for learning whether the plan—or the way the organization is executing it—needs to change.

A Plan Is a Direction, Not a Prediction

Annual planning creates alignment by forcing a leadership team to make choices.

Where are we going?

What does success look like?

What matters most this year?

What capabilities need to exist?

What results should each functional area produce?

Those decisions give the organization something extremely valuable: a shared direction.

But planning does not give leadership perfect foresight.

A One-Year Plan is built using the organization's current understanding of its customers, market, product, people, capital, capacity, and opportunities.

The moment execution begins, the organization begins producing new information.

That is not a flaw in planning.

It is part of planning.

The mistake is treating the annual plan either as something that can never change or as something that should change every time reality becomes inconvenient.

A healthy organization does neither.

It builds the plan, executes against it, measures what is happening, learns, and then returns to the plan on a deliberate cadence.

This Is Why Operating Rhythm Matters

Without an operating rhythm, companies tend to review their plans at the wrong times.

Sometimes they barely review them at all.

The annual plan gets created at an offsite, shared with the company, and then gradually disappears beneath the urgency of everyday work. Teams spend the year executing tasks without regularly asking whether those activities are still producing the intended outcomes.

Other companies operate at the opposite extreme.

The plan is constantly being reconsidered.

A disappointing month causes the CEO to question the strategy.

A large prospect asks for a feature and Product priorities change.

A competitor makes an announcement and leadership changes direction.

An investor shares an idea and suddenly a new market becomes urgent.

The organization is constantly “adapting,” but never stays focused long enough to learn whether its existing plan could work.

Operating rhythm creates an alternative to both extremes.

Teams deliberately move between planning, execution, review, learning, and replanning.

Depending on the organization and team, the deeper review-and-planning rhythm may occur annually, semiannually, quarterly, or through some combination of those cadences.

In Peak OS, the core structure uses annual and quarterly planning sessions connected to the weekly execution rhythm.

The Annual Session establishes or refreshes longer-term direction and the One-Year Plan.

Quarterly Sessions bring the team back to that plan after another 90 days of reality.

The weekly operating rhythm provides visibility into execution between those deeper review points.

Each level of cadence serves a different purpose.

Weekly Execution Produces the Information

The weekly rhythm should not become a weekly strategy session.

Its primary purpose is to help the team execute and learn.

What is on course?

What is off course?

What are the KPIs telling us?

Which OKRs are progressing?

Where is something blocked?

Which issues need to be solved?

What decisions need to be made?

What actions happen next?

This creates organizational visibility.

Instead of leadership waiting three months to discover that an assumption was wrong, the team sees information accumulating throughout the quarter.

A KPI begins moving in the wrong direction.

An OKR repeatedly goes off course.

A dependency appears between Product and Engineering.

Sales receives consistent customer feedback.

Hiring takes longer than expected.

A cost assumption changes.

The weekly rhythm captures the signals.

It does not necessarily mean the One-Year Plan changes.

The information becomes part of what the team evaluates when it zooms back out.

The Deeper Cadence Is Where the Team Reviews the Plan Against Reality

A quarterly, semiannual, or annual planning session should therefore be more than a meeting to create another set of goals.

It is a learning checkpoint.

The team has two pictures in front of it.

The plan: what we believed should happen.

Reality: what actually happened and what we now understand.

The planning process brings those pictures together.

What did we accomplish?

What did we miss?

Why?

What did our KPIs teach us?

What did customers teach us?

What did the market teach us?

What did execution teach us about our capacity?

Which assumptions turned out to be correct?

Which assumptions were wrong?

Which opportunities emerged?

Which risks became more important?

What do the teams throughout the organization now understand that leadership did not understand when the original plan was created?

Then the team asks the most important question:

Given what we know now, is the plan still right?

Sometimes the answer is yes.

Sometimes part of the plan needs to change.

Occasionally, reality requires a larger reset.

That is organizational learning.

Often the Goal Is Right and the Way Needs to Change

This is where OKRs become especially valuable.

One of the easiest planning mistakes is to confuse the outcome the organization wants with the way it originally expected to achieve it.

Suppose the One-Year Plan includes an objective to build a repeatable enterprise growth engine.

That outcome may remain strategically important all year.

But the organization may learn that its original route is not working.

Perhaps direct outbound sales is producing weaker results than expected.

A channel strategy is showing significantly stronger economics.

Product learns that a specific capability is becoming essential for enterprise adoption.

Marketing discovers that the original ICP was too broad.

Customer Success identifies an onboarding constraint that is hurting expansion.

The company does not necessarily need a new annual goal.

It may need new quarterly OKRs that represent a better way of accomplishing the annual goal.

That distinction is fundamental.

The plan answers:

What outcomes are we committed to creating?

The quarterly planning process asks:

Based on what we know now, what should we accomplish over the next 90 days to move toward those outcomes?

OKRs therefore allow the organization to evolve the route without constantly abandoning the destination.

Review, Learn, Then Build the Next Set of OKRs

This is why quarterly planning should not begin with:

“What OKRs should we do next?”

It should begin with review.

Look at the One-Year Plan.

Look at the current reality.

Look at the KPIs.

Look at the previous quarter's OKRs.

Look at the misses.

Look at the wins.

Look at what changed.

Look at what the organization learned.

Only then should the team decide what the next quarter requires.

Sometimes a major annual outcome is still correct, but the organization needs to build a capability it did not know it needed.

That becomes an OKR.

Sometimes one function is preventing several others from progressing.

The next quarter may require resolving that constraint.

Sometimes the team needs to test a different approach.

Sometimes a capacity problem requires hiring, technology, process improvement, or organizational redesign.

The annual outcome can stay in place while the quarterly path changes substantially.

That is not abandoning the plan.

It is using the operating rhythm to execute the plan more intelligently.

When Should the Annual Plan Itself Change?

There are also times when a better OKR is not enough.

Reality can invalidate the plan itself.

A market may disappear.

Customer behavior may fundamentally change.

A regulatory shift may alter the business.

A product thesis may be disproven.

A major funding event may change the company's available capital.

An acquisition may create a materially different opportunity.

A critical partnership may appear or disappear.

Leadership may discover that an important outcome is no longer strategically valuable.

In those cases, continuing to pursue the original plan simply because it was approved months earlier is not execution discipline.

It is rigidity.

The operating rhythm should give leadership permission to ask a harder question:

If we were creating this plan today with everything we now know, would we still choose this outcome?

If the answer is no, the plan deserves reconsideration.

Do Not Change the Plan to Escape an Execution Problem

The reverse is equally important.

Sometimes the plan is not the problem.

Execution is.

The objective goes off course because ownership is unclear.

A critical dependency was not surfaced.

The company does not have enough capacity.

Leaders keep changing priorities.

The CEO is overriding decisions.

Teams are operating with different assumptions.

KPIs are not visible.

Cross-functional work is poorly coordinated.

Important issues are discussed repeatedly but not solved.

Changing the annual plan will not solve those problems.

It may temporarily make them less visible.

A difficult objective disappears.

The team gets a new initiative.

Everyone feels renewed energy.

But the same operating weaknesses move into the new plan.

Before changing direction, leadership should therefore ask:

If we executed the current plan exceptionally well, would we still believe the plan is wrong?

If the answer is no, the organization probably needs to improve execution rather than rewrite strategy.

Separate the Outcome From the Method

A useful way to make this decision is to separate three layers.

The Outcome

What are we trying to accomplish?

This may be an annual or longer-term strategic outcome.

The Approach

What do we currently believe is the best way to accomplish it?

This can evolve as the company learns.

The Current Work

What are we doing this quarter and this week to move the outcome forward?

This should evolve even more frequently.

Organizations create unnecessary instability when they treat changes at the third level as changes at the first.

An OKR changes and suddenly leadership thinks the strategy changed.

A tactic fails and the annual objective gets questioned.

A product experiment does not work and the destination is abandoned.

Strong operating rhythm helps leadership keep those layers distinct.

The company can remain deeply committed to an outcome while being highly flexible in how it reaches it.

The Operating Rhythm Is a Learning Loop

This is larger than planning.

It is how an organization becomes more intelligent over time.

The sequence looks something like:

Plan → Execute → Measure → Review → Learn → Adjust → Replan → Execute again

The value is in repetition.

A company that does this once per year learns slowly.

A company that changes everything every week never learns what actually works.

The operating rhythm creates intentional learning intervals.

Weekly meetings provide near-term execution intelligence.

Quarterly sessions create deeper review and course correction.

Annual planning revisits the larger direction.

Some organizations may create semiannual checkpoints between those levels depending on their complexity and needs.

The exact calendar matters less than the discipline behind it.

There must be predictable moments when the team asks:

What did reality teach us, and what should we do differently because of it?

That is why operating rhythm is not simply a meeting cadence.

It is the organization's learning cadence.

Consistency and Adaptability Are Not Opposites

This resolves what can otherwise look like a contradiction.

Teams need consistency.

They also need adaptability.

Peak Teams emphasizes the importance of consistency because habits develop through repetition. Teams that constantly abandon their planning, measurement, communication, and problem-solving disciplines never develop strong operating behaviors.

But consistency does not mean repeating the same decisions forever.

The system stays consistent.

The organization learns inside the system.

The cadence stays.

The review stays.

The measurement stays.

The expectation of clear ownership stays.

The practice of surfacing problems stays.

The habit of learning stays.

What the team decides to do can change as reality changes.

That is a much more durable model than either rigid planning or constant improvisation.

The operating system stays stable enough for the organization to adapt intelligently.

The Plan Should Be Reviewed Before the Team Creates the Next Quarter

This has a practical implication for leadership teams.

Quarterly planning should not exist in isolation from annual planning.

A company can create very good quarterly OKRs that gradually move it away from its annual plan if nobody reconnects the two.

Every deeper planning cycle should therefore begin by returning to the larger plan.

Where did we say we were going?

What did we say success would look like this year?

Where are we now?

What changed?

Which outcomes remain correct?

Which need to be modified?

Then:

What does this mean for the next quarter?

That connection keeps quarterly activity anchored to strategy.

It also prevents annual planning from becoming ceremonial.

The One-Year Plan remains a living reference point because the organization repeatedly returns to it.

Organizational Insight Should Inform the Review

The leadership team should not evaluate reality using only the information inside the executive room.

A meaningful review pulls intelligence from throughout the organization.

What are the teams closer to customers seeing?

What has Engineering learned?

What constraints are appearing inside Operations?

What is Sales hearing?

What patterns are appearing in Customer Success?

What is Finance seeing in the economics?

What are functional teams learning about their capacity?

What dependencies have appeared across teams?

What perspective does the board have on significant strategic assumptions?

As with the original planning process, useful information moves upward, downward, and across the Team-of-Teams.

The executive leadership team still integrates the information and owns the company-level plan.

But the organization's broader intelligence improves the quality of that decision.

This is particularly important when considering a significant mid-year change.

The executive team's first interpretation of the problem may not be the full reality.

When the Plan Changes, the Change Has to Travel Through the Organization

Changing the plan is not finished when the leadership team changes a slide.

The original plan has already propagated into the organization.

Functional plans reflect it.

Teams have created OKRs around it.

Budgets support it.

People have been hired for it.

Product roadmaps reflect it.

Customer commitments may depend on it.

Cross-functional dependencies have formed around it.

If the annual plan changes materially, the organization needs to realign.

What changed?

Why?

What did we learn?

What remains the same?

Which outcomes changed?

Which OKRs change?

Which KPIs matter now?

What work stops?

What resources move?

Which dependencies need to be renegotiated?

Does ownership change?

Which teams are affected?

This is why changing the plan should be deliberate.

The cost is not simply the executive decision.

The cost is the organizational recoordination that follows it.

Sometimes the Right Decision Is to Stay the Course

Operating rhythm does not exist to create change.

It exists to create better decisions.

A team can complete a thorough quarterly review and conclude:

The annual outcomes remain correct.

The assumptions still broadly hold.

The business is learning.

Some things are off course.

The path is difficult.

But we believe the destination is right.

In that case, the planning session may produce new or adjusted OKRs while the One-Year Plan stays largely intact.

That is a valuable outcome.

The review created confidence that leadership is not continuing blindly.

The organization examined reality and deliberately recommitted.

There is a large difference between:

“We're sticking with the plan because that's what we wrote in January.”

and:

“We reviewed the plan against everything we have learned, and we still believe these are the right outcomes.”

The second is execution discipline.

Sometimes the Route Changes

The next possibility is more common.

The outcome remains correct.

The path needs to improve.

The organization learned something.

A capability needs to be built.

A dependency needs to be solved.

A different approach appears more effective.

Resources need to move.

This is where quarterly OKRs become a powerful execution mechanism.

The One-Year Plan continues providing direction while each 90-day cycle reflects the organization's newest understanding of how to reach it.

The company is adapting without becoming directionless.

And Sometimes the Plan Really Does Need to Change

Finally, there are moments when reality has moved enough that the destination itself deserves reconsideration.

That should not be treated as organizational failure.

The failure would be refusing to learn.

A plan based on an assumption that is no longer true should not become sacred simply because leadership once committed to it.

The discipline is in being able to explain the change.

What did we believe?

What happened?

What did we learn?

Why is the original outcome no longer the best use of our capacity?

What is the new outcome?

What will stop?

How will the organization realign?

How will we measure whether the new direction is working?

That turns a pivot into an organizational decision instead of an executive reaction.

The Better Question Is Not Whether Plans Should Change

The debate is often framed incorrectly.

Should companies stick to their plans or remain flexible?

They need both.

The real question is:

Does the organization have a recurring system for comparing its plan with reality and making intelligent changes based on what it learns?

That is what operating rhythm provides.

Annual planning establishes direction.

Quarterly or other periodic reviews bring leadership back to the plan.

Weekly execution creates visibility.

KPIs help the organization understand what is happening.

OKRs give teams new ways to accomplish strategic outcomes.

Triage helps solve the problems standing in the way.

The Team-of-Teams contributes intelligence from throughout the organization.

Then leadership makes the next set of decisions.

The organization does not simply plan once.

It plans, executes, learns, and plans again.

That is the difference between having an annual plan and having an operating system.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?