What COOs Should Measure Between Quarterly Planning Cycles

Quarterly business reviews look backward at what happened. The alignment signal that predicts whether next quarter goes well or poorly is only visible between reviews, and most COOs have no instrument to read it.

What quarterly reviews actually tell you (and what they miss)

A QBR is a rearview mirror. It tells you what happened to revenue, to project completion, to headcount, to key accounts. It surfaces outcomes. It does not surface the conditions that produced those outcomes, or the conditions that are quietly forming right now for next quarter.

This is not a criticism of QBRs. Measuring outcomes is essential. The problem is that COOs who rely on QBR data alone are always operating on a lag. By the time misalignment shows in the numbers, it has already been compounding for weeks or months.

Research from MIT Sloan Management Review found that 97% of senior leaders said they understood their organization's strategy, but when asked to describe it accurately, roughly half could not. If that gap exists at the senior level, the gap at the team level is wider. And teams make hundreds of micro-decisions between reviews that either compound or contradict the strategy. None of those decisions appear in a QBR until they become outcomes you cannot change.

The strategy execution gap is not a planning problem. It is a measurement problem. COOs who have closed it are not running better QBRs. They are reading different data in the weeks between them.

The mid-cycle intelligence gap that most COOs are flying blind through

Between one QBR and the next, there is an intelligence gap. Teams are making decisions, interpreting priorities, adapting to ambiguity, and either holding or drifting from the plan's intent. Most of that is invisible to the COO.

The standard workaround is informal: walking the floor, one-on-ones with direct reports, asking managers what they're hearing. These are valuable practices. They are not measurement. They are anecdote collection under social pressure, because nobody tells the COO in a one-on-one that they do not understand the Q3 priorities.

Gallup research on manager engagement shows that when employees know their performance is being evaluated, their responses shift significantly toward what they perceive leadership wants to hear. The same dynamic applies to alignment conversations. The signal degrades at the moment it matters most.

For COOs responsible for strategy alignment across multiple teams, this gap is not a minor inconvenience. It is the difference between catching a drift early, when a conversation can correct it, and catching it at the QBR, when a quarter of execution has already gone in the wrong direction.

HBR research puts strategy execution failure rates at 67%. Most of that failure does not happen because the strategy was wrong. It happens in the space between planning cycles, where teams interpret, adapt, and quietly deviate without anyone registering the signal until it is too late to recover in-quarter.

Four signals worth measuring between planning cycles

Effective mid-cycle monitoring does not require adding overhead to a team that already has too many meetings. It requires knowing which signals to read and building a repeatable mechanism to read them. The four that matter most:

1. Strategic comprehension

Can teams describe the current priorities accurately, without prompting? Not whether they have heard the strategy. Whether they can restate it in their own words in a way that matches leadership's intent. The MIT Sloan 97/50 finding is worth keeping close here: self-reported understanding and actual comprehension diverge sharply. Comprehension is the foundation everything else rests on.

2. Directional confidence

Do teams believe the plan will work? Understanding the direction and believing in it are different conditions. A team that comprehends the strategy but doubts it will execute defensively: following the letter of the plan without the judgment and initiative that make it succeed. Directional confidence is a leading indicator for execution quality that no output metric captures until after the fact.

3. Decision alignment

When teams face decisions the plan does not explicitly address, are they making the call the strategy implies? This is the test of whether strategy has become an operating system or remained a document. Teams with high decision alignment handle ambiguity in ways that advance the plan. Teams with low decision alignment fill the gap with whatever is most immediately rewarding or least likely to cause conflict.

4. Escalation rate

Are teams absorbing appropriate uncertainty, or are they pushing everything upward for a decision? Rising escalation rates between QBRs are often misread as a capacity problem. They are usually an alignment problem. Teams that understand the strategy and believe in it can make more decisions autonomously. Teams that do not push those decisions up to the COO or chief of staff, creating a bandwidth bottleneck that looks like an operations problem but is rooted in comprehension.

These four signals are covered in more detail in how to measure team alignment to strategy, along with specific collection methods and cadence recommendations.

How to get honest signal from a team that knows leadership is paying attention

The challenge with any mid-cycle measurement is that teams perform for it. Ask people in a group setting how well they understand the strategy and you will get a room full of nodding. Ask them individually and the social pressure to give the right answer is high. This is not dishonesty. It is a rational response to being evaluated.

The signal degrades exactly when you most need it to be accurate: when something has gone wrong and you are trying to diagnose it. A team that has drifted from the strategy is not going to tell the COO that in a one-on-one. They are going to describe the work they are doing, which sounds aligned, because it is the work they decided to do.

Getting honest signal requires separating measurement from evaluation. When teams understand that the questions are about organizational comprehension, not individual performance review, they respond differently. Team-level anonymized data produces a very different signal than direct reporting chains, because the social cost of honest response drops to near zero.

This is the core design principle behind alignment measurement as distinct from OKR tracking. OKRs measure outputs attributed to individuals or teams. Alignment measurement measures the conditions that produce outputs, at a level of aggregation that makes honest response rational. These are complementary instruments, not substitutes.

What changes when you have mid-cycle alignment data before the next QBR

The operational difference is significant. When a COO walks into a QBR having read mid-cycle alignment data from the preceding weeks, the conversation changes from diagnosis to strategy. Instead of asking why the numbers look the way they do, they already know. They have been watching the conditions that produced the numbers develop in real time.

This changes what is fixable. Misalignment caught at week four or five of a quarter is recoverable. A clarifying conversation with a team lead, a re-articulation of a priority that got muddied, a decision framework that resolves a recurring ambiguity. These are low-cost, high-leverage interventions. The same misalignment caught at the QBR, after twelve weeks of compounding, often requires restructuring work that has already been done.

It also changes the QBR conversation itself. COOs with mid-cycle alignment data come to the review with hypotheses, not just questions. They know where the comprehension gaps were, which teams had low directional confidence, where escalation rates spiked. The QBR validates or challenges those hypotheses and feeds the next planning cycle with sharper signal.

The broader framing is in closing the strategy execution gap across business teams. The COO's job between planning cycles is not to wait for outcomes. It is to read the conditions that are forming them.

Frequently Asked Questions