Parent OKR: the higher-level goal that team OKRs roll up to

Definition

A Parent OKR is the Objective that a lower-level OKR explicitly contributes to. Rather than thinking of it as an "OKR hierarchy", think of it as a contribution chain: each level brings its own piece to the higher-level ambition, in its own words and with its own metrics.

Saying an OKR has a parent means "what we're committing to achieve serves something at the level above us". The parent/child relationship makes that contribution traceable, but it's never a relationship of subordination.

The three forms of parentage, illustrated

Common parent OKR across the three examples: "Become the European benchmark for managing distributed teams."

Form	Mechanism	Team-side example
Objective reuse	The team reuses the parent Objective as-is and frames its own KRs.	Marketing team: "Become the European benchmark for managing distributed teams", with KRs on SOV, organic traffic, press mentions.
Promotion of a Key Result to Objective	A parent KR becomes the team's Objective, because it depends almost entirely on them.	Customer Success team: Objective "Reach an NPS of 60 on the installed base" (which is a KR of the parent), with its own KRs to get there.
Contribution by design	The team frames its own Objective that serves the parent Objective without copying it.	Product team: "Ship a 1:1 experience managers adopt within a week", which clearly serves the parent without quoting it.

The healthiest pattern is contribution by design. The other two work when getting started, or when a team is very tightly bound to the parent Objective.

See the cascading page for the methodological detail.

Can an OKR have multiple parents?

Yes, sparingly. An OKR serving two parent Objectives at once may make sense as a shared OKR (see alignment). Beyond two parents, the OKR loses clarity and becomes hard to arbitrate.

Watch out for over-documenting the parentage

OKR tools often encourage rigorously documenting every parent/child relationship, sometimes across several levels. The risk is real: confusing contribution traceability with administrative traceability. Three signs of toxic over-documentation:

Managers spend more time updating parent/child links in the tool than talking about Objectives in team meetings.
The parent/child map is documented to 100%, but no team can explain its contribution without checking the tool.
OKR planning includes a "parent/child relationship cleanup phase" that lasts longer than the conversation about the meaning of the Objectives themselves.

Practical rule: documenting one parent per child, in one line, is enough. If the contribution chain isn't obvious from that, clarify the framing rather than adding more documentation.

Good practices for parent/child relationships

Practice	Why
Explicitly document the parent of every child OKR.	Undocumented alignment only exists in the head of whoever thought of it.
Validate the relationship in a conversation with the parent's owner.	Prevents self-declared contributions without buy-in from the level above.
Cap at one parent by default, two maximum for shared OKRs.	Preserves the readability of the contribution chain.
Revisit the parentage at every new cycle.	A parent OKR can evolve or disappear between two cycles.

Get parent/child relationships right

If your teams struggle to see how their work serves the strategy, the parent/child chain is usually implicit. Let's talk about making it explicit and alive.

Impact on the organization

The parent/child relationship makes alignment traceable and lets every team connect its work to the strategy. Without it, team OKRs become a list of well-meaning intentions disconnected from the company level.

Key takeways for Parent OKR

Higher-level OKR that a child OKR explicitly contributes to.
Three parentage patterns: Objective parent, Key Result parent, or contribution by design.
One parent by default, two only for shared OKRs.
The relationship must be documented and validated in conversation, not self-declared.

Curated related readings

Synonyms for Parent OKR : Higher-level okr; Parent goal; Upstream okr;