OKR guide

    OKR template: a simple format you can copy

    Most teams do not need an elaborate framework. One objective, two to four key results and a weekly check-in is all most teams need. Copy the template below, fill it in, then use the guidance to check it holds up.

    The template

    Objective: [a qualitative, inspiring outcome for this quarter]
    Why it matters now: [one sentence]
    Key result 1: [metric] from [baseline] to [target] by [date]
    Key result 2: [metric] from [baseline] to [target] by [date]
    Key result 3: [metric] from [baseline] to [target] by [date]
    Owner: [one person]
    Initiatives (bets, not commitments): [the work you think will move the key results]
    Weekly check-in: confidence per key result (on track / at risk / off track), what changed, what is blocking

    Example 1: a product team improving activation

    Objective:
    New customers reach their first real result in the product without needing help
    Why it matters now:
    Most trial users who never activate in their first week never come back.
    Key result 1:
    Share of new sign ups who complete setup within 7 days from 38% to 55% by 31 March
    Key result 2:
    Median time from sign up to first completed project from 4 days to 2 days by 31 March
    Key result 3:
    Onboarding support tickets per 100 new sign ups from 12 to 6 by 31 March
    Owner:
    The product manager for onboarding
    Initiatives (bets, not commitments):
    Shorten the setup flow, add a sample project, send a day two nudge email to users who stall
    Weekly check-in:
    Key result 1 on track, key result 2 at risk, key result 3 on track. The sample project shipped; the email is blocked on copy review.

    Example 2: a customer support team

    Objective:
    Customers get their problem solved the first time they contact us
    Why it matters now:
    Repeat contacts are filling the queue and slowing every other reply.
    Key result 1:
    First contact resolution rate from 62% to 75% by 30 June
    Key result 2:
    Share of tickets reopened within 7 days from 14% to 8% by 30 June
    Key result 3:
    Customer satisfaction score after a resolved ticket from 4.1 to 4.4 out of 5 by 30 June
    Owner:
    The support team lead
    Initiatives (bets, not commitments):
    Rewrite the ten most used reply templates, give agents refund authority up to a set limit, run a fortnightly review of reopened tickets
    Weekly check-in:
    Key result 1 at risk, key result 2 on track, key result 3 on track. Refund authority is approved; template rewrite is half done.

    The figures in both examples are illustrative, not taken from a real company.

    How to fill it in

    1. Start from the outcome. Write the objective as the change you want to see, not the work you plan to do. If it could be ticked off like a task, rewrite it.
    2. Pick metrics you can actually measure today. Choose key results you already have data for, or can get within a week. A metric you cannot see will not guide anyone.
    3. Set a baseline before a target. Find where each metric stands now before deciding where it should go. A target without a baseline is a guess.
    4. Keep initiatives separate from key results. List the work in the initiatives field. Key results describe the result, so you can change the plan without changing what success means.
    5. Agree the check-in rhythm. Decide when the team meets each week and who updates the numbers. Ten minutes on confidence, changes and blockers is enough.

    Common mistakes with OKR templates

    MistakeWhat it looks likeFix
    Task lists as key results"Launch the new help centre" written as a key resultMove the task to initiatives and measure what it should change, such as tickets per customer
    Too many objectivesSix objectives for one team in one quarterKeep one to three, and leave the rest as KPIs or next quarter's work
    No baseline"Increase retention to 80%" with no idea of today's figureMeasure the current level first and write it into the key result
    Key results nobody can measure"Improve team morale" with no survey or data sourceName the data source when you write the key result, or pick a metric you can track
    Filling the template once and never opening it againA tidy document in week one, untouched by week fourPut the weekly check-in in the calendar and update the template in that meeting

    FAQ

    Two to four is enough for most objectives. Fewer than two and you are usually measuring one narrow slice of the outcome. More than four and the team stops being able to hold them all in mind, so some quietly get ignored.

    Yes, but in their own field, kept apart from the key results. Initiatives are the work you think will move the numbers. Writing them down makes the plan visible, and keeping them separate means you can drop one that is not working without pretending the key result changed.

    A spreadsheet or a shared document is fine for one team and a handful of OKRs. It starts to strain when several teams need to see each other's key results, when you want a history of check-ins, or when nobody remembers where the latest version lives. Pick whatever your team will actually open every week.

    Update the key result numbers and confidence every week in a short check-in. Revisit the objective and the key results themselves at the end of the quarter, or sooner if the situation has clearly changed.

    Yes, for personal goals or for a role with a clear outcome to own. Keep it a planning and learning tool, though. Using OKR attainment to rate or reward individuals encourages safe targets and undermines the honesty the check-ins depend on. For a lighter format with examples, see personal OKRs. See how to keep OKRs and performance reviews apart.

    If the blank page is the hard part, the free OKR generator from OKRgen drafts one objective with three key results that you can paste into this template and adjust.