What Your Quarterly Review Can't See

The compression problem

A quarterly review is a compression algorithm. It takes three months of organisational reality, thousands of decisions, hundreds of metrics, dozens of evolving situations, and compresses it into a format that fits a 60-minute meeting with 15 slides.

Compression always loses information. The question is what gets lost.

We applied signal archaeology to this question across two organisations: a mid-size bank and a technology services company. We selected 16 strategic signals, eight from each organisation, and traced them from their operational origin to their final representation in executive quarterly reporting. At each organisational boundary, we measured what was preserved, what was transformed, and what disappeared.

The results: on average, 67% of signal content was lost, transformed, or delayed by more than 90 days by the time it reached the quarterly review. The quarterly review isn’t just an imperfect window into reality. It’s structurally incapable of showing leaders the things that matter most.

The 16 signals

We deliberately chose signals that mattered strategically, not trivial operational noise. These were signals that, if accurately understood, would have changed a decision at the executive level:

At the bank: a shift in customer acquisition channel mix, an emerging pattern in loan default risk in a new segment, a competitor’s pricing move in a key product, a deterioration in developer velocity in the digital platform team, a supplier dependency risk in a critical infrastructure contract, a regulatory signal about upcoming compliance requirements, a retention problem in a high-value customer cohort, and a cross-sell conversion decline in branches.

At the technology services company: a change in enterprise deal cycle length, a talent attrition pattern in a specific engineering discipline, a customer satisfaction divergence between two product lines, a margin compression trend in managed services, a partner ecosystem shift, a product adoption plateau in mid-market accounts, a security vulnerability pattern in a legacy platform, and an emerging competitive threat from an adjacent market player.

Each of these signals was real, documented, and present in operational data at the time we started tracing. The question was whether they made it to the quarterly review in a form that was accurate, timely, and actionable.

What we found at each boundary

Boundary 1: Operational to team lead

The first transformation happened when operational data crossed into team-level reporting. This was the smallest loss point, typically 10-15% of signal content. Team leads were close enough to the work to preserve most of the specificity.

But even here, we saw consistent patterns. Quantitative signals were preserved well. Qualitative signals, like a shift in customer sentiment or a change in how a competitor was positioning, lost specificity. A sales rep’s observation that “enterprise deals are taking two to three extra weeks because procurement is adding a new AI governance review step” became “deal cycles lengthening slightly in enterprise segment.” The mechanism (the AI governance review) and the magnitude (two to three weeks) were already degrading.

Boundary 2: Team lead to department head

This is where serious loss began. Department heads aggregate across multiple teams. They have 30 minutes for their weekly report and five minutes of attention from their VP. Signals compete for space.

We saw two dominant patterns:

Priority filtering. Signals that aligned with existing departmental priorities were preserved. Signals that didn’t were dropped or mentioned briefly. The bank’s branch cross-sell decline was a clear example. The retail banking department head was focused on digital channel migration. Branch performance metrics were included in the report but not highlighted. The cross-sell decline appeared as a single line in a table. No narrative. No context. No connection to the strategic bet it was contradicting.

Normalisation. Signals were compared against historical baselines, and anything within “normal” range was classified as unremarkable. The technology company’s deal cycle lengthening was reported as “within seasonal variation” because Q3 deal cycles had historically been slightly longer. The underlying cause, the new procurement requirement, was a structural change being masked by a seasonal label.

At this boundary, we measured an average of 35% additional signal loss. Cumulative loss was now around 45%.

Boundary 3: Department head to VP/GM

The VP layer is where signals get repackaged for executive consumption. This is the boundary with the most consistent and severe degradation.

VPs optimise for coherent narrative. Their job is to present their function or division’s performance in a way that is comprehensible to a CEO and board. Comprehensibility requires simplification. Simplification requires choice. And the choices made at this boundary systematically favour coherence over completeness.

We documented a specific example at the bank that illustrates the pattern precisely. The loan default risk signal had been identified by the credit analytics team four months before our study began. Their analysis was specific: a new customer segment acquired through a digital partnership channel was showing default indicators 2.3x higher than the equivalent segment acquired through traditional channels, at a stage that was 60 days earlier in the loan lifecycle than baseline.

By the time this reached the Chief Risk Officer’s quarterly report, it read: “Credit risk metrics for digital partnership portfolio within acceptable parameters. Monitoring enhanced for newer vintage cohorts.”

The specificity (2.3x elevation, 60 days earlier), the urgency (this was a fast-moving problem), and the actionability (the digital partnership acquisition criteria needed immediate review) had all been removed. What remained was a statement that was technically accurate but strategically useless. The risk was “within acceptable parameters” because the absolute default rate was still low. The sample was new. The parameters themselves hadn’t been updated for this channel.

At this boundary, we measured 20-25% additional signal loss. Cumulative loss: approximately 65%.

Boundary 4: VP to quarterly review

The final compression. All of the VP-level inputs get assembled into a quarterly deck. A 60-minute meeting. Fifteen slides. Each function gets two or three slides. Discussion time is allocated primarily to the biggest issues, which means the issues already known to be big.

Emerging signals, the ones that are small now but strategically significant, are exactly the ones that get cut. They don’t warrant a slide. They don’t fit the existing narrative structure. They’re mentioned in appendices, if at all.

Of our 16 signals, the quarterly review representation looked like this:

• 3 signals were presented accurately and with enough context for a useful executive discussion
• 5 signals were mentioned but with significant loss of specificity, timing, or causal context
• 4 signals appeared only in appendix tables or backup slides that were never discussed
• 4 signals were completely absent from the quarterly materials

Three out of sixteen. The quarterly review accurately surfaced less than 20% of the strategic signals that were present in operational data.

The timing problem

Loss of content is only half the story. The other half is delay.

Of the eight signals that did appear somewhere in the quarterly review (even in degraded form), the average delay between operational detection and executive visibility was 94 days. The fastest was 47 days. The slowest was 163 days.

The bank’s competitor pricing signal is instructive. A competitor adjusted pricing on a key mortgage product in week two of the quarter. The product team noticed within days. Their analysis, including estimated impact on competitive win rates, was completed by week three. This analysis reached the department head in week five. It was included in the VP’s monthly report in week eight. And it appeared in the quarterly review in week thirteen.

By that point, the competitor had been in market with the new pricing for eleven weeks. The bank’s response, when it came, was reactive rather than proactive. The information had been available. The organisation’s reporting structure had delayed it past the point of timely action.

What the quarterly review optimises for

The quarterly review isn’t broken. It’s doing exactly what it’s designed to do, just not what executives think it’s designed to do.

It optimises for:

Completeness of coverage. Every function gets represented. Every major initiative gets a status. The review creates a sense of comprehensive oversight. But comprehensive coverage at a surface level is different from deep insight into the things that matter.

Narrative coherence. The quarterly story hangs together. Good news is presented with context. Bad news is presented with mitigating actions. The overall narrative arc is “challenges exist, but we’re managing them.” This coherence is reassuring. It’s also the mechanism that smooths out the warning signals that should be causing alarm.

Backward orientation. The quarterly review reports what happened. By definition, it’s a lagging view. The signals that matter most for strategic governance are leading indicators: things forming now that will become problems or opportunities in six to twelve months. Leading indicators are speculative. They’re uncertain. They don’t fit neatly into a backward-looking reporting format. So they get cut.

Political equilibrium. The quarterly review is a political event as much as an information event. Each presenter is managing their narrative. Each listener is assessing relative performance. The format implicitly rewards stability (“we’re on track”) and penalises surprise (“we didn’t see this coming”). This incentive structure suppresses exactly the kind of early, uncertain, potentially alarming signals that strategic governance needs most.

What would replace it

We’re not arguing that organisations should stop having quarterly reviews. The synthesis function matters. But the quarterly review cannot be the primary mechanism for strategic governance, because its structure is optimised against the information that matters.

What’s needed is a complementary system that operates at a different cadence with different design principles:

Continuous evidence streams. The 16 signals we traced should have been visible to senior leadership in something close to real time. Not as raw data dumps, but as curated evidence streams connected to specific strategic bets, with context provided by the people closest to the data.

Boundary transparency. The four organisational boundaries we identified as loss points need to be made visible. When a signal crosses from team to department to VP to executive, the transformation should be traceable. What was the original signal? What was passed along? What was lost? This isn’t about catching people hiding information. It’s about making the compression visible so that leaders can decide whether they’re comfortable with what’s being compressed away.

Leading indicator priority. The governance system should be biased toward emerging signals rather than established ones. A confirmed problem is already being managed (or should be). An emerging pattern that might become a problem, or an opportunity, in six months is where strategic attention adds the most value.

Shorter feedback loops. Ninety-four days between operational detection and executive visibility is too slow for strategic governance. Fortnightly or monthly evidence reviews for active strategic bets, focused on what the evidence is showing rather than what the team has delivered, would surface signals while they’re still actionable.

The structural argument

The quarterly review is not a broken tool. It’s a limited one. It was designed for an era when information moved more slowly, when strategic cycles were longer, and when the primary governance challenge was ensuring accountability for planned work.

The current environment is different. Competitive shifts happen in weeks, not quarters. Customer behaviour changes faster than annual plans can anticipate. AI is accelerating execution speed while the governance mechanisms that oversee execution remain on quarterly cadence.

We traced 16 signals. Thirteen of them were degraded below the threshold of usefulness by the time they reached the leadership team. That isn’t a failure of the people involved. Every person in every reporting chain we studied was competent and acting in good faith. The failure is structural. The quarterly review is a lossy compression algorithm applied to a high-bandwidth signal environment. What it loses is exactly what leadership needs most: specificity, timeliness, and early warning.

The organisations that figure out how to complement the quarterly review with continuous, evidence-based strategic governance will see their operating environment more clearly. The ones that don’t will keep making decisions based on 33% of the information that’s available to them and wonder why their strategies keep drifting off course.