One Key Result, One Objective: Why Shared Key Results Cause Finger-Pointing
Two Objectives land on the planning board and someone notices they both touch the same number. Objective A wants to grow revenue from existing accounts. Objective B wants to improve customer satisfaction. Both would benefit from a lower churn rate, so someone suggests reusing "Reduce churn from 8% to 5%" as a Key Result under both Objectives. It feels efficient. Nobody has to write a second metric, and the two teams already talk to each other. This is one of the most common shortcuts teams take when setting OKRs, and it almost always causes problems by the middle of the quarter.
Why Sharing a Key Result Feels Reasonable at First
A single number rarely serves only one purpose. Churn affects revenue, satisfaction, referrals, and support load all at once. So when two Objectives sit close together, it's natural to think one Key Result can represent progress for both. Writing it twice feels redundant, and tracking it once seems like the tidier solution. The problem isn't the instinct, it's what happens once real work starts.
The Ownership Problem
A Key Result needs a single owner, someone accountable for moving the number and reporting on it during check-ins. When one Key Result sits under two Objectives, it usually ends up with two owners, one per team, or worse, no clear owner at all because each team assumes the other is driving it. When churn doesn't move, the retention team points to marketing's onboarding emails, and the customer success team points to product's missing features. Nobody update the check-in because nobody is sure whose job it is. The accountability structure John Doerr describes in "Measure What Matters" depends on a clear line from Key Result to owner. Sharing a Key Result across Objectives breaks that line before the quarter even starts.
The Evaluation Problem
At the end of the cycle, every Objective gets scored based on how its Key Results performed. If churn drops from 8% to 6%, was that a win for Objective A, a partial win for Objective B, or neither because the target was 5%? A shared Key Result forces this same number to answer two different questions at once, and it usually answers neither one clearly. Scoring becomes a negotiation instead of a read of the data, which defeats the point of using a measurable Key Result in the first place.
The Real Signal: Your Objectives Probably Overlap
When a single Key Result genuinely fits two Objectives equally well, that's usually not a coincidence, it's a sign the two Objectives are describing the same underlying goal from two different angles. Objective A, "grow revenue from existing accounts," and Objective B, "improve customer satisfaction," might both really be about the same thing: keeping customers around and getting more value from them. When the metric that matters most is identical, the honest fix is often to merge the two Objectives into one, rather than splitting the workaround across two Key Results.
A Worked Example
A software organization had "Increase expansion revenue" under sales and "Improve product stickiness" under product, both pointing at the same Key Result: "Reduce churn from 8% to 5% by end of quarter." Neither team updated it reliably, and at review time both teams claimed partial credit while nobody could say what actually drove the change. The team resolved it two ways at once. First, they split the Key Result: sales kept "Increase expansion revenue from existing accounts from $40K to $65K per month," owned by the account management lead, while product kept "Reduce churn from 8% to 5% by improving onboarding completion," owned by the product manager. Second, they noticed that a third Objective, "Improve customer satisfaction," was really just a restatement of the product Objective and folded the two together. What had been three overlapping Objectives with one shared metric became two distinct Objectives, each with its own Key Results and a single accountable owner.
How to Catch This Before It Happens
When drafting Key Results, ask a simple question for each one: if this number doesn't move, whose job did not get done? If the honest answer names two different people or two different teams, the Key Result needs to be split, with each half rewritten to reflect what that specific owner actually controls. If splitting it feels artificial, because the two halves would just be duplicates of each other, that's the signal that the Objectives themselves overlap and should be merged instead. Either path is better than leaving one Key Result serving two masters.
A Rule of Thumb
Every Key Result should have exactly one home and one clear owner. If a metric seems to belong to two Objectives, either write two distinct Key Results, each scoped to what that owner controls, or recognize that the Objectives overlap and combine them. Google's guide to setting OKRs stresses that Key Results should be owned and updated by the people closest to the work, and that only works when each one has a single, unambiguous home.