Multi-team OKRs become a wishlist when a director cascades every objective downward and every team's key results just restate its existing roadmap with new labels. The fix: own only the two or three objectives that force a real cross-team tradeoff, and let each team author its own key results — they control the mechanism.
Quick answer: Cascade objectives sparingly — most
OKRs should originate with the team, not descend from the director. Own the objectives that require a genuine cross-team tradeoff; let each team write its own key results, because only the team knows which lever actually moves.
Why Cascaded OKRs Collapse Into a Wishlist
Cascaded OKRs collapse into a wishlist when alignment gets redefined as every team restating the director's objective in different words, then filling in key results that were already sitting on the roadmap. Nothing gets prioritized or traded off — the exercise produces compliance, not commitment, and by quarter's end nobody can say what actually changed.
Andy Grove built the original OKR system at Intel around a simple filter: an objective should capture "the vital few, not the trivial many." John Doerr's Measure What Matters keeps returning to that line because directors keep forgetting it. A cascade rate of 100% guarantees the opposite outcome — a focusing tool turns into an org chart with due dates attached.
The symptoms are recognizable once you know what to look for:
- Key results that are really tasks. "Ship the new onboarding flow" scored as a
KRisn't an outcome; it's a deliverable wearing an outcome's clothes. - Identical KRs wearing different team names. Five teams each own "increase activation," and none of them can name the specific lever that's theirs to pull.
- No tension anywhere. A real key result trades something off — speed for reliability, breadth for depth. A copied one never has to.
- A scorecard nobody reads. Once
OKRs stop reflecting a live decision, they become a quarterly form that gets filled in and filed away.
Christina Wodtke's Radical Focus proposes a rough discipline for the cascade itself: roughly a third of a team's objectives should come from above, and the rest should originate with the team closest to the problem. That ratio isn't a law of physics, but it's a useful gut-check — if a director's group is closer to 100% top-down, ownership has already left the building, whatever the document says.
This tension — deciding what a director should coordinate versus what belongs to the teams — runs through most of the job at this level, not just goal-setting. The complete guide to the director of product role covers how it shows up in hiring, roadmap arbitration, and stakeholder management as well.
Top-Down Mandate vs. Negotiated Alignment
A top-down mandate hands each team pre-written key results and calls the result alignment. Negotiated alignment hands each team a shared objective and a deadline to propose its own key results, which the director then pressure-tests before sign-off. The second approach takes longer to publish, but it holds up better in April, because the team that writes a commitment is the team that defends it.
The difference shows up across almost every dimension of how the goal actually gets used, not just how it gets written:
| Dimension | Top-Down Mandate | Negotiated Alignment |
|---|---|---|
| Who drafts the key results | Director or director's staff | Team, proposed then negotiated with the director |
| Time to publish | Fast — a few days | Slower — one to two weeks of back-and-forth |
| Ownership in practice | Nominal; team executes someone else's plan | Real; team defends a number it chose |
| Risk-taking behavior | Teams pad or sandbag to avoid missing a number they didn't set | Teams stretch, because the target is theirs to be proud of |
| Typical failure mode | Wishlist / compliance theater | Slower quarter-start; needs director judgment to referee |
| Best used for | Crisis mandates, compliance deadlines, hard pivots | Normal quarterly and annual planning |
Google's internal OKR guidance, documented in its public re:Work materials, grades objectives on a 0 to 1.0 scale and treats a consistent 1.0 across the board as a warning sign, not a success — usually evidence the goal was set low enough to guarantee a win. That behavior is a predictable response to a mandate: if you didn't choose the number, protecting yourself from missing it becomes the rational move. Negotiated targets don't eliminate sandbagging, but they remove the main incentive for it.
None of this means top-down mandates are always wrong. A regulatory deadline, a security incident, or a genuine pivot are moments when a director should simply state the objective and the constraint, and skip the negotiation. The mistake is defaulting to mandate every quarter because negotiation feels slower — it is slower, and that's the cost of the ownership you're buying.
The Ownership Rule: What the Director Owns, What Teams Author
A director should own an objective only when hitting it requires a tradeoff that no single team can make alone — shared infrastructure, a budget ceiling, a sequencing call across roadmaps. Everything else, including how to hit a shared objective, belongs to the team that controls the mechanism. The director's job there is to negotiate the key results, not supply them.
A simple test separates the two cases:
| Signal | Director should own the objective | Team should author it |
|---|---|---|
| Depends on more than one team's roadmap moving together | Yes | No |
| Requires a spend or headcount tradeoff across teams | Yes | No |
| A single team already controls the system or journey moving the metric | No | Yes |
| Success depends on domain judgment only that team has | No | Yes |
| The number is a rollup of team-level metrics with no shared dependency | No | Yes |
This maps closely onto team boundaries themselves. Matthew Skelton and Manuel Pais's Team Topologies argues that a team's remit should track its actual cognitive load and its ownership of a value stream, not an org chart convenience drawn two reorgs ago. When a key result gets assigned to a team that doesn't control the relevant system, you've manufactured a fake owner — no matter how clean the OKR document looks.
Drawing goal boundaries and team boundaries together, rather than as two separate exercises, is covered in more depth in this guide to product org design and team boundaries.
This rule also assumes something that's easy to skip past: team-level PMs you actually trust to write a good key result unsupervised. That's a hiring bar as much as a process one — a PM who can't defend a tradeoff in the room will either over-ask the director for direction or under-commit to protect themselves. What that judgment looks like in an interview, rather than just a résumé, is the subject of interviewing for judgment when hiring PMs.
A Worked Example: One Group Objective, Five Independent Key Result Sets
A group objective survives contact with five teams when the director owns the objective's framing and the cross-team tradeoff it implies, while each team writes key results that reflect a genuinely different lever. The test of a healthy set: no two teams' key results could be swapped without changing what either team actually has to do.
Take a director running five teams — Onboarding, Core Workflow, Integrations, Billing & Packaging, and Platform & Reliability — around a churn problem showing up at renewal time for mid-market accounts. The wishlist version of this objective is "Reduce churn by improving the product," scored by five near-identical KRs about activation or retention. The negotiated version starts narrower:
Group objective (director-owned): Make the renewal decision a non-event for mid-market customers — not a re-sale.
Framing the objective around the underlying job the customer is trying to get done — renew without re-litigating the original purchase — rather than a lagging metric like "reduce churn," is what keeps five teams from all reaching for the same lever. The complete guide to Jobs to Be Done goes deeper on why objective framing built around a customer's job holds up better across a group than one built around a single company metric.
Each team then proposes a key result tied to the specific point in the renewal journey it actually controls:
| Team | Key result (team-authored) | Lever it actually controls |
|---|---|---|
| Onboarding | Raise the share of renewing accounts that reach their second core-workflow milestone before month three | Depth of early activation |
| Core Workflow | Cut support tickets tied to the top three workflow gaps flagged in renewal-risk reviews | Workflow completeness |
| Integrations | Increase the share of accounts with at least one active data integration live before renewal date | Switching cost and stickiness |
| Billing & Packaging | Reduce the number of manual pricing exceptions negotiated at renewal | Packaging and pricing clarity |
| Platform & Reliability | Hold P1 incidents affecting renewal-quarter accounts at zero | Reliability and trust |
None of these five key results is a copy of the others with a team name swapped in, and none of them is "reduce churn by N points" repeated five times — that would be a wishlist wearing a nicer format. Each ladders up to the group objective through a distinct causal path.
Mapping which moment in the renewal journey — and which dip in customer confidence — each team's work actually touches is what makes assigning a distinct key result possible in the first place. The complete guide to the customer journey walks through building that map before a group's next OKR cycle starts.
The director's real work in this example isn't drafting five key results. It's checking whether the five together cover the causal path from current state to the objective without gaps or overlaps — coverage, not authorship, is the director's contribution.
Running Alignment as a Conversation, Not a Spreadsheet Rollup
Alignment across five teams holds up when it's maintained through a recurring, structured conversation — a quarterly negotiation and a monthly or biweekly check-in — rather than a form that gets filled in once and forgotten until the next cycle. A spreadsheet can hold the record of what was agreed; it cannot detect that two teams have quietly started working at cross-purposes.
The mechanics of that recurring conversation belong to the broader rhythm a director runs across a group — the same cadence that governs 1:1s, roadmap reviews, and stakeholder updates. Director operating cadence and rhythms covers how quarterly OKR negotiation fits alongside those other rituals rather than competing with them for calendar space.
One reason these conversations degrade into a rollup in practice: nobody actually agrees on what "done" means for the deliverable a key result depends on. One team's "shipped" is another team's "in beta behind a flag."
Prodinja's Spec Studio addresses that narrower, unglamorous problem directly — its readiness gates give every team a shared, visible definition of "done enough" for a spec before it's considered hand-off ready. A key result tied to "ship the integration" then points at the same finish line for the director and the team, instead of two different vanity milestones dressed up as one.
Two habits keep the conversation from sliding back into a rollup over time:
- Check health, not just status. A monthly check-in should ask whether the key result is still the right bet given what's been learned, not just what percentage complete it is.
- Renegotiate in the open. When a team's key result needs to change mid-quarter, that's a five-minute conversation with the director and affected peers — not a silent edit to the tracker.
Key Takeaways
- Cascade objectives sparingly, not key results at all. A director's group objective should set direction; the how belongs to the team closest to the mechanism.
- Use a rough one-third test. Christina Wodtke's guidance from Radical Focus — roughly a third of a team's goals coming from above — is a useful gut-check for whether a group has slid into pure top-down mandate.
- Own only genuine cross-team tradeoffs. If a single team already controls the lever, the director's role is to negotiate the target, not to write it.
- Let team boundaries set goal boundaries. Assigning a key result to a team that doesn't control the underlying system creates ownership in name only.
- Grade for stretch, not for a clean scorecard. A row of perfect scores across five teams is more often evidence of sandbagging than of a strong quarter.
- Frame the shared objective around a customer job, not a lagging metric. It's what keeps five teams from reaching for the same lever and producing duplicate key results.
- Treat quarterly OKR-setting as a negotiation with a deadline, not a data-entry exercise. The extra week it takes is the cost of real ownership.
Frequently Asked Questions
How many OKRs should cascade down to each team?
Aim for roughly a third of a team's objectives originating from the director's group objective, with the rest generated by the team itself — a discipline popularized by Christina Wodtke in Radical Focus. If nearly all of a team's goals trace back to a directive rather than the team's own read of its problem, alignment has tipped into mandate, whatever the meeting agenda calls it.
What's the difference between a group-level OKR and a team-level OKR?
A group-level objective should name a cross-team tradeoff or shared outcome that no single team can resolve alone — budget, sequencing, or shared infrastructure. A team-level OKR is the team's own bet on how to move that outcome, authored and defended by the people who control the mechanism, not handed down pre-written.
Should a director ever assign a team its key results directly?
Rarely, and only in specific conditions: a genuine crisis, a compliance deadline with no room to negotiate, or a brand-new team that hasn't yet built the context to author its own commitments. Outside those cases, an assigned key result usually signals that the director doesn't trust the team's judgment enough to negotiate with it — worth naming directly rather than quietly working around.
How often should multi-team OKRs be reviewed?
At minimum, monthly, with a lighter pulse check biweekly if the group is navigating something volatile. The quarterly moment is for setting and negotiating the goals; the monthly and biweekly moments are for catching drift, renegotiating a key result that's stopped making sense, and keeping the goals a live conversation rather than a document nobody revisits until the next quarter.
Is it a problem if teams don't hit 100% of their OKRs?
No — and a group that consistently hits 100% across every team is usually the bigger problem. Google's own internal grading practice treats a KR scored a perfect 1.0 as more often evidence the target was set too low than evidence of a great quarter; a healthy range signals a stretch that was taken seriously, not a guarantee that was quietly banked in advance.