When team-level plans are aggregated upward and the total falls short of the organizational target, you have an alignment gap. Here’s how to negotiate, not mandate, a resolution.
The Number Nobody Wants to See
It’s day 12 of the quarter. Teams have spent 10 days building their bottom-up plans — honestly, from ground-level data, with the AI assistant helping them import pipeline projections and shape their distributions. The parent KR owner opens Profit.co’s aggregated view and sees three numbers:
Top-down target: $5.0M
Aggregated bottom-up: $4.2M
Gap: $800K (16%)
Sixteen percent. Not a rounding error. Not a minor calibration issue. A structural gap between what leadership expects and what the teams collectively believe they can deliver. This gap is uncomfortable. It implies one of three things: leadership’s target was too ambitious, the teams are being too conservative, or something material has changed since the target was set.
The instinct in most organizations is to close this gap with pressure: “We committed to $5M. We need to find the extra $800K.” This approach closes the gap on paper but not in reality. The teams adjust their numbers upward, the aggregate now matches the target, and three months later the QBR reveals a miss of — you guessed it — approximately $800K.
The aggregation gap is not a problem to be closed with pressure. It’s a signal to be diagnosed with curiosity. The gap tells you something important about the relationship between your strategic ambition and your execution capacity. Ignoring it doesn’t make it go away. It just delays the discovery.
Diagnosing the Gap: Five Root Causes
Before deciding how to respond to the gap, you need to understand what’s causing it. In our experience, aggregation gaps fall into one of five categories, each requiring a different response:
Cause 1: Capacity Constraint
The teams don’t have enough people, budget, or tooling to deliver the target. This is the most common cause and the most legitimate. A team that lost two engineers, a team whose budget was cut mid-planning, or a team that’s carrying 120% of their normal workload simply cannot produce at the rate the target assumes.
Diagnostic question: Has anything changed in team capacity since the target was set? Headcount, budget, tool availability, competing priorities?
Evidence: Staffing changes, budget revisions, or project load data that post-date the target-setting process.
Response: Either add capacity (backfill, budget, tooling) or reduce the target to match available capacity. Do not ask the team to “do more with less” without specifying what “less” they should do.
Cause 2: Risk Discounting
The teams are accounting for risks that leadership hasn’t factored into the target. A dependency might slip. A market assumption might not hold. A new hire might not ramp as fast as expected. Teams who plan honestly include these risks in their projections; leadership targets often don’t.
Diagnostic question: What risks are the teams pricing into their plans that weren’t reflected in the top-down target?
Evidence: Specific risk factors documented in team plans or check-in notes: dependency timelines, market uncertainty, ramp-up periods for new hires.
Response: Evaluate each risk. If the risks are legitimate, the gap is real and the target should adjust. If the risks are speculative, the team may be over-discounting — discuss which risks to plan for and which to accept.
Cause 3: Sandbagging
The teams are deliberately planning below their capability to ensure they hit their numbers. This is the cause that leadership most often suspects and the one that’s actually least common — but it does happen, especially in organizations where OKR attainment is tied to performance reviews or compensation.
Diagnostic question: How do the team’s bottom-up projections compare to their actual performance last quarter, adjusted for known changes?
Evidence: A team that delivered $1.6M last quarter and is now projecting $1.2M with no material change in conditions. The gap between historical performance and current projection is unexplained.
Response: Present the comparison data directly. “Last quarter you delivered $1.6M. Your current projection is $1.2M. What’s changed that accounts for the $400K reduction?” If the answer is specific and credible (capacity loss, market change), accept it. If it’s vague, calibrate upward.
Cause 4: Information Asymmetry
Leadership set the target based on information that the teams don’t have, or the teams are planning based on information that leadership doesn’t have. The gap exists because the two levels are literally working with different data.
Diagnostic question: What does leadership know that teams don’t? What do teams know that leadership doesn’t?
Evidence: Leadership may know about an upcoming partnership, a budget increase, or a strategic initiative that hasn’t been communicated. Teams may know about a channel degradation, a technical constraint, or a competitive threat that hasn’t reached leadership.
Response: Share the information in both directions. Once everyone is working from the same data, recalibrate the plans. This cause is the easiest to fix — the gap was never about capability or ambition, just about incomplete information.
Cause 5: Stale Target
The target was set weeks or months ago based on conditions that have since changed. The market shifted, a product launch moved, a key customer churned, or a regulatory change altered the landscape. The target is a historical artifact; the bottom-up plans reflect current reality.
Diagnostic question: Have the conditions that informed the original target changed materially since it was set?
Evidence: Specific events or data points that post-date the target-setting process and affect the KR’s achievability.
Response: Update the target. A stale target is not a commitment — it’s an outdated estimate. Adjusting it to reflect current conditions is adaptive planning, not failure.
The Gap Resolution Framework
Once you’ve diagnosed the root cause, the gap needs to be resolved. There are five resolution strategies, ranked from most to least interventionist:
| Strategy | When to Use | How It Works | Typical gap closure |
|---|---|---|---|
| Invest to close | The gap is caused by a specific, solvable constraint: a missing hire, an unfunded initiative, a tool that would accelerate output. | Fund the constraint. Backfill the role, approve the budget, purchase the tool. Teams revise their plans upward based on the new capacity. | High (50–100% of gap) |
| Redistribute across teams | Some teams have more capacity headroom than others. The gap is concentrated in one or two teams but can be absorbed by others. | Shift target allocation from constrained teams to teams with capacity. The total stays the same; the distribution changes. | Medium (30–60% of gap) |
| Negotiate a stretch | Teams’ plans are honest but slightly conservative. A modest stretch (5–10% above their bottom-up projection) is achievable with effort. | Ask each team to add a specific, bounded stretch to their plan. “Can you absorb an additional $50K if we prioritize your Q3 dependency?” | Medium (20–40% of gap) |
| Accept the gap partially | Part of the gap is structural (capacity, stale target) and part is addressable. Close the addressable portion and adjust the target for the rest. | Combine two or more strategies above to close part of the gap. Reduce the parent target by the remaining unaddressable portion. | Partial (varies) |
| Accept the gap fully | The gap is entirely structural. Teams are planning honestly. The target was set with incomplete information or conditions have changed. | Reduce the parent target to match the aggregate. Communicate the revised target upward with the root cause analysis. | 0% — target adjusts to aggregate |
The resolution strategy should match the root cause diagnosis. Invest to close works for capacity constraints. Redistribute works for uneven allocation. Negotiate a stretch works for mild conservatism. Accept works for stale targets and structural gaps. Using the wrong strategy — stretching teams when the problem is capacity, or investing when the problem is a stale target — wastes resources and erodes trust.
The Resolution Meeting: A 30-Minute Protocol
The gap resolution meeting should be structured, time-boxed, and data-driven. Here’s a 30-minute protocol that works for gaps up to 20%:
Minutes 1–5: Present the Gap
The parent KR owner shares the three numbers: top-down target, aggregated bottom-up, and gap. They show the breakdown by child team: which teams are above their proportional share, which are below, and by how much. This data comes directly from Profit.co’s aggregated parent view. No slides needed — project the dashboard.
Minutes 5–15: Diagnose
Go team by team, focusing on the biggest contributors to the gap. For each, ask: what’s the root cause? Each team lead answers in one to two sentences, using the five-cause framework. The facilitator categorizes each contribution: capacity, risk, sandbagging, information asymmetry, or stale target.
This diagnostic step is the most important part of the meeting. Without it, the resolution conversation degrades into negotiation theater where the loudest voice wins. With it, the resolution is evidence-based.
Minutes 15–25: Resolve
Based on the diagnosis, the parent KR owner proposes a resolution strategy for each contributing team. The proposals should be specific and bounded:
“Team A’s gap is capacity-driven. We’ll backfill the AE role with a contractor. If approved, Team A revises their plan up by $120K.”
“Team B’s gap is risk-based — the channel algorithm change. I agree this is a legitimate risk. We’ll accept Team B’s plan as-is.”
“Team C projected $300K below last quarter with no material change. Team C, can you stretch by $100K? That would bring you to $200K below last quarter — still conservative but less so.”
“The remaining $280K gap is structural. I recommend we reduce the parent target from $5.0M to $4.72M.”
Each team lead accepts, counters, or escalates their specific proposal. Most proposals are accepted because they’re grounded in the diagnostic data.
Minutes 25–30: Lock and Document
The agreed resolution is executed in Profit.co during the meeting:
Teams that agreed to stretch modify their plans using the AI assistant: “Increase target by $100K. Redistribute into February and March.”
The parent target is adjusted if needed via inline From/To editing.
The parent’s check-in notes document the gap resolution: “Q2 aggregation gap: $800K (16%). Resolution: $120K from contractor backfill (Team A), $100K stretch (Team C), $580K target reduction. Revised target: $4.72M.”
The reconciled aggregate in Profit.co matches the revised parent target. The operating plan is locked.
The entire meeting takes 30 minutes because the data is already in Profit.co. The aggregated view, the team-by-team breakdown, and the plan modification tools are all accessible in the same session. There are no spreadsheets to reconcile, no slides to prepare, no formulas to verify.
The Mid-Quarter Aggregation Gap
The aggregation gap isn’t just a quarter-start phenomenon. It can appear — or reappear — mid-quarter when teams modify their plans in response to signals. Profit.co’s threshold notification system handles this automatically.
How It Works
When any child plan is modified, the parent’s aggregated view updates in real time. If the aggregated total deviates from the parent target by more than the configured threshold (typically 10–15%), the parent KR owner receives a notification: “Aggregated plan is now $4.5M against a target of $4.72M. Gap: $220K (4.7%). Triggered by: Team B reduced March targets by $180K.”
The notification includes which child modification triggered the alert, so the parent owner can assess whether the gap requires a full re-resolution or just awareness. Small gaps (under 5%) typically don’t require action — they’re logged for the quarterly review. Larger gaps (over 10%) trigger a mini-resolution conversation: a 10-minute check-in with the affected team and the parent owner.
The Progressive Gap Pattern
Watch for a pattern where the aggregation gap grows progressively over the quarter. If the gap is 5% at week 4, 8% at week 6, and 12% at week 8, that’s not three independent modifications — it’s a systemic signal. The parent plan’s target may be fundamentally misaligned, and the children’s modifications are collectively revealing the true trajectory.
When you see a progressive gap, don’t address each individual modification. Step back and assess the parent target itself. A progressive gap that has grown for three consecutive modifications is almost certainly telling you the target needs to change.
Communicating the Gap Upward
When the gap requires a parent target reduction, the parent KR owner needs to communicate this upward — to the VP, the CEO, or the board. This conversation uses the same Signal-Impact-Solution framework, but with the aggregation data as the signal:
“Our four teams have completed their Q2 bottom-up plans. The aggregate is $4.2M against our $5.0M target — a 16% gap. The primary drivers are: a capacity constraint in Team A (lost a senior AE), a channel algorithm change affecting Team B (40% reduction in organic reach), and a partnership delay in Team D (launch moved from April to June). After our resolution meeting, we’ve closed $220K through a contractor backfill and a modest stretch from Team C. The remaining $580K gap is structural. I recommend reducing the Q2 target to $4.72M. This reflects the realistic aggregate with interventions applied.”
The key elements of this communication: the gap is presented as a data output, not a negotiating position. The root causes are specific and attributed. The resolution actions already taken are documented. The remaining gap is structural and the recommended target adjustment is explicit.
Notice that the parent owner has already taken action (contractor backfill, stretch negotiation) before presenting to leadership. This positions them as a problem-solver who has partially closed the gap, not as a messenger delivering bad news.
What Not to Do with the Gap
The aggregation gap invites several counterproductive responses. Here are the most common, and why they fail:
| Bad Response | Why It Fails | What to Do Instead |
|---|---|---|
| Mandate that teams increase their plans to match the target. | Teams adjust their numbers but not their beliefs. The plans now show $5M, but execution still tracks at $4.2M. The QBR surprise is preserved, just delayed. | Diagnose the root cause. Invest or redistribute to close the gap through real capacity changes, not number changes. |
| Split the gap equally across all teams. | Equal distribution of a gap is equitable but not intelligent. The team with capacity headroom absorbs the same stretch as the team that’s already at 120% capacity. | Distribute the gap based on capacity analysis. Teams with headroom absorb more. Teams at capacity absorb less or none. |
| Ignore the gap and hope teams overperform. | Hope is not a strategy. If the gap is 16%, the probability that all teams overperform by exactly the right amount is near zero. | Accept the gap, reduce the target, and communicate the revised number with the root cause analysis. |
| Add the gap as an unallocated “stretch target” at the parent level. | A parent target of $5M with children summing to $4.2M creates a permanent 16% misalignment in every dashboard and report for the entire quarter. | If you want to maintain an aspirational target, document it separately. The operating plan (what the hierarchy tracks) must match the aggregate. |
| Punish the teams with the largest gaps. | Teams learn that honest bottom-up planning leads to punishment. Next quarter, they’ll plan to the executive number regardless of reality, and you’ll lose the bottom-up signal permanently. | Reward honest planning. The team that identified a gap early gave you information that saves the organization from a bigger surprise later. |
Tracking Gap Health Over Time
The aggregation gap is a recurring metric that reveals your organization’s planning calibration quality. Track it over successive quarters to identify trends:
| Metric | What It Measures | Healthy Trend |
|---|---|---|
| Initial gap size (day 12) | The gap between top-down target and first bottom-up aggregate. | Decreasing. As leadership and teams develop shared understanding of capacity, the initial gap should shrink from 15–20% to under 10%. |
| Resolved gap (day 14) | The gap remaining after the resolution meeting, before any target adjustment. | Decreasing. Better diagnosis and more creative resolution strategies close more of the gap through investment and redistribution. |
| Target adjustment frequency | How often the parent target is reduced to match the aggregate. | Stable, then decreasing. Some adjustment is healthy (it means you’re calibrating). Frequent large adjustments suggest targets are set without sufficient input. |
| Progressive gap growth | The increase in aggregation gap from quarter-start to quarter-end due to mid-quarter modifications. | Stable at 3–5%. Some mid-quarter gap growth is expected as conditions change. Growth above 10% suggests the initial plans didn’t account for likely risks. |
| Gap root cause distribution | The breakdown of gap causes: capacity, risk, sandbagging, information asymmetry, stale target. | Shift toward information asymmetry (fixable) and away from stale targets (preventable). Capacity gaps are structural and will always exist. |
The organizations that track aggregation gap metrics over time develop a superpower: they can predict the gap before the bottom-up plans are submitted. When you know that your organization typically has a 12% initial gap driven primarily by capacity constraints, you can set the top-down target 5–8% higher than your aspirational number, expecting the resolution process to calibrate it to the right level.
The Gap Is the Conversation
The aggregation gap is uncomfortable. It represents the distance between ambition and reality, and no organization likes to stare at that distance. But the organizations that face the gap head-on — that diagnose its causes, resolve what they can, and adjust what they must — are the organizations that end the quarter with plans they believed in and results that match.
The alternative is to paper over the gap with pressure, watch the plans drift apart from execution, and arrive at the QBR with the same gap disguised as a “miss.” The gap doesn’t go away when you close it with numbers. It goes away when you close it with diagnosis, investment, and honest calibration.
An aggregation gap at the start of the quarter is a planning input. An aggregation gap at the end of the quarter is a planning failure. The only variable is whether you chose to process it at day 12 or discover it at day 90.
See the gap the moment it appears. Resolve it before it compounds.
Profit.co’s real-time aggregation, threshold notifications, and inline plan modification give you the tools to diagnose and resolve aggregation gaps in a single 30-minute session. Start your free trial.