Objectives and Key Results (OKRs)

What Are OKRs?

OKRs (Objectives and Key Results) are our framework for setting and tracking quarterly goals. They help us focus on what matters most and measure our progress.

Structure

Objective: A qualitative, aspirational goal

Key Results: 3-5 quantitative measures of success

Example OKR

Objective: Become the leading choice for professional Home Assistant installers

Key Results:

1. Grow active installer accounts from 50 to 100
2. Achieve 90% customer satisfaction rating
3. Reduce average time-to-deployment from 2 weeks to 3 days

How We Work on OKRs

OKR work happens asynchronously using GitLab Epics. Each OKR is tracked as an Epic in GitLab, with individual initiatives and tasks as issues within that Epic.

Why GitLab Epics?

• Transparency: Everyone can see progress on company and team OKRs
• Async Collaboration: Team members can contribute updates and discussion on their own schedule
• Integrated Workflow: OKRs are directly connected to the work we’re doing in issues and merge requests
• Progress Tracking: Automatic progress calculation based on completed issues

How to Use Epics for OKRs:

1. Each quarterly OKR is created as an Epic in GitLab
2. Break down initiatives into issues and link them to the Epic
3. Update progress regularly (weekly or as milestones are reached)
4. Use Epic discussions for async collaboration on strategy and blockers

This keeps OKR planning and execution visible to the entire team while respecting everyone’s time and working style.

Weekly OKR Status Updates

Each OKR should receive a weekly status update to track progress, maintain momentum, and communicate progress to stakeholders. These updates are posted as comments in the OKR’s GitLab Epic.

Weekly Update Format

Use this template for consistent, clear status updates:

## Weekly Update

**Week of:** [Month] [Day]-[Day], [Year]

### Progress This Week

#### [Scope/Initiative Name]

* [Specific accomplishment or progress made]
* [Another accomplishment]

#### [Additional Scope if Applicable]

* [Specific accomplishment or progress made]

### Next Week

#### [Scope/Initiative Name]

* [Planned work item]
* [Another planned item]

### Notes

* [Any blockers, dependencies, or important context]
* [Decisions made or needed]

---

### KR Progress:

* [Key Result 1]: [Current value] / [Target value] ([Percentage]%)
* [Key Result 2]: [Current value] / [Target value] ([Percentage]%)
* [Key Result 3]: [Current value] / [Target value] ([Percentage]%)

Example Weekly Update

## Weekly Update

**Week of:** November 11-15, 2025

### Progress This Week

#### Connect Portal & Installation Management

* Completed user authentication flow with SSO integration
* Deployed staging environment for installer testing
* Fixed 8 bugs reported from beta testers

#### API Development

* Launched v2 endpoints for device provisioning
* Improved API response times by 40%

### Next Week

#### Connect Portal & Installation Management

* Begin user acceptance testing with 5 installer partners
* Implement dashboard analytics widgets

#### API Development

* Add rate limiting to public endpoints
* Write API documentation for v2 endpoints

### Notes (if any)

* Waiting on security team review for SSO implementation (ETA: Nov 18)
* Designer is out next week, UI polish will shift to following week

---

### KR Progress:

* Launch Connect Portal Beta: 85% complete (target: 100% by Nov 30)
* Onboard 20 beta installers: 12/20 (60%)
* Achieve <500ms API response time: 420ms average (target met)

Best Practices

Be Specific: Use concrete accomplishments rather than vague statements

Update Consistently: Post updates on the same day each week (e.g., every Friday)

Track Blockers: Raise issues early so they can be addressed

Celebrate Progress: Acknowledge wins, both big and small

Link to Work: Reference related issues, MRs, or documentation where appropriate

OKR Process

Quarterly Cycle

Week 1: Leadership proposes company OKRs

Week 2: Teams draft department OKRs aligned with company goals

Week 3: Finalize and publish OKRs company-wide

Weeks 4-12: Execute and track progress

Week 13: Review, score, and reflect

Setting Good OKRs

Ambitious but Achievable: Aim for 70-80% success rate

Measurable: Key results should be quantifiable

Aligned: Team OKRs should support company OKRs

Time-Bound: All OKRs are quarterly

Scoring OKRs

We score OKRs on a 0.0 - 1.0 scale:

• 0.0 - 0.3: We made some progress but missed significantly
• 0.4 - 0.6: Made good progress but didn’t hit the target
• 0.7 - 0.9: Hit or exceeded the target (ideal range)
• 1.0: Exceeded all expectations (may indicate sandbagging)

OKR Examples by Department

Engineering

Objective: Deliver rock-solid platform reliability

Key Results:

1. Achieve 99.9% uptime for hosted instances
2. Reduce mean time to recovery (MTTR) from 2 hours to 30 minutes
3. Deploy automated rollback system for 100% of production updates

Sales

Objective: Build predictable revenue growth

Key Results:

1. Grow MRR from $X to $Y
2. Achieve 50% win rate on qualified opportunities
3. Reduce sales cycle from 45 to 30 days

Customer Success

Objective: Drive exceptional customer outcomes

Key Results:

1. Achieve Net Promoter Score (NPS) of 50+
2. Reduce customer churn from 5% to 3%
3. Increase customer expansion revenue by 25%