Teams closest to execution often have the most accurate view of what’s achievable. A framework for when bottom-up plans should reshape the top-level target — and how to make the case.
The Information Advantage at the Edge
There’s a persistent assumption in organizational planning that the people at the top have the best view. They see the full landscape: the market, the competition, the board’s expectations, the strategic priorities. From their vantage point, they set targets that reflect the organization’s ambition and distribute them downward.
This view is half right. Leadership does have the best view of strategic context. But they have the worst view of execution reality. They don’t know that the sales team’s top performer is on parental leave for six weeks. They don’t know that the engineering team’s velocity dropped 25% because two seniors left last month. They don’t know that the marketing team’s best channel just changed its algorithm, cutting organic reach by 40%.
The people who know these things are the teams themselves. They live in the execution reality every day. Their planning data — pipeline projections, sprint velocities, channel performance, capacity models — is richer, more current, and more specific than anything available at the leadership level. When this data says the executive target is unrealistic, the bottom-up signal should be heard.
Bottom-up planning doesn’t replace top-down targets. It pressure-tests them. The executive target represents strategic ambition. The bottom-up plan represents execution reality. The gap between them is the most important number in your planning process.
When Bottom-Up Should Lead
Not every KR benefits from bottom-up planning. Some are best set from the top (see our companion article on top-down distribution). Bottom-up planning is the right approach in specific circumstances:
| Condition | Why Bottom-Up Leads | Example |
|---|---|---|
| Teams have proprietary execution data. | Pipeline models, velocity metrics, channel analytics — data that leadership doesn’t see in real time. | A sales team with CRM pipeline data projecting $1.4M when leadership’s target is $2M. |
| The KR depends on new or experimental approaches. | When the path to the target is unproven, the team’s assessment of feasibility is more realistic than a top-down stretch. | A growth team testing a new acquisition channel with no historical conversion data. |
| Capacity has recently changed. | Hiring delays, departures, or reassignments that leadership may not have factored into the target. | An engineering team that lost two senior developers mid-quarter. |
| The KR spans multiple contributing teams. | No single leader owns the full picture. Each team’s contribution must be planned independently and aggregated. | A customer satisfaction KR that depends on Support response time, Product bug fix rate, and Success team outreach. |
| Historical data contradicts the executive target. | Last quarter’s actuals provide the best baseline for this quarter’s projection. | A retention KR where last quarter’s data shows 4.2% churn, but the target assumes 2.5% — a 40% improvement with no identified intervention. |
The Bottom-Up Planning Workflow
In Profit.co, bottom-up planning follows a four-step workflow that produces an aggregated view for leadership to review:
Step 1: Teams Build Their Own Plans
Each child KR owner opens Modify Plan and builds their plan independently. They use whatever data source is most relevant to their context: importing from a pipeline spreadsheet, pasting from a sprint planning tool, describing the plan shape based on their operational knowledge, or using last quarter’s actual pattern as a template.
The AI assistant is particularly useful here. A sales team lead can say: “Build an S-curve from 0 to $1.4M. Slow start through January while pipeline matures, steep ramp in February when the top deals are expected to close, tapering in March.” The assistant generates the distribution in seconds, and the team lead reviews against their pipeline data.
The critical instruction to teams is: plan for what you believe is realistically achievable with your current resources and knowledge. Not what you hope for. Not what leadership wants to hear. What you actually expect to deliver, given what you know today.
The honesty of bottom-up planning is its greatest value and its greatest vulnerability. If teams plan conservatively to guarantee they’ll hit their number, the aggregate will be artificially low. If they plan aspirationally to avoid a difficult conversation, it’ll be artificially high. The instruction must be clear: plan for the realistic case, not the best case or the safe case.
Step 2: Profit.co Aggregates Upward
As child plans are set, Profit.co automatically aggregates them into the parent KR’s plan view. The aggregation is real-time: as each team submits their plan, the parent’s aggregated total updates.
The parent plan view shows three numbers for each check-in period: the parent’s own target (if one was set top-down), the aggregated sum of children’s plans, and the gap between them. This three-number view is the foundation for the alignment conversation.
If the parent KR has no top-down target yet (pure bottom-up mode), the aggregated sum becomes the proposed parent target. Leadership reviews this number and decides whether to accept it, negotiate it upward, or accept a version between the aggregate and their original aspiration.
Step 3: The Gap Conversation
The gap between the aggregated bottom-up plans and the leadership target is the most important number in hierarchical planning. It represents the difference between what leadership expects and what teams believe they can deliver. This gap is not a problem to be solved by pressure — it’s information to be processed.
There are three possible states:
No Gap (Rare but Ideal)
The aggregated plans match the leadership target. No negotiation needed. This happens occasionally when the target was well-calibrated and teams’ assessments confirm it.
Negative Gap: Bottom-Up < Top-Down
This is the most common state. Teams collectively plan for less than leadership expects. The gap conversation should explore the root cause before pushing for closure:
Is the gap caused by capacity? If teams are short-staffed, the gap reflects a resource constraint, not a motivation gap. The response is to either add resources or reduce the target.
Is the gap caused by risk assessment? If teams are discounting for risks that leadership hasn’t considered, the gap represents information that leadership needs to hear. Investigate the risks.
Is the gap caused by conservatism? If teams are sandbagging, the gap is artificial. The evidence for this is usually in the comparison with last quarter’s actuals: if the team achieved $1.6M last quarter and is now planning for $1.2M with no material change in conditions, there’s a calibration issue.
Positive Gap: Bottom-Up > Top-Down
Teams collectively plan for more than leadership expected. This is an opportunity signal. The response is usually to keep the upside: raise the parent target to match the aggregate, or treat the excess as a buffer. Investigate the optimism to ensure it’s grounded in data, not wishful thinking.
Step 4: Reconcile and Lock
After the gap conversation, the reconciled plan is locked in. In Profit.co, this means:
If the parent target is adjusted to match the aggregate, the parent KR’s To value is updated via inline editing. The reconciliation prompt fires, and the parent plan is redistributed.
If teams are asked to stretch, the affected child owners modify their plans upward. The AI assistant makes this fast: “Increase my target by 10% and redistribute equally.”
If a compromise is reached, both parent and select children are adjusted. The parent target is set to the negotiated number; the children whose plans were furthest from the needed stretch absorb the delta.
The aggregated view in Profit.co confirms that children now sum to the parent. The operating plan is locked.
Making the Case: How to Present a Bottom-Up Number That’s Below Target
The hardest moment in bottom-up planning is presenting an aggregate that falls short of the executive target. The team lead or department head has to tell their VP: “Our teams collectively believe they can deliver $4.2M. Your target is $5M. Here’s why.”
This conversation follows the same Signal-Impact-Solution framework from our Manager’s Guide article, with one adaptation: the signal is the aggregated bottom-up data, not an external event.
“Our four teams have independently built their Q2 plans based on current pipeline data, staffing levels, and channel performance. The aggregate comes to $4.2M against a target of $5M — an $800K gap. The primary drivers are: Team A lost their senior AE and projects $200K less in enterprise deals; Team B’s primary channel reduced organic reach by 40%, reducing projected leads by 30%; and Team C’s key partnership launch moved from April to June. I’ve prepared three options: accept $4.2M as the realistic target, invest in backfilling Team A’s role with a contractor to recover $120K, or accelerate Team D’s expansion plan to absorb $150K. The best realistic case with intervention is $4.47M.”
Notice the structure: the aggregate number is presented as a data-driven output, not a negotiating position. The drivers are specific and attributable. The options include both acceptance and intervention. This framing positions the presenter as a strategic partner offering diagnosis and solutions, not as a team that couldn’t meet expectations.
The Information Feedback Loop
Bottom-up planning doesn’t end when the operating plan is locked. It creates a continuous information feedback loop that improves planning accuracy over time:
During the Quarter: Bottom-Up Signals Drive Modifications
As teams check in against their bottom-up plans, the check-in data provides real-time signal about whether the plans are accurate. When a team modifies their plan mid-quarter (per the 72-Hour Rule), the aggregated parent view updates automatically. If three teams independently modify their plans downward based on ground-level signals, the parent owner sees the cumulative impact without waiting for anyone to report it.
This is the real-time version of the gap conversation. The initial reconciliation happened in the first two weeks. The ongoing aggregation keeps the conversation alive for the remaining 11 weeks. The parent view is never stale because it always reflects the latest child plans.
After the Quarter: Bottom-Up Accuracy Drives Better Calibration
At the end of the quarter, compare the final attainment of each KR to three benchmarks: the original top-down target, the bottom-up plan, and the final modified plan. This three-way comparison reveals calibration patterns:
| Pattern | What It Means | Action for Next Quarter |
|---|---|---|
| Bottom-up plan was more accurate than top-down target. | Teams had better information than leadership for this KR. Bottom-up should lead next quarter. | Default to bottom-up planning. Use top-down only as a ceiling, not a target. |
| Top-down target was more accurate than bottom-up plan. | Teams were either too conservative or too optimistic. Leadership’s strategic view was closer to reality. | Use top-down distribution. Give teams a refine window but weight leadership’s assessment more heavily. |
| Both were inaccurate. Final modified plan was closest. | Neither initial assessment was right, but the adaptive modification process corrected course. | Focus on modification speed and quality rather than initial plan accuracy. The 72-Hour Rule is the critical lever. |
| Bottom-up was conservative by >15%. | Teams were sandbagging. The aggregate was artificially low. | Calibrate by comparing bottom-up proposals to last quarter’s actuals. Flag teams whose plans are significantly below their historical performance without a documented reason. |
Over successive quarters, this feedback loop tightens the calibration of bottom-up plans. Teams learn how their initial estimates compare to outcomes. Leadership learns which teams are reliable bottom-up planners and which need calibration assistance.
Bottom-Up in a Hierarchical Context
Bottom-up planning works differently at different levels of the hierarchy. The dynamics change based on how many levels separate the planning teams from the leadership target:
Two-Level Hierarchy (VP → Teams)
The simplest case. Teams plan, the VP aggregates and reviews, the gap conversation is direct. One reconciliation meeting covers everything. This works well for departments of 3–6 teams.
Three-Level Hierarchy (VP → Directors → Teams)
Aggregation happens in two stages. Teams’ plans aggregate into director-level views. Directors reconcile within their organizations first (days 4–10). Then directors’ reconciled plans aggregate into the VP-level view, and the VP reconciles across directors (days 10–14). The refine window is the same, but the reconciliation is staged.
Four+ Level Hierarchy
At four or more levels, bottom-up planning becomes a rolling aggregation. Each level reconciles with the one above it in sequence. The total refine-and-reconcile cycle may extend to 18–21 days. To keep this manageable, the lowest two levels should use a compressed 7-day window, and each aggregation level adds 3–4 days.
The deeper the hierarchy, the more important it is to start bottom-up planning early. In a four-level hierarchy, teams should begin building their plans at least 5 days before the quarter starts. The rolling aggregation then completes by the end of week 2.
Common Pitfalls of Bottom-Up Planning
| Pitfall | What Happens | The Fix |
|---|---|---|
| Anchoring to the top-down number | Teams know the executive target and plan to match it instead of planning honestly. The bottom-up process produces a mirror of the top-down target, defeating the purpose. | Don’t share the executive target with teams before they build their plans. Let the bottom-up process run blind, then compare. |
| Uneven planning quality | Some teams build rigorous plans from pipeline data. Others guess. The aggregate mixes precision with noise, reducing its signal value. | Train all teams on the same planning methodology. Provide templates and AI import tools. Set a minimum standard: every plan must reference a data source. |
| The loudest team wins the gap negotiation | In the reconciliation meeting, the team with the best presenter or the most political capital absorbs less of the gap, even if they have more capacity. | Use objective criteria for gap distribution: capacity ratios, historical performance, risk-adjusted projections. The data should drive the negotiation, not the personalities. |
| Aggregation without reconciliation | Teams build plans, Profit.co aggregates them, and leadership accepts the aggregate without reviewing the gap. The gap conversation never happens. | Schedule the reconciliation meeting as a calendar event at the start of every quarter. It’s 30 minutes on day 12–14. Non-negotiable. |
| Treating bottom-up as an annual exercise | Teams build bottom-up plans once per year and then receive top-down distributions for quarterly plans. The ground-level signal goes stale. | Run bottom-up planning every quarter for the KRs where teams have the information advantage. It’s a 15-minute per-KR exercise with AI tools, not a multi-week planning cycle. |
Combining Bottom-Up with Top-Down
Bottom-up and top-down planning are not mutually exclusive. In practice, the best organizations use both in the same quarter, for different KRs:
| KR Characteristic | Planning Approach | Rationale |
|---|---|---|
| Clear strategic target with proven execution path | Top-down distribution with refine window | Leadership has the best signal on the target. Teams refine the distribution. |
| Team has proprietary data that leadership can’t access | Bottom-up with aggregation | Teams have the best signal on achievability. Aggregate and reconcile. |
| New initiative with high uncertainty | Bottom-up with scenario variants | Nobody has strong signal. Let teams plan their realistic case, then compare to leadership’s aspiration. |
| Cross-functional KR with multiple contributors | Bottom-up from each contributor, aggregated at the shared parent | No single leader can set the target. Each team plans their contribution independently. |
| Operational KR with stable trajectory | Top-down with linear distribution | Minimal uncertainty. Leadership’s target matches historical data. Simple cascade is sufficient. |
The decision of which approach to use for each KR should be made during the quarterly planning kickoff. The KR owner and their manager agree: is this a top-down or bottom-up KR this quarter? The answer may change quarter to quarter as the organization gains confidence in the team’s planning capability or as the strategic context evolves.
The Gap Is the Gift
Organizations that embrace bottom-up planning quickly discover something counterintuitive: the gap between the bottom-up aggregate and the top-down target is the most valuable output of the entire planning process. It’s not a problem to be minimized. It’s information to be processed.
A gap that says “teams believe they can deliver 85% of the target” is telling leadership exactly three things. First, the teams have assessed their capacity and it falls short of the ambition. Second, the specific reasons are identifiable and potentially addressable. Third, any target that ignores this gap is aspirational, not operational — and the organization should decide consciously whether it wants an aspirational number or a realistic one.
The organizations that process this gap productively — identifying root causes, investing in interventions, adjusting targets where the gap is structural — end up with operating plans that people believe in and execute against with genuine commitment. The ones that override the gap with pressure end up with plans that look good on paper and miss by exactly the amount the gap predicted.
The question bottom-up planning answers is not “what do we want?” — that’s leadership’s job. The question it answers is “what can we actually do?” The best planning processes honor both questions and reconcile the answers honestly.
Let the edge inform the center.
Profit.co’s bottom-up aggregation gives leadership a real-time view of what teams actually plan to deliver. The gap between bottom-up and top-down is visible the moment it appears — not at the QBR. Start your free trial.