Setting targets from the top is efficient, but rigid cascades kill ownership. Here’s how to distribute plans downward while preserving room for teams to adapt at their level.
The Tension at the Heart of Top-Down Planning
Top-down planning is efficient. A VP sets a quarterly target, defines how it should be distributed across the quarter, and pushes that distribution down to their directors, who push it to their teams. In five minutes, every level of the hierarchy has a plan. Alignment is guaranteed by construction — the children’s plans sum to the parent’s target because they were derived from it.
The problem is that this efficiency comes at a cost: the teams who receive the plan didn’t build it. They don’t own it. The distribution was designed at a level above them, by someone who may not understand the ground-level dynamics that determine how work actually gets done. The VP’s S-curve might assume a February ramp, but the team knows their key dependency doesn’t deliver until March. The VP’s equal allocation across three directors might not account for the fact that Director A has twice the capacity of Director C.
This tension — between top-down alignment and bottom-up ownership — is the central challenge of hierarchical planning. Resolve it in favor of alignment, and you get coordinated plans that nobody believes in. Resolve it in favor of ownership, and you get realistic plans that nobody coordinates. The solution is to resolve it in favor of both: distribute the shape from above, then let teams refine the details below.
Top-down distribution should set the starting point, not the final word. The plan that leadership distributes is a first draft. The plan that teams refine is the operating plan. The gap between them is where alignment conversations happen.
What Gets Distributed and What Doesn’t
The key design decision in top-down distribution is what to cascade and what to leave for teams to define. Getting this right is the difference between productive alignment and micromanagement.
| Distribute from the Top | Leave for Teams to Define | Why |
|---|---|---|
| The quarterly target (To value) | The distribution shape within the quarter | Leadership should set the destination. Teams should choose the route based on their execution dynamics. |
| The proportional allocation between children | Individual period-level targets | Leadership knows the relative capacity of each team. Teams know their week-by-week reality. |
| The overall distribution shape as a starting point | Refinements to match local dependencies and capacity | The shape is a hypothesis about how the quarter unfolds. Teams closest to execution have the best data to refine it. |
| The check-in frequency | Nothing — check-in frequency should be consistent | Mixed frequencies across the same hierarchy level create aggregation problems. Standardize within each level. |
| Propagation rules for re-cascading | The modification decisions within those rules | Leadership sets the governance. Teams operate within it autonomously. |
The rule of thumb: distribute the “what” (targets and allocations) from the top. Let teams define the “how” (period-level distribution, shape, and timing) from the bottom. This preserves alignment on outcomes while giving teams autonomy over execution planning.
The Distribution Workflow in Profit.co
Here’s the step-by-step process for distributing a plan from a parent KR to its children:
Step 1: Set the Parent Plan
The parent KR owner (typically a VP or director) opens Modify Plan and sets the distribution for the parent KR. This can be done manually, via AI import from a spreadsheet, or with a natural language command: “S-curve with 20% in month one, 45% in month two, 35% in month three.”
The parent plan represents leadership’s view of how the target should unfold across the quarter. It doesn’t need to be perfect — it needs to be directionally correct and internally consistent.
Step 2: Choose the Allocation Method
Before distributing, the parent owner selects how the target is allocated across children. Profit.co supports four allocation methods:
| Method | How It Works | Best For |
|---|---|---|
| Equal split | Each child receives an equal share of the parent’s target. If there are 4 children, each gets 25%. | Teams of similar size and capability working on comparable scopes. |
| Weighted allocation | Each child receives a share proportional to a manually assigned weight. E.g., 40/30/30 across three children. | Teams of different sizes or with different capacity levels. |
| Proportional to existing range | Each child’s share is proportional to their own From/To range relative to the total of all children’s ranges. | When child KRs already have targets set and you want the distribution to respect those pre-set targets. |
| Custom allocation | The parent owner specifies exact target amounts for each child. | When the allocation doesn’t follow any formula — one team gets a fixed amount, another gets the rest. |
Step 3: Distribute
Click Distribute to Children. Profit.co calculates each child’s plan based on the parent’s distribution curve and the chosen allocation method. Each child’s plan preserves the parent’s shape (S-curve, back-loaded, linear) while scaling the absolute values to fit the child’s allocated portion of the target.
If a child KR has a different check-in frequency than the parent (e.g., parent is weekly, child is monthly), Profit.co aggregates the parent’s weekly values into monthly totals for the child.
Step 4: Notify Child Owners
Each child KR owner receives a notification: “A plan has been distributed to your KR from [parent KR name]. Please review and refine within 10 days.” The notification includes a link to the child KR’s Modify Plan view, where the distributed plan is already loaded.
The notification framing matters. It says “review and refine,” not “accept.” This language signals that the distributed plan is a starting point, not a mandate.
The Refine Window: Where Autonomy Lives
The refine window is the 10-day period after distribution during which child KR owners are expected to review their distributed plans and modify them based on ground-level knowledge. This is the mechanism that transforms top-down distribution from a mandate into a conversation.
What Teams Do During the Refine Window
-
Check the shape against local reality. Does the S-curve ramp match when their dependency delivers? Does the back-loading align with their team’s actual capacity curve? If not, they reshape: “Shift the ramp from week 5 to week 7. My API dependency delivers in week 6, not week 4.”
-
Validate the allocation. Is their proportional share of the parent target realistic given their current capacity? If the team lost a member or gained a project, the allocation may need adjustment. They note the discrepancy and propose a revised target.
-
Import their own operational data. Many teams have their own planning data — pipeline projections, sprint velocities, campaign calendars — that is more detailed than the distributed plan. They paste or upload this data into the AI assistant, which reconciles it with the distributed plan and generates a refined version.
-
Flag irreconcilable gaps. If the distributed target is fundamentally unrealistic (e.g., the parent allocated $2M to a team that projects $1.4M in pipeline), the team flags this to the parent owner during the refine window. This triggers a negotiation, not a silent acceptance of an impossible target.
The refine window is not optional. If teams skip it and accept the distributed plan without review, two things happen: they’re executing against assumptions they haven’t validated, and the organization misses the bottom-up signal that would improve the parent plan. Mandate the review. Make it a 15-minute task, not a planning session.
The Reconciliation Conversation
After the refine window closes, the parent KR owner reviews the aggregated bottom-up plans. In Profit.co, this is a single view: the parent plan shows the original distributed target alongside the aggregated total of all children’s refined plans. If these numbers match, reconciliation is complete. If they don’t, a conversation is needed.
When Children’s Plans Sum to Less Than the Parent Target
This is the more common case. Teams refine their plans downward based on realistic assessments, and the aggregate falls short. The gap requires one of three responses:
Negotiate upward: ask one or more teams to absorb more of the target. This works when some teams were conservative and have capacity headroom.
Redistribute: shift the gap to a team that was under-allocated or that has a specific advantage (a new hire starting, a partnership launching).
Adjust the parent target: reduce the parent’s total to match the realistic aggregate. This is the honest response when the original target was set with insufficient information.
When Children’s Plans Sum to More Than the Parent Target
This happens when teams are optimistic or when the allocation method underestimated their capacity. The response is simpler: keep the upside. If teams believe they can collectively exceed the parent target, the parent plan can be adjusted upward, or the excess can be treated as a buffer that provides protection if one team underperforms.
The reconciliation conversation should take 30 minutes or less. It’s not a planning session — it’s a gap negotiation. The data is already in Profit.co: the parent target, the aggregated children’s plans, and the gap. The conversation is about what to do with the gap, not about debating the numbers.
Handling Re-Distribution Mid-Quarter
Top-down distribution doesn’t happen only at the start of the quarter. When a parent plan is modified mid-quarter, the modification may need to cascade to children. The propagation rules determine how this happens:
| Propagation Rule | What Happens on Parent Plan Modification | Team Autonomy Impact |
|---|---|---|
| Auto-cascade | Children’s plans are automatically adjusted proportionally. Owners are notified after the fact. | Low autonomy. Fast alignment. Best for urgent changes where speed matters more than team input. |
| Review-required | Children’s owners receive a notification with the proposed changes. They must accept, modify, or reject within 48 hours. | Medium autonomy. Balanced approach. The default recommendation for most organizations. |
| Lock-down | Children’s plans are not affected. The parent plan changes independently. | Full autonomy. No cascade. Best for mature teams managing their own plans or when child plans are intentionally decoupled. |
The review-required rule is the sweet spot for most organizations. It preserves team autonomy (owners can modify the cascaded change) while ensuring alignment (changes are communicated and acknowledged). The 48-hour review window is short enough to maintain the 72-Hour Rule discipline.
What the Review Notification Looks Like
When a parent plan is modified with review-required propagation, each child owner receives a notification that includes: the parent KR name and the change that was made, the proposed impact on their child plan (specific periods and values), the rationale from the parent’s check-in notes, and three action buttons: Accept (applies the proposed changes as-is), Modify (opens Modify Plan with the proposed values pre-loaded for adjustment), or Reject (keeps the current child plan unchanged and notifies the parent owner of the rejection).
Accept is the most common response (approximately 70% of the time). Modify accounts for about 25% — the team accepts the direction but adjusts the specifics. Reject is rare (under 5%) and signals a fundamental disagreement that requires a direct conversation.
Five Anti-Patterns to Avoid
| Anti-Pattern | What It Looks Like | The Fix |
|---|---|---|
| Distribute and disappear | Leadership distributes plans but never checks the aggregated bottom-up view. Teams refine their plans, but no one reconciles the gap. | Schedule the reconciliation conversation for day 12–14 of the quarter. It’s a 30-minute meeting that closes the loop. |
| Distribute without a refine window | Plans are distributed and treated as final. Teams don’t review or modify. The distributed plan becomes a mandate. | Explicitly communicate the refine window: “You have 10 days to review and adjust. The distributed plan is a starting point.” |
| Over-allocate to avoid difficult conversations | The parent allocates 110% of the target across children, hoping everyone will hit 90% and it’ll work out. This avoids the negotiation but ensures every team is set up to miss. | Allocate 100% of the target. If you want a buffer, reduce each team’s allocation by 5% and hold the 5% as a central reserve. |
| Distribute weekly plans to monthly teams | A parent with weekly check-ins distributes to children who check in monthly, but doesn’t account for the frequency mismatch. | Configure Profit.co to aggregate weekly parent values into monthly child plans automatically. Review the aggregation to ensure it makes sense. |
| Cascade every modification automatically | Auto-cascade is set for all parent-child relationships, so every minor parent plan adjustment ripples to every child plan without review. | Use auto-cascade only for urgent, time-sensitive changes. Default to review-required for routine modifications. This gives teams a chance to adapt the cascade to their local context. |
The Distribution Playbook: Quarter-Start Workflow
Here’s the complete workflow for top-down distribution at the start of a quarter, from plan creation to locked-in operating plan:
| Day | Action | Who |
|---|---|---|
| Day 1–3 | Leadership sets parent-level plans (company and department KRs). Uses AI import from strategic planning spreadsheets or natural language commands. | VPs, Directors |
| Day 3–4 | Distribute to Children for each parent KR. Choose allocation method (weighted is most common). Send notifications to child owners. | Directors, Department leads |
| Day 4–13 | Refine window. Child KR owners review distributed plans, modify based on local knowledge, import operational data. Flag irreconcilable gaps to parent. | Team leads, KR owners |
| Day 12–14 | Reconciliation meeting. Parent owners review aggregated bottom-up plans. Negotiate gaps. Adjust parent targets if needed. Re-cascade if significant changes. | VPs, Directors, Team leads |
| Day 14 | Operating plan locked. All plans — parent and child — are confirmed in Profit.co. The distributed-then-refined plans become the system of record. | All |
| Day 15+ | Normal check-in rhythm begins. Plans are now subject to the 72-Hour Rule for signal-triggered modifications. Propagation rules govern any mid-quarter cascades. | All |
The entire distribution-to-lock-in process takes 14 days. Compare this to traditional bottom-up planning, which often takes 4–6 weeks because every team builds from scratch. Top-down distribution with a refine window gets you to a better operating plan in a third of the time.
When Top-Down Distribution Is the Wrong Choice
Top-down distribution works best when leadership has a clear view of the target and a reasonable hypothesis about the distribution shape. There are situations where it’s the wrong starting point:
-
Exploratory KRs: When the team is exploring a new market, testing a new channel, or running an experiment, the leadership team may not have enough information to set a meaningful distribution. In these cases, bottom-up planning is more honest: let the team set their own plan based on their hypothesis and aggregate it upward.
-
Teams with high planning maturity: If a team already has sophisticated planning capability (pipeline models, sprint velocity data, campaign forecasts), distributing a top-down plan over their existing model creates friction without adding value. Let them import their own plan and aggregate upward.
-
Cross-functional KRs with no clear owner: When a KR’s child plans span multiple departments (e.g., a revenue KR with contributions from Sales, Marketing, and Partnerships), top-down distribution from a single parent may not reflect the cross-functional dynamics. Use a facilitated bottom-up approach instead, where each contributing team plans independently and the parent aggregates.
In all these cases, the alternative is bottom-up planning with aggregation — covered in our companion article. The two approaches are complementary: use top-down distribution where leadership has strong signal, and bottom-up aggregation where teams have stronger signal.
Distribution Is a Conversation, Not a Broadcast
The most important shift in thinking about top-down distribution is this: you’re not broadcasting a plan. You’re starting a conversation. The parent plan says: “Here’s what we think the quarter looks like from up here.” The refine window says: “Now tell us what it looks like from down there.” The reconciliation meeting says: “Let’s close the gap between those two views.”
Organizations that treat distribution as a broadcast get compliance but not commitment. Organizations that treat it as a conversation get both.
Top-down distribution gives every team a plan on day one. The refine window gives every team ownership of that plan by day fourteen. Together, they solve the alignment-autonomy tension: aligned by construction, autonomous by design.
Distribute plans in minutes. Refine them in days. Align in two weeks.
Profit.co’s top-down distribution cascades plans through your hierarchy with configurable allocation methods and propagation rules. Teams refine with AI-powered tools. The operating plan is ready in 14 days. Start your free trial.