OKR guide

    Top down vs bottom up OKRs: which works better?

    Neither extreme works: leadership sets a few company objectives and the why, teams propose their own key results and initiatives, and the two meet in a short negotiation. The healthy pattern blends clear direction with the judgement of the people closest to the work.

    By Reuben Chircop, OKR specialist and leadership coach

    Top down OKRs

    In a top down approach, leadership writes the objectives and key results, then assigns them to teams. The direction is clear and the organisation can move quickly without waiting for every team to propose a plan.

    That can help in a crisis, when a new strategy needs a decisive start, or in a small company where leadership is close enough to the work to understand the constraints. It gives teams an immediate priority when uncertainty would otherwise leave them pulling in different directions.

    The problem begins when direction becomes prescription. Teams copy leadership key results into their own documents, even when they cannot directly influence those measures. There is a neat hierarchy of numbers, but no clear account of what each team will actually contribute.

    Ownership then means accepting an instruction rather than making a commitment. Sandbagging, where people negotiate an easy target, is replaced by compliance: people agree to the number because arguing feels pointless. The target looks ambitious, but the honest conversation about capacity and risk never happens.

    Bottom up OKRs

    In a bottom up approach, teams propose objectives and key results from their knowledge of customers, systems and day-to-day work. Leadership reviews those proposals rather than starting with a prescribed set.

    This helps when teams are mature, understand the strategy and can make sound trade-offs. They often see opportunities and constraints that a company-level view misses. Writing their own measures also makes it easier to explain why the work matters and to change initiatives when evidence changes.

    Without clear company direction, however, each team can optimise its own corner. One team might prioritise faster delivery while another adds checks that slow the same process. Both can make progress locally without improving the outcome the company needs.

    Another risk is too many objectives. If every worthwhile idea becomes an OKR, the organisation has a collection of local wish lists rather than a strategy. Bottom up input needs boundaries: shared priorities, limited capacity and permission to leave good ideas out of this cycle.

    Top down, bottom up and the blend at a glance

    AspectTop downBottom upThe blend
    Who writes objectivesLeadership writes and assigns themTeams propose their ownLeadership sets company direction; teams define their contribution
    Who writes key resultsLeadership prescribes the measuresTeams choose the measuresTeams propose measures; both sides negotiate commitments
    AlignmentClear on paper, sometimes weak in practiceDepends on shared strategic contextExplicit links and trade-offs agreed together
    OwnershipCan become acceptance of instructionsStrong local ownershipTeam ownership within shared priorities
    SpeedQuick to issue, slower if teams cannot deliverQuick to draft locally, slower to reconcileA prepared draft and one alignment conversation
    Main riskCompliance replaces honest judgementLocal optimisation replaces company progressNegotiation drifts without a decision maker

    How the blend works in practice

    Leadership owns the company direction. Teams own a proposal for their contribution. Neither draft is final until the two have checked the assumptions together.

    1. Leadership shares two to three company objectives and the context. Explain the why, the choices behind the strategy and the constraints. Teams need to know what matters and what is deliberately not a priority. Share draft company key results as something to discuss, not a finished list to cascade.
    2. Teams draft their own key results and initiatives. Ask what change the team can contribute, how it will measure that change and what work it thinks will move the measures. Keep initiatives separate from results so the team can change its approach without moving the goalposts.
    3. Hold one alignment conversation per team. Discuss what we will contribute and what we will not. Check capacity, dependencies and competing demands. Resolve overlaps with other teams and record the trade-offs, rather than adding another objective to keep everyone happy.
    4. Leadership adjusts company key results. Use what teams can commit to as evidence. If the combined contributions do not support the company target, revisit capacity, scope or the target itself. Do not quietly turn a strategic ambition into a promise nobody can keep.
    5. Agree the check-in rhythm. Name the outcome owners, decide when numbers and confidence will be updated, and put reviews in calendars. Use check-ins to surface learning and blockers, not to score individuals on attainment.

    As a rule of thumb, aim for roughly 60% of team key results to be proposed by the team itself. This is not a statistic or a quota. It is a prompt to check whether teams have real room to shape the plan. The right balance depends on the situation; the important thing is that contributions are discussed rather than simply assigned.

    Signs your balance is off

    These signs are starting points for a conversation, not proof of one cause. Ask the teams what is happening before deciding how to fix it.

    SignLikely causeFix
    Every team key result is a copy of a company oneCascading has replaced team judgementAsk each team for the specific contribution it can influence and measure
    Teams have objectives nobody above them recognisesThe strategy is unclear or alignment was skippedShare the company context and agree which outcomes belong in this cycle
    Planning takes more than three weeksToo many approval rounds or unresolved prioritiesReduce the objective list and name a decision maker for the remaining trade-offs
    Key results are all safe targetsTeams fear missing a target or being judged on attainmentSeparate learning from individual evaluation and negotiate credible stretch openly

    FAQ

    No. Use team OKRs where there is a meaningful change to achieve and the team can influence the outcome. A team keeping a stable service running may be better served by KPIs and a clear operating plan. Do not invent objectives just to make every team fill in the same document.

    Start with two to three company objectives. They should describe the few changes that matter most, not every responsibility in the organisation. If teams cannot remember them or explain why they matter, narrow the list before asking for team drafts.

    Ask the team to explain the contribution, rather than forcing an identical metric. A team key result can support a company objective without copying a company key result. If there is no credible connection, decide whether it is essential operating work, a missing company priority, or work to defer. Make that decision together and record the reasoning.

    Name one accountable owner for the shared outcome, with a contributor from each team involved. That owner keeps the check-ins and dependency decisions moving; they do not take over everyone else's work. Agree each team's contribution and name the person who can resolve a conflict over capacity or priorities.

    Aim to agree the team contribution in one short conversation, with preparation shared beforehand and a clear decision maker present. Allow a follow-up for a genuine dependency, not repeated approval rounds. If quarterly alignment runs beyond three weeks, examine unclear strategy, too many objectives or unresolved decisions rather than adding more meetings. Annual strategy planning is a separate process.

    If drafting the first version is the slow part, the free OKR generator from OKRgen drafts one objective with three key results as a starting point for the team conversation.