---
title: "Why Did We Miss the Plan? A Four-Part Diagnostic for CEOs and Boards"
url: "https://www.collective-genius.com/insights/why-did-we-miss-the-plan-a-four-part-diagnostic-for-ceos-and-boards-msp0f2b4"
author: "Jeff James Martin"
organization: "Collective Genius"
date_published: "2026-08-22T07:00:37.403Z"
date_modified: "2026-08-22T07:00:37.403Z"
reading_time_minutes: 13
cluster: "Organizational Execution"
tags: ["Organizational Execution", "Strategic Planning", "Organizational Intelligence", "Organizational Visibility", "Decision Making", "Execution Discipline", "Peak OS"]
description: "Learn how CEOs and boards can diagnose a missed plan by separating strategy problems, market changes, organizational capacity constraints, and execution failures."
---

# Why Did We Miss the Plan? A Four-Part Diagnostic for CEOs and Boards

A missed plan is an outcome, not a diagnosis. CEOs and boards should evaluate four possible causes: strategy, market conditions, organizational capacity, and execution. Each requires a different response. Misdiagnosing the cause can lead leadership teams to spend the next quarter solving the wrong problem.

When a company misses its plan, the first instinct is usually to focus on execution.

Why didn't the team deliver?

Who missed the number?

Which commitment slipped?

What needs to change next quarter?

Those are reasonable questions. But they begin one step too late.

**A missed plan is an outcome. It is not a diagnosis.**

In my work with hundreds of CEOs and leadership teams, I have seen very different organizational problems produce almost identical-looking results.

Revenue comes in below plan. A product launch slips. Hiring falls behind. A strategic initiative does not deliver. The company misses the quarter.

From the boardroom, all of those situations can initially look like execution failure.

But they are not necessarily the same problem.

Before deciding what to fix, CEOs, leadership teams, and boards should determine which of four conditions created the miss:

**Strategy → Market → Capacity → Execution**

Was the strategy itself wrong?

Did something important change in the market?

Did the organization commit to more than it had the capacity to deliver?

Or did the company have a viable strategy, a real market opportunity, and enough capability—but fail to execute together?

The distinction matters because each diagnosis requires a different response.

If leaders misdiagnose the miss, they can spend the next quarter solving the wrong problem.

## Why Companies Move Too Quickly From Miss to Action

Missing the plan creates pressure.

The CEO has to explain the result to the board. Investors want to know what happened. Functional leaders begin defending their numbers. The leadership team wants to demonstrate that it has a plan to fix the problem.

Everyone wants action.

That urgency can cause teams to move directly from:

**Result → Explanation → New Action**

without spending enough time understanding the root cause.

One executive believes the targets were unrealistic.

Another thinks Sales underperformed.

Product argues that the market changed.

Finance believes the company hired too slowly.

The CEO thinks accountability is the issue.

The board begins wondering whether the management team can execute.

Each perspective may contain part of the truth.

But if leadership simply chooses the explanation that feels most obvious, the resulting corrective action can create even more problems.

A company with a strategy problem does not need more execution pressure against the same strategy.

A company facing a market change should not necessarily replace leaders because the original forecast missed.

An organization with a capacity problem cannot solve every issue by demanding more accountability from people who were already overcommitted.

And an organization with a true execution problem will not fix it simply by lowering the target.

The diagnosis has to come first.

## 1. Was It a Strategy Problem?

A strategy problem means the organization was executing against choices or assumptions that were unlikely to produce the desired outcome.

The team may have worked hard.

People may have delivered their commitments.

Projects may have finished on time.

The problem is that the work was pointed toward the wrong destination or based on assumptions that proved incorrect.

This is one of the most important distinctions a leadership team can make because **a company can execute a bad strategy extremely well**.

Imagine a company whose growth plan depends on expanding into a new customer segment.

Marketing builds the campaigns.

Sales develops the pipeline.

Product completes features the new segment requested.

Customer Success creates a new onboarding process.

Everyone executes.

But the segment does not convert at the expected rate. Sales cycles are far longer than anticipated. Acquisition costs make the economics unattractive.

The problem may not be that the team failed to execute.

The underlying strategic bet may have been wrong.

The most useful question is:

**If we executed the same strategy significantly better next quarter, would we reasonably expect a different outcome?**

If the answer is no, leadership should resist the temptation to solve the problem with more pressure, more meetings, or more accountability.

The strategy itself needs to be reconsidered.

CEOs and boards should examine whether the assumptions behind the plan were valid, whether the chosen market or product direction still makes sense, and whether the initiatives completed actually created the effects leadership expected.

Execution cannot compensate indefinitely for the wrong strategic choice.

## 2. Did the Market Change?

The second possibility is different.

The strategy may have been reasonable when leadership created the plan.

Then the external environment changed.

Customer buying behavior shifts.

A major competitor changes pricing.

A new technology changes expectations.

Sales cycles lengthen.

Capital becomes harder to access.

A regulatory change affects demand.

A significant customer pauses spending.

The strategy was not necessarily poor.

**The environment moved.**

Growth companies face this constantly because they often operate in markets where there is limited historical information and conditions change quickly.

The important question is not simply whether something changed.

Markets always change.

The better questions are:

**When did we first have evidence that conditions were changing?**

**How quickly did that information reach the leadership team?**

**How quickly did we adapt once we understood what was happening?**

This is where organizational intelligence and operating rhythm become important.

A market change can become an execution problem if the organization sees the signal but cannot respond.

Customer behavior may begin changing in January.

Sales sees it.

Customer Success hears something similar.

Marketing notices conversion changing.

But those signals remain inside the individual functions.

The leadership team does not connect them until the quarter is almost over.

At that point, leadership may say:

“The market surprised us.”

But the deeper issue might be that the organization did not have a way to turn distributed information into shared understanding quickly enough.

Strong organizations do not predict every external change.

They become better at **seeing, interpreting, and responding to change while there is still time to influence the outcome**.

## 3. Did We Have the Organizational Capacity to Deliver the Plan?

The third diagnosis is one leadership teams often overlook.

The strategy may be sound.

The market opportunity may still exist.

The team may even be executing reasonably well.

But the organization may simply have committed to more than it had the capacity to accomplish.

Capacity is not the same thing as headcount.

Organizational capacity includes people, skills, leadership bandwidth, capital, technology, operating infrastructure, time, and the number of simultaneous priorities the company can realistically absorb.

This is where ambitious growth plans quietly become impossible plans.

Imagine a leadership team committing to a major product launch, a new market expansion, a CRM implementation, a Series B raise, several executive hires, and aggressive revenue growth in the same period.

Every priority may make strategic sense.

Together, they may exceed the organization's real capacity.

The problem becomes even harder when work crosses functions.

Sales assumes Product will deliver a capability in March.

Product depends on Engineering.

Engineering is simultaneously addressing technical debt.

Finance has constrained hiring.

People is trying to recruit critical roles for three different departments.

Marketing is already preparing the launch.

Every team can be behaving responsibly while the collective plan requires the organization to do more than the system can support.

I have seen this repeatedly.

Leadership teams often plan each initiative independently, then discover during execution that many of the initiatives require the same people, the same capital, the same executive attention, or the same cross-functional dependencies.

The company did not necessarily fail to execute.

It may have **overcommitted relative to organizational capacity**.

This is why planning requires more than identifying what the company wants to accomplish.

Leadership also has to ask:

Do we have the people required?

Do we have the skills?

Do we have the leadership bandwidth?

What initiatives compete for the same resources?

What dependencies have to occur in sequence?

What capabilities must exist before another priority can succeed?

If the plan exceeds capacity, the answer may be fewer priorities, different sequencing, additional resources, or investment in new organizational capabilities.

Demanding more effort from the existing system is not always the answer.

## 4. Was It an Execution Problem?

Only after evaluating strategy, market, and capacity should leadership move deeply into execution.

An organizational execution problem exists when the company has a reasonable strategy, the opportunity still exists, and sufficient capacity is available—but teams fail to translate the plan into coordinated action.

This is the territory I have encountered most often in working with growth-company leadership teams.

The symptoms usually appear before the final miss.

Different executives have different interpretations of the plan.

Priorities change without the organization realigning.

An important cross-functional outcome has no clear owner.

Teams use different definitions of the same metric.

OKRs exist but are not reviewed consistently.

KPIs reveal a problem but do not lead to action.

Dependencies remain invisible until a commitment slips.

Leadership meetings repeatedly discuss the same issues without solving them.

The CEO becomes involved in decisions that should be owned elsewhere.

People are working hard.

But the organization is not moving together.

In *Peak Teams*, I describe a leadership team that initially looked exactly like this.

The CEO and CFO discovered while preparing for a board meeting that they were working from different year-end revenue goals—and neither matched the number previously shared with the board.

Engineering was not on track for a product launch Marketing was already preparing.

Another leader was building an international go-to-market strategy even though the CEO and Head of Sales did not intend to expand internationally for several years.

There was no shortage of effort.

Each person believed they were moving the business forward.

But the company was effectively moving in several different directions at once.

That is an execution problem.

## Execution Often Breaks Between Teams, Not Inside Them

One of the reasons execution problems can be difficult for CEOs and boards to identify is that the individual functions may look healthy.

Sales has a plan.

Marketing has campaigns.

Product has a roadmap.

Engineering has a development process.

Finance has a forecast.

Customer Success has retention initiatives.

Viewed independently, every function may appear competent.

But most important company outcomes do not belong inside one function.

Revenue is not exclusively a Sales outcome.

A successful product launch is not exclusively Product's responsibility.

Customer retention is not exclusively owned by Customer Success.

Strategic initiatives increasingly require several functions to move together.

That means organizational execution often breaks at the **connections between teams**.

Ownership is unclear.

A dependency is invisible.

Two functions are operating from different assumptions.

A decision is made but does not reach everyone affected.

One team's priority conflicts with another team's capacity.

Timing is not synchronized.

The CEO becomes the person who discovers and reconciles those differences.

This is why replacing one underperforming function does not always solve repeated execution misses.

Sometimes the organization does not have a functional-performance problem.

It has a **coordination problem across otherwise capable functions**.

## What Should Leadership Do Immediately After a Miss?

The first response to a missed quarter should not be to immediately create the next quarter's plan.

Use the miss to learn.

Start by reconstructing reality.

What did we originally believe?

What actually happened?

When did results first begin moving off course?

What did the KPIs tell us?

Which OKRs or initiatives slipped?

Which assumptions proved incorrect?

Where did dependencies fail?

What resource constraints appeared?

What information did we know during the quarter that we did not act on quickly enough?

Then work through the four diagnoses:

**Strategy:** Was the direction or strategic assumption wrong?

**Market:** Did something material change outside the organization?

**Capacity:** Did the plan require more organizational capability than was realistically available?

**Execution:** Did the organization fail to coordinate around an otherwise viable plan?

More than one can be true.

A market change may reveal a weakness in strategy.

A capacity constraint may be made worse by poor prioritization.

An execution problem may prevent the company from responding quickly enough to external changes.

The point of the framework is not to force every miss into one category.

The point is to prevent leaders from defaulting to the easiest explanation.

## Why Better Metrics Improve the Diagnosis

Companies cannot diagnose misses well if they do not understand the business while it is operating.

This is one of the reasons I put so much emphasis on measurement in Peak OS.

I often tell teams that **we measure the business to learn the business**.

At first, a KPI may be imperfect.

A forecast may be wrong.

The target may turn out to be unrealistic.

That is not necessarily a reason to abandon measurement.

It is information.

Over repeated cycles, the organization learns which metrics actually predict outcomes, which assumptions are reliable, what levels of capacity are realistic, and where execution begins to drift.

The team becomes better at understanding the mechanics of the business.

In *Peak Teams*, one CEO described this shift after the team began working more systematically with KPIs. Each review improved the company's ability to understand and forecast what was happening.

That is organizational learning.

Measurement should not exist simply to tell leadership whether someone hit a number.

It should help the company understand **why the number moved**.

## Why OKRs and KPIs Tell Different Parts of the Story

This distinction also helps when diagnosing a miss.

KPIs help leadership understand how the business is performing.

OKRs help the organization focus on the important outcomes and capabilities it needs to build.

Those are different forms of information.

Imagine revenue is below plan.

That KPI tells leadership something important about the business.

The diagnostic question becomes why.

Perhaps the company needs to create a new enterprise-sales capability. That might become an OKR.

Or perhaps the problem is not a capability at all. Maybe demand in the target segment has changed.

Or the company has enough pipeline but implementation capacity is preventing new customers from going live.

Looking at both ongoing performance and strategic execution helps leaders avoid simplistic diagnoses.

Metrics, goals, and operating conversations should work together to create a more complete picture of reality.

## Boards Need the Same Diagnostic Discipline

This framework is particularly useful for boards.

Boards see the output of organizational execution, but they are not inside the company every day.

A miss can therefore create understandable concern.

Did management set unrealistic goals?

Is the strategy failing?

Is the CEO losing control of execution?

Does the company need stronger leaders?

Should the board push for more reporting?

Those questions matter.

But the board should resist treating every missed plan as evidence of the same underlying management problem.

A board that assumes every miss is an accountability problem may encourage management to create more pressure when the strategy needs to change.

A board that accepts “the market changed” too easily can overlook a company that saw warning signals and failed to act.

A board that sees a capacity constraint as a talent problem may push for leadership changes when the organization simply committed to too much at once.

Good execution oversight requires enough visibility to distinguish between:

**a bad strategic bet, a changed environment, insufficient capacity, and an execution-system failure.**

The board does not need to run the company to ask those questions.

But it does need to understand what kind of problem management is solving.

## Where a Business Operating System Helps

A business operating system does not remove strategy risk.

It cannot control the market.

It does not create unlimited capacity.

And it cannot guarantee that a company will always hit its plan.

What a strong operating system can do is help leadership see problems earlier and learn from them faster.

Long-term direction and annual planning make strategic assumptions explicit.

KPIs create ongoing visibility into business performance.

OKRs connect important organizational work to measurable outcomes.

Clear Roles and Responsibilities strengthen ownership.

A regular operating rhythm keeps the plan connected to current reality.

Triage creates a place for off-course issues and important decisions to be addressed.

Quarterly and annual reviews give the organization structured opportunities to reflect, learn, and adjust.

In Peak OS, those practices are designed to reinforce one another.

The objective is not simply to make the organization execute harder.

The objective is to help the organization **see reality, understand what it means, and respond while there is still time to change the result**.

Sometimes that response will improve execution.

Sometimes it should change the strategy.

Sometimes leadership should reduce the plan.

Sometimes the company needs more capacity.

Knowing the difference is the real advantage.

## A Miss Should Make the Organization Smarter

Missing a plan is painful.

Repeated misses can damage confidence with the board, investors, employees, and customers.

But a miss can also become one of the organization's most valuable learning opportunities.

The strongest leadership teams are not necessarily the teams that never miss.

They are the teams that get better at understanding **why** they miss.

They know when a strategic assumption was wrong.

They recognize meaningful market changes without using the market as an excuse.

They understand the limits of organizational capacity.

They identify execution breakdowns before automatically blaming individual functions.

And they use what they learn to create a better next plan.

The wrong question after a miss is:

**“Who failed?”**

A better question is:

**“What did this result teach us about how the business and organization actually work?”**

That shifts the conversation from blame to diagnosis.

From activity to understanding.

From explanation to learning.

And that is what gives the next plan a much better chance of becoming reality.


## Related Insights

[What Is Peak OS?](https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx)

[What Is Organizational Execution?](https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p)

[What Is Organizational Intelligence?](https://www.collective-genius.com/insights/what-is-organizational-intelligence-mq7jys1i)

[What Is a Business Operating System?](https://www.collective-genius.com/insights/what-is-a-business-operating-system-mq4qmt39)

[What Is Operating Rhythm?](https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur)

## Key Takeaways
- A missed plan should not automatically be treated as an organizational execution failure.
- Leaders should diagnose four possible causes: strategy, market, organizational capacity, and execution.
- A strategy problem exists when better execution of the same strategic choices would still be unlikely to create the desired outcome.
- A market problem occurs when important external conditions change and the organization must recognize and respond to new information.
- A capacity problem means the plan requires more people, skills, time, capital, infrastructure, leadership bandwidth, or coordination capability than the organization currently has.
- An execution problem occurs when a viable strategy and sufficient organizational capacity fail to translate into coordinated action across teams.
- KPIs, OKRs, ownership, visibility, operating rhythm, and structured problem-solving help organizations diagnose misses earlier.
- Strong leadership teams use missed plans as organizational learning rather than simply as a reason to assign blame.

## Frequently Asked Questions

### Why do companies miss their quarterly plans?

Companies can miss plans for fundamentally different reasons. The strategy may be wrong, market conditions may change, the organization may lack the capacity required by the plan, or teams may fail to execute a viable plan together. The result alone does not tell leadership which problem occurred.

### How can a CEO tell whether the strategy or execution is the problem?

Ask whether significantly better execution of the same strategy would reasonably produce the desired outcome. If not, the strategic assumptions or choices may need to change. If the strategy remains viable but teams struggle with priorities, ownership, dependencies, decisions, or follow-through, the problem is more likely organizational execution.

### What is an organizational capacity problem?

An organizational capacity problem occurs when the company does not have enough people, skills, leadership bandwidth, capital, technology, infrastructure, time, or coordination capability to deliver everything in the plan. A company can have strong people and good execution while still committing to more than the organization can realistically absorb.

### How do you know whether the market caused a missed plan?

Identify what external assumptions changed, when the company first had evidence of the change, and how quickly leadership responded. Market changes are real, but leaders should also evaluate whether the organization had warning signals earlier and whether slow internal response contributed to the miss.

### What are signs of an organizational execution problem?

Common signs include unclear ownership, conflicting priorities across functions, hidden dependencies, inconsistent metrics, objectives that are not regularly reviewed, recurring unresolved issues, slow decisions, weak cross-functional visibility, and frequent CEO intervention to reconnect work across teams.

### What should a leadership team do immediately after missing a quarter?

Reconstruct what happened before creating the next plan. Review the original assumptions, KPIs, OKRs or major initiatives, resource constraints, dependencies, and the point at which results began moving off course. Then diagnose how much of the miss came from strategy, market, capacity, or execution.

### How should a board respond when a company misses its plan?

The board should first understand the type of problem management is addressing. It should ask questions that distinguish strategic assumptions, external market changes, organizational capacity, and execution capability rather than immediately prescribing more reporting, leadership changes, or increased accountability.

### Can a business operating system prevent companies from missing their plans?

No operating system can guarantee a company will hit every plan. A strong system can make strategic assumptions, performance signals, ownership, capacity constraints, dependencies, and off-course execution more visible. That gives leadership a better chance to diagnose problems and adjust before the final result is determined.

Source: https://www.collective-genius.com/insights/why-did-we-miss-the-plan-a-four-part-diagnostic-for-ceos-and-boards-msp0f2b4