Child OKR: the team OKR that contributes to a higher-level goal

A Child OKR is an OKR (most often at team level) that explicitly contributes to a Parent OKR at a higher level. It''s the operational unit of the OKR cascade.

Definition

A Child OKR is the Objective of a team (or more rarely an individual) that contributes to a Parent OKR at a higher level. It embodies the commitment "here's how our team contributes to that company Objective".

The right framing: a child OKR expresses a contribution, not a subordination. The team isn't receiving an order from above; it's proposing how it puts itself in service of a larger stake. A good child OKR is almost always co-authored between the team and its management, not dictated.

A good child OKR isn't a copy of its parent. It inherits the strategic direction but translates it through the team's own words, Key Results, and Initiatives.

Full parent → child example

Parent OKR (company):

  • Objective: "Become the European benchmark for managing distributed teams."
  • KR 1: Move our Share of Voice on target queries from 8% to 20%.
  • KR 2: Sign 30 new scale-up customers.
  • KR 3: Reach an NPS of 60 on the installed base.

Child OKR (Customer Success team):

  • Objective: "Turn our existing customers into our best advocates."
  • KR 1: Move NPS on existing customers from 48 to 60 (contributes to company KR 3).
  • KR 2: Generate 12 publishable customer case studies (contributes to company KR 1).
  • KR 3: Move the referral share to 25% of inbound leads (contributes to company KR 2).

The CS team's child OKR serves multiple parent KRs without copying any of them. It describes the team's own contribution, with its own metrics and its own voice.

What a good Child OKR looks like

Three quality markers:

  • The team can present the child OKR without referring to its parent. If you have to read the parent to make sense of the child, the framing is off.
  • The Key Results are specific to what the team can move, not a copy of upstream metrics.
  • The Objective is qualitative and inspiring at the team level, not a watered-down version of the company line.

Common mistakes on Child OKRs

  • The child OKR copies its parent. Symptom: you can read both Objectives back-to-back without hearing a difference. Reframe from the team's point of view.
  • The child OKR serves too many parents. Symptom: the team can no longer make trade-offs. Pick a primary parent.
  • The child OKR has no identified parent. Symptom: nobody above feels concerned by whether it succeeds. Either find a parent, or pull it out of the cycle.
  • The child OKR is actually an Initiative. Symptom: it describes a project to ship, not an outcome to reach. Reframe as an outcome.

When to cascade down to the individual

Individual child OKRs aren't a good fit for everyone. They make sense in two cases: high-autonomy roles (lead engineer, design lead, solo growth practitioner) and transversal roles (chief of staff, OKR champion). For everyone else, the team OKR is enough and protects collective work.

Tie your Child OKRs to your strategy

A child OKR's quality is decided in the conversation between the team and its leadership. Let's talk about how we tool that dialogue.

Request a demo

Impact on the organization

The child OKR is the meeting point between company strategy and operational reality. Well-framed, it preserves team autonomy while guaranteeing its contribution to the collective. Poorly framed, it becomes either a copy that kills engagement, or a self-centered Objective that ignores the strategy.

Key takeways for Child OKR

  1. Team-level (or individual) OKR that rolls up to a higher-level Parent OKR.
  2. Inherits the strategic direction but frames its own Key Results and Initiatives.
  3. Should not be a copy of the parent: the test is being able to present it without quoting the parent.
  4. Reserved for individuals only on highly autonomous or transversal roles.

Curated related readings

Synonyms for Child OKR : Team okr; Sub-objective; Derived okr;

Share this definition