How to set up top-down distribution, enable bottom-up aggregation, configure propagation rules, and manage plan modifications across your entire OKR hierarchy.
Why Hierarchical Planning Matters
Every organization has a hierarchy. Whether it’s two levels deep or six, the way goals cascade from leadership to individual contributors determines whether strategy translates into execution or dissolves into disconnected activity. And yet, most OKR tools treat each Key Result’s plan as an isolated artifact — a flat table of dates and numbers with no awareness of the plans above or below it.
This creates a fundamental problem: when a VP modifies their quarterly target, the directors and managers beneath them have no idea. When a team realizes their ground-level plan is unrealistic and adjusts it, the department-level view doesn’t update. The hierarchy exists in the org chart, but not in the planning system.
Hierarchical adaptive planning solves this by treating plans as connected structures that flow in two directions: downward from leadership through trickle-down distribution, and upward from teams through bottom-up aggregation. When a plan changes at any level, the connected plans respond — either automatically or through a prompted review.
Adaptive planning is not about changing goals constantly. It’s about ensuring that the path to those goals reflects current reality at every level of the organization, updated as soon as the reality changes — not at the next quarterly review.
Two Directions of Plan Flow
Trickle-Down: Top-Down Plan Distribution
Top-down distribution begins with a leader defining a plan for a parent objective or Key Result. In Profit.co, this plan specifies how the target value is distributed across the planning period — weekly, bi-weekly, or monthly check-in intervals.
Once the parent plan is set, it can be distributed to child Key Results beneath it in the OKR hierarchy. Distribution doesn’t mean every child gets a carbon copy of the parent plan. Instead, Profit.co allocates proportional targets based on the child KR’s own From and To range and check-in frequency, preserving the distribution curve — the shape of the plan — while adapting the absolute values to each child’s context.
When to Use Top-Down Distribution
Clear organizational targets exist. The CEO or VP has committed to a number — revenue, NPS, adoption rate — and needs that commitment distributed across business units in a coordinated way.
Speed matters more than precision. At the start of a quarter, distributing a reasonable plan quickly and letting teams adjust later is often more effective than waiting for every team to build from scratch.
Alignment is the priority. In large organizations, ensuring every team’s plan sums to the organizational target is more important than individual accuracy. Top-down distribution guarantees this by design.
How It Works in Profit.co
Navigate to the parent KR and open Modify Plan.
Set the plan distribution — manually, via AI import, or using a natural language command like “linear growth from 0 to 100 across Q1.”
Click Distribute to Children. Profit.co identifies all child KRs in the hierarchy and calculates proportional plans for each, respecting their individual ranges and check-in frequencies.
Each child KR owner receives a notification that a distributed plan has been applied. They can review it, accept it, or modify it at their level.
Bottom-Up: Aggregated Planning
Bottom-up planning inverts the direction. Instead of leadership defining the plan and pushing it down, teams build their own plans based on ground-level knowledge — their actual capacity, their pipeline data, their understanding of what’s achievable given the engineers they have, the deals in motion, or the campaigns in flight.
Profit.co aggregates these team-level plans upward through the hierarchy, producing a real-time view at every parent level of what the organization is actually committing to. This aggregated view often differs from the top-down target — and that’s the point. The gap between what leadership expects and what teams are planning for is one of the most valuable signals in organizational alignment.
When to Use Bottom-Up Aggregation
Execution reality should drive targets. When the team closest to the work has significantly better information about what’s achievable, bottom-up planning produces more realistic targets.
You want early warning signals. If the aggregated bottom-up plans fall 20% short of the organizational target in week one, that’s an alignment conversation you want to have now — not at the end-of-quarter review.
Teams need ownership. Plans that teams build themselves carry more accountability than plans handed down from above.
How It Works in Profit.co
Child KR owners build their own plans using Modify Plan — manually, via AI import, or by pasting data from their operational spreadsheets.
Profit.co automatically aggregates child plans into the parent KR’s plan view. The parent shows a summed visualization of all child contributions.
If the aggregated total doesn’t match the parent’s target, Profit.co highlights the gap: “Aggregated plan: 82%. Target: 100%. Gap: 18%.”
The parent KR owner initiates a negotiation cycle — discussing with teams which plans can absorb more, or adjusting the parent target to reflect reality.
Combining Both Directions
In practice, most organizations use both modes in sequence. The most common pattern is what we call the “distribute-then-refine” cycle:
Leadership distributes a top-down plan at the start of the quarter. This sets the initial shape and ensures every team has a starting point on day one.
Teams review their distributed plans during the first two weeks. They modify based on ground-level knowledge — adjusting the curve, shifting targets between periods, or flagging unrealistic portions.
Modified child plans aggregate back up. Leadership sees the real-world version of their plan — what teams actually believe is achievable.
A reconciliation conversation happens. The gap between top-down and bottom-up gets negotiated. Maybe leadership adjusts the target. Maybe specific teams take on more. Maybe the plan shape changes.
The reconciled plan becomes the operating plan. From this point forward, any modification at any level triggers the appropriate notification and propagation.
The “distribute-then-refine” cycle typically completes within the first 10 days of a quarter. After that, the operating plan is realistic, aligned, and owned at every level.
Propagation Rules: Controlling What Cascades
Not every parent plan change should automatically ripple to every child. And not every child plan change should silently alter the parent’s aggregated view without someone being notified. Profit.co’s propagation rules give administrators control over how plan changes flow through the hierarchy.
Parent → Child Propagation
| Rule | Behavior | Best For |
|---|---|---|
| Auto-cascade | Child plans update automatically when the parent plan changes. Child owners are notified but don’t need to approve. | Fast-moving orgs where speed of alignment matters more than team-level autonomy. |
| Review-required | Child owners receive a review prompt when the parent plan changes. They must accept, modify, or reject the cascaded change. | Organizations that value team ownership and want changes acknowledged at every level. |
| Lock-down | Parent plan changes do not cascade. Child plans are independently managed. | Mature teams with high planning capability, or intentionally decoupled plans. |
Child → Parent Escalation
| Rule | Behavior | Best For |
|---|---|---|
| Silent aggregation | Parent’s aggregated view updates in real time. No notification unless gap exceeds threshold. | High-trust environments where minor adjustments are expected. |
| Threshold notification | Parent owner is notified when the aggregated total deviates by more than a configurable percentage (e.g., 10%). | Most common. Balances signal quality with noise reduction. |
| Approval required | Any child plan modification requires parent-level approval before the aggregated view updates. | Regulated industries or budget-sensitive contexts. |
Modifying Plans at Any Level
The real value of hierarchical adaptive planning shows up mid-quarter, when conditions change and plans need to respond. Profit.co ensures that plan modifications at any level are handled gracefully.
Scenario: A Team Modifies Its Plan
A product team realizes that a key dependency has slipped by three weeks. Their original plan front-loaded most of the target into month one, but now they need to shift effort into months two and three. The team lead opens Modify Plan, tells the AI assistant “move 30% of the January target into February and March equally,” and applies the change.
What happens next depends on the propagation rules. Under silent aggregation, the parent view updates immediately and the director sees the shift in their dashboard. Under threshold notification, if this team’s change pushes the department’s aggregate more than 10% from target, the director gets a notification. Under approval required, the change is held in a pending state until the director reviews it.
Scenario: Leadership Modifies the Parent Plan
A VP learns mid-quarter that the board has raised the annual revenue target. The Q2 plan needs to absorb an additional 15% of growth. The VP opens the company-level KR, edits the To target from 100M to 115M, and Profit.co’s reconciliation prompt immediately fires — because a customized plan already exists.
The VP chooses “Open Modify Plan,” adjusts the distribution curve to back-load the additional 15M into months two and three, and clicks Distribute to Children. Each department head receives a notification with their updated allocation and can either accept or negotiate.
Plan Integrity Across the Hierarchy
Hierarchical planning introduces a category of data integrity issues that flat plans don’t face. When plans are connected across levels, a change at one level can create mismatches at others. Profit.co addresses this with three safeguards:
Reconciliation prompts: When a KR’s From or To value is edited at any level, and a customized plan exists, the system blocks the user from proceeding without either opening Modify Plan to reconcile or resetting to auto distribution. This prevents the most common source of plan corruption.
Aggregation gap alerts: When the sum of child plans deviates from the parent target beyond a configurable threshold, the parent owner is alerted. The alert includes a breakdown showing which children are over-plan and which are under, enabling targeted conversations rather than blanket adjustments.
Change audit trail: Every plan modification is timestamped, attributed to a user, and recorded with before and after values. For hierarchical plans, the audit trail captures which propagation rule was in effect and whether the change was auto-cascaded, manually applied, or pending approval.
Getting Started: A Practical Setup Checklist
If you’re implementing hierarchical adaptive planning in Profit.co for the first time, here’s the recommended setup sequence:
Define your OKR hierarchy structure. Ensure parent-child relationships between objectives and KRs are correctly configured before setting up plans. The plan hierarchy follows the OKR hierarchy.
Choose your default propagation rules. Start with “review-required” for parent-to-child and “threshold notification at 10%” for child-to-parent. These are the most balanced defaults for organizations new to hierarchical planning.
Set the parent plan first. Use top-down distribution to give every team a starting point. Even a rough linear distribution on day one is better than waiting for bottom-up plans to trickle in.
Give teams a 10-day window to refine. Communicate that the distributed plan is a starting point, not a mandate. Teams should review, modify, and submit their refined plans within the first 10 days.
Hold a reconciliation meeting on day 12 to 14. Review the aggregated bottom-up plans against the top-down target. Negotiate gaps. Lock in the operating plan.
Enable AI import for teams with existing plans. Many teams will have plans in spreadsheets from their own processes. The AI import lets them bring that data in without manual re-entry.
Review propagation rules at the end of Q1. After one cycle, you’ll know whether your rules are too loose (too many unnoticed changes) or too tight (too many approval bottlenecks).
Ready to implement hierarchical adaptive planning?
Start a free trial at profit.co and set up your first trickle-down plan in under 5 minutes. Or schedule a demo to see hierarchical planning in action with your own OKR structure.