OKR Planning

Define objectives and key results for your cycle

Planning Your OKRs

Planning is the phase where you define what you want to achieve (objectives) and how you'll measure success (key results). Good planning sets the foundation for a successful cycle.

Start with your overall strategy and break it down into specific, measurable goals for the cycle.

How to Plan OKRs
1

Navigate to Planning View

Select your cycle and click "Plan" to open the planning interface

2

Create Objectives

Define 3-5 aspirational goals for the cycle

3

Add Key Results

For each objective, define 2-4 measurable key results

4

Set Targets

Define start value, target value, and current value for each key result

Review draft OKRs

New OKRs start as Draft. Review OKRs lets you walk through every draft one at a time and decide which ones are ready to become Active.

  1. 1. On the Plan page, click Review OKRs
  2. 2. Narrow the list with the team and cycle filters if you like
  3. 3. Read the objective, its key results and comments
  4. 4. Change the review status from Draft to Active and click Save
  5. 5. Use Previous OKR and Next OKR to move through the drafts, or Edit to change the OKR

Admins and Product Leaders can review OKRs. When there are no drafts, the page shows "No OKRs in Draft".

Writing Effective OKRs

Objectives Should Be:

  • • Qualitative and inspirational
  • • Clear and easy to understand
  • • Time-bound to the cycle
  • • Aligned with organization goals
  • • Actionable by your team

Key Results Should Be:

  • • Quantitative and measurable
  • • Specific with clear success criteria
  • • Ambitious but achievable (70-80% target)
  • • Outcome-focused, not activity-focused
  • • Limited to 2-4 per objective
Quality check for key results

When you add or edit a key result, the Quality check under the title grades it as you type. It gives a score out of 100 (Strong, Needs work or Weak) and four checks:

  • • Measurable: tracked as a number with a target, not as done/not done
  • • Baseline: has a start value to measure from
  • • Target: has a target value that differs from the start value
  • • Outcome, not output: does not lead with a task such as "Launch", "Build" or "We will roll out", and says what you are measuring: a direction ("Increase", "Reduce"), a threshold ("under 5 minutes", "above 50", "40%") or a metric such as churn, revenue or active users

The score comes from fixed rules, not AI, so it works for every plan. The outcome rule only looks at the wording, so a pass is a hint, not a guarantee. If your organization has given AI consent, click Check with AI for AI-assisted suggestions and alternative wordings, and click Use to apply one. The AI reading then decides the outcome check: if AI reads the title as an activity the check fails, and if it reads it as an outcome the check passes, until you change the title. AI suggestions are labelled AI-assisted and count towards your daily AI requests.

Example OKRs

Objective: Deliver exceptional user experience

KR1: Increase NPS score from 42 to 60

KR2: Reduce support tickets by 30% (from 500 to 350/month)

KR3: Achieve 90% user satisfaction rating

Objective: Grow our customer base significantly

KR1: Acquire 1,000 new customers (from 2,500 to 3,500)

KR2: Increase trial-to-paid conversion from 15% to 25%

KR3: Reduce customer acquisition cost by 20%

Common Pitfalls to Avoid
  • • Too many OKRs: Focus on 3-5 objectives maximum
  • • Vague key results: Avoid "improve" or "increase" without numbers
  • • Activities as key results: Focus on outcomes, not tasks
  • • Easy targets: OKRs should be ambitious (70-80% completion is success)
  • • Misalignment: Ensure OKRs align with team and organization goals
Next Steps

After planning your OKRs, start tracking progress with regular check-ins.