An OKR-Set always consists of Objectives and Key Results. The Objectives clearly show us what we want to achieve. The key results have to be measurable to tell us: “Did I do that or did I not do it.” The key results describe therefore how we get to the objective and what is the progress towards it.

Key Results

• Key Results are earthbound and metric-driven.
• Each Key Result should be a challenge in its own
• Key results should be succinct, specific, and measurable.
• A mix of outcomes, outputs, and inputs is helpful
• Completion of all key results must result in attainment of the objective

How to track the progress based on Key Results

We track our progress in that we measure it. To make something easily measurable, it should always have a number. You can formulate it however you like, to keep it practical. If the key result works better as a percentage or a due date, that’s fine too.

Objective	Key Results	Tracking
New Product Feature MetaGuide up and running Owner: xxx	KR1 At least 75% of clients use the new features w/in 30 days.	Status:
	KR2 Enable product returns at all locations – for retail and online.	Status:
	KR3 Reduce app downtime by 1%.	Status:

As with objectives, you want to avoid setting too many key results. Around three key results per objective should work best (although depending on your team size and objective, you could set up to five). 

Identifying Effective Key Results

At the most basic level, Key Results need to support their attached Objective. So if it isn’t clear how meeting these benchmarks will make the Objective true, that’s the first warning sign that the Key Results may not be effective.

• Are they measurable and verifiable? 
  • Is it clear when the criteria for success will be met?
  • Ask yourself whether the key result will leave you with evidence.
• Are they aggressive, yet realistic?
  •  Are they aspirational, yet not so outrageous that they could never be accomplished?
• Are they specific and timebound? 
  • Is it plainly stated what needs to occur and by when?