OKRs (Objectives and Key Results) have become the standard goal-setting framework for companies like Google, Intel, and Spotify. Google even published a detailed guide on setting OKRs based on their internal practices. But they're not just for organizations - they work incredibly well for personal goal setting too.

What are OKRs?

OKRs consist of two parts:

  • Objective: What you want to achieve. It should be qualitative, inspirational, and time-bound.
  • Key Results: How you'll measure progress. These should be quantitative and specific.

Why Use Personal OKRs?

As developers, we often have vague goals like "get better at programming" or "learn new technologies." OKRs force you to be specific:

  • They create focus - you know exactly what to work on
  • They provide accountability - you can measure your progress
  • They give you direction - when you're unsure what to do next, check your OKRs

How to Write Personal OKRs

Step 1: Define Your Objective

Your objective should be ambitious but achievable. It should excite you and give you a clear direction. Good decision-making matters here - I wrote about frameworks for that in making decisions the right way.

Bad:  "Learn programming"
Good: "Become proficient in backend development with Go"

Step 2: Define Key Results

Each objective should have 2-5 key results. They must be measurable.

Objective: Become proficient in backend development with Go

Key Results:
- Complete 3 Go projects and deploy them
- Read "The Go Programming Language" book (100%)
- Contribute to 2 open source Go projects
- Build a REST API with authentication and deploy to production

Step 3: Set a Timeline

Quarterly OKRs work best. Three months is long enough to achieve something meaningful but short enough to stay focused.

Example Personal OKRs for Developers

Career Growth

Objective: Grow as a senior engineer

Key Results:
- Lead 2 major features from design to deployment
- Mentor 1 junior developer (weekly 1:1s)
- Give 1 tech talk at a meetup or conference
- Write 6 technical blog posts

Learning

Objective: Master cloud infrastructure

Key Results:
- Get AWS Solutions Architect certification
- Deploy 3 production services on Kubernetes
- Reduce team's cloud costs by 20%
- Document the team's infrastructure in a runbook

Health and Productivity

Objective: Sustainable high performance

Key Results:
- Exercise 4x per week (track in app)
- Read 6 books (2 technical, 4 non-technical)
- Maintain inbox zero daily
- Sleep 7+ hours per night (90% of days)

Tracking and Reviewing

Set a weekly check-in with yourself:

  • Score each key result from 0.0 to 1.0
  • 0.7 is a good score - if you're hitting 1.0 every time, your OKRs aren't ambitious enough
  • Adjust key results if circumstances change, but don't lower the bar just because it's hard. If you're consistently falling short and feeling drained, that might be a sign of something deeper - I wrote about recognizing and recovering from burnout

Tools for Personal OKRs

  • A simple spreadsheet works fine
  • Notion has good OKR templates
  • Dedicated apps: Weekdone, Gtmhub
  • Or just a markdown file in your notes

The tool doesn't matter. Consistency does. Pick something and review it weekly.

Start Today

Write down one objective and three key results right now. Set a calendar reminder to review them next Sunday. That's it - you've started.