A Short Guide to OKRs and How to Implement Them

I have helped dozens of companies implement Objectives and Key Results (OKRs) as a system of goal setting. First introduced to the world in Andrew Grove’s cult classic – High Output Management, OKR’s are designed for teams dealing with or driving for growth and change.  This is a quick, digestible but comprehensive guide to setting goals using OKRs and rolling out the framework in your team.

The Vision Cascade

This diagram of a Vision Cascade shows how the company’s long-term vision breaks down into strategic objectives and team OKRs (which could go further to personal OKRs). Each layer translates ambition into focus.

For me, this is the purpose of OKRs: to help everyone see how their work connects to the company objectives and ultimately the vision.

Without this cascade, companies generate long lists of initiatives, KPIs and ideas—none of which feel connected. With it, teams can focus on the few things that matter.

The Vision is defined as the ultimate change you and your team wish to see in the world. The impact of your mission. The Mission defines your first or next step towards realising your vision. For example, if your vision is to change the way people use computers forever, your mission might be to become the No. 1 software of choice in the country.

The Benefits of OKRs — Anchored in Autonomy

When departments and teams set their own OKRs in response to the company-level Objective, you create alignment and autonomy. Figure 2 illustrates this: leadership defines the ends; teams decide the means. This reduces micromanagement and boosts motivation.

This idea echoes Drucker’s Management by Objectives: define the what, empower teams on the how.

But OKRs go further by making the key results measurable and time-bound, so progress becomes visible across the whole organisation.

How to build great OKRs

OKRs grew out of Intel and spread through Google as a simple method to prioritise work in fast-changing environments. They build on S.M.A.R.T. thinking by separating:

• Objectives – qualitative, inspiring end-states; and
• Key Results – quantitative measures of success

This separation is powerful: it prevents confusion between tasks and outcomes, keeps planning cycles short, and clarifies what progress actually means.

Start with your most important metrics:

Your company OKR should reflect the stage you’re in and focus on the most important metrics. Try identifying the one most important thing you must achieve. For start-ups, this is extremely important and might consist of one of the following:

1. Problem-Solution Fit Stage – A metric that proves you have an accessible market, and people will pay for your product.
2. Product Market Fit Stage – A metric that proves people want more of what you do, for example it demonstrates customer retention.
3. Revenue Stage – A metric that proves people are recommending you, there is organic growth, the business model is sustainable, scalable and profitable.
4. Scale Up Stage – A metric that drives or proves you have accelerating growth (without accelerating costs).

Identify your stage. Choose the most Important metric/s, then craft one to three strong Company Objectives. This focuses the entire Vision Cascade.

At every level—company, team, individual—OKRs should describe inspiring outcomes. If an OKR feels like a task list, it is not an OKR.

Use conversion rates, volumes, percentages—anything that predefines success. Subjective metrics count too (e.g.,via satisfaction surveys – just define the exact questions in advance).

Examples of Good OKRs:

Business Objective: Win the Super Bowl. (Yes I am an American Football fan!)

• KR1: 300+ passing yards per game
• KR2: Defense allows <17 points per game
• KR3: Special teams top 3 in punt return coverage

Product Objective: Design a UX so intuitive that no customers need support.

• KR1: Design meets 100% of user requirements
• KR2: <1 UX-related support query per week
• KR3: Infra supports 100,000 users

Notice in these examples the Key Results are Outcomes or End-States too. Not outputs, or tasks. Tracking tasks is less likely to get you to your desired end-state and can feel meaningless, especially in meetings.

Sales Targets are not a good use of OKR’s, while you might argue they are outcomes, they wont define:

• What strategic shift must happen
• What must be true for this revenue to materialise
• What capability or behaviour change is required.

 

The Quarterly OKR Cycle

OKRs enable rapid course correction. This diagram helps you understand a typical cycle of OKR setting. A quarterly cycle has been typical for the companies I have helped, but it may be more appropriate to go monthly. Think: Short cycles and sprints, learning and iteration rather than long-term roadmaps.

You can report in on Key Results in weekly meetings. You might decide to iterate OKRs prior to the Quarterly Team Meeting. Reporting on Key Results rather than tasks helps keep it relevant to everyone and prevents micromanagement.

I hope you found this very concise guide helpful. Do send over any questions you have in the comments and remember, start simple. It can be difficult to craft and track inspiring and practical OKRs at first, so stick to one to three Objectives at company level and within each team/functional department. Then stick to a maximum of three Key Results per Objective.

I would recommend using AI tools to craft great OKR’s, it will vastly speed up the process. 

Good luck!