OKR examples for every team

The OKR template

**Objective:** Where you want to be, in one qualitative line

- **KR1:** Metric from {baseline} to {target}
- **KR2:** Metric from {baseline} to {target}
- **KR3:** Metric from {baseline} to {target}

**Initiatives:** the work you'll do to move the key results
**Owner:**
**Period:** Q_ 20__
**Check-in:** weekly, score 0.0–1.0

OKR examples by team

How to write good OKRs (and what makes good OKR examples)

• Objectives are qualitative

  The objective says where you want to be and why it matters, in words the team would repeat. “Customers get help fast and leave happy” works. “Increase CSAT by 8 points” is a key result wearing the wrong label.

• Key results are outcomes, not tasks

  If you can tick it off a to-do list, it's an initiative. “Launch help center” is work. “Tickets resolved by help center articles from 5% to 20%” is the result that work should cause.

• Every key result has a baseline and a target

  “From 14 hours to 2 hours” shows the size of the ambition and makes progress easy to score. If you don't know the baseline yet, write {current} and measuring it becomes week one's job.

• Ambitious, not impossible

  Set targets you'd be proud to hit 70% of. If the team hits every key result, the targets were too safe. If it hits none, they were fiction.

• Fewer is better

  One to three objectives per team, each with three to five key results at most. Ten OKRs means no priorities.

• Review them weekly

  OKRs set in January and opened in March don't change anything. A five-minute weekly check-in with a confidence score keeps them in the work.

You are an experienced OKR coach. Turn the goals or strategy notes below into OKRs.

Rules:
- Write 1–3 OKRs, one per distinct goal area. Merge related goals. Never add goals the notes don't mention.
- Objective: one short, qualitative line that says where the team wants to be and why it matters. No numbers, no metric names, and never a launch or deliverable ("Launch the app" is a task, "Customers can run their day from their phone" is an objective).
- Key results: 2–4 per objective. Each is a measurable outcome in the form "Metric: from {baseline} to {target}".
- Use only numbers that appear in the notes. For any missing baseline or target, write {current} or {target}. Never invent numbers.
- Key results measure outcomes, not tasks. When the notes list work ("ship X", "launch Y", "hire Z", "get certified"), list it under "Initiatives" and make sure at least one key result measures the change that work should cause (e.g. "launch help center" → "Tickets resolved by help center articles"). Only list initiatives the notes mention, in their words.
- End with a "**Watch out**" section. Add a line only for a goal in the notes that was a task rather than an outcome, or too vague to measure: quote it, name the problem in a few words, and say which key result now measures it. Leave the section out if nothing needs flagging.
- Plain, specific language. No buzzwords ("synergy", "world-class", "leverage", "best-in-class"). No "we".

Format each OKR as a bold "**Objective:**" line, the key results as bullets, then an "*Initiatives:*" line if any. Return only the OKRs in markdown. No other text.

Use it where you work

• In a Notion or Google Docs planning doc

  Select the bullet list of goals in your quarterly plan, run the snippet, and the list becomes OKRs in place. The {current} gaps show which baselines to pull before the planning meeting.

• From a Slack message from leadership

  Copy the CEO's “priorities for the half” message and get a first draft of team OKRs that trace back to it, ready to share in the thread.

• In Lattice or Workboard

  Draft the objective and key results before you open the goal form, then paste each line into its field instead of writing them from scratch.

• Meeting agenda generator

  Before the meeting, paste a Slack thread, a list of topics or an invite, and get a focused agenda. After it, paste your notes and get decisions and action items.

• Performance review phrases

  Paste your rough notes about someone's year, or your own, and get review text that is specific, fair and ready to submit.

• User story template

  Copy the user story template below, or paste a feature idea, a Slack thread or customer feedback and get stories with acceptance criteria your team can estimate.