OKR — User Guide

Recommended roles:

• OKR Admin
• Configures cycles, permissions, and templates.
• OKR Owner
• Owns objectives and key results for a team or initiative.
• Contributor
• Updates check-ins, adds notes, supports progress.
• Viewer / Leadership
• Reviews dashboards and reports.

Best practice:

• Keep OKR editing limited to owners/admins. Keep check-ins open to contributors.

### 1) Define OKR cadence

• Choose cycle type:
• quarterly (recommended for strategic)
• monthly (recommended for operational)
• Set:
• start/end dates
• check-in frequency (weekly or biweekly)

### 2) Define a scoring method

• Use a simple scale (0–1, or 0–100%).
• Decide how you treat “stretch goals”.

### 3) Create templates (recommended)

• For recurring team OKRs, create consistent objective patterns.
• Standardize key result types:
• increase X to Y
• reduce X by Y
• deliver X by date

### 4) Assign ownership

• Every objective must have:
• owner
• team/department
• Every key result must have:
• numeric baseline/target where possible
• check-in owner

### Workflow 1: Create a new OKR cycle

1. Create cycle (monthly or quarterly)
2. Set dates and check-in cadence
3. Publish cycle to teams

### Workflow 2: Create objectives and key results

1. Create objective
2. Add key results:

• measurable target
• owner
• due date (if used)

1. Validate key results are measurable and not activity-only
2. Publish and share visibility

### Workflow 3: Weekly check-ins

1. Open key result
2. Add check-in:

• current value / progress %
• confidence (if used)
• notes and blockers

1. Save and review dashboard update

Best practice:

• Use check-in notes to capture blockers and actions.

### Workflow 4: Mid-cycle review

1. Review dashboard by team
2. Flag:

• KRs behind schedule
• low confidence items

1. Assign actions and adjust execution plan
2. Avoid changing targets unless governance allows

### Workflow 5: End-cycle review and close

1. Review final values for key results
2. Score objectives
3. Capture lessons learned
4. Close cycle and create next cycle OKRs

Common OKR reporting:

• OKR dashboard overview
• OKRs list by owner/team
• Check-ins list by period
• Progress trends (where enabled)
• Outcomes summary by cycle

Recommended cadence:

• Weekly: check-in review
• Monthly/quarterly: cycle review and planning

### OKRs are not measurable

• Rewrite KRs as numeric targets (baseline → target).
• Avoid “do X” key results without measurable outputs.

### Teams stop doing check-ins

• Add a recurring calendar cadence.
• Make check-in review part of weekly team meeting.
• Keep check-in flow simple (2–3 fields + notes).

### Too many objectives

• Limit objectives per team (2–5 per cycle).
• Focus on outcomes not activities.