Course outline
Module 1
Module 1: What Are OKRs?
What Are OKRs?
Knowledge check
Q1. What does the 'O' in OKR stand for?
- A. Outcome
- B. Objective ✓
- C. Operation
- D. Output
Why: OKR stands for Objectives and Key Results. The Objective is the qualitative, inspiring goal that states what you want to achieve.
Q2. Which of the following is the best example of a well-written Objective?
- A. Increase monthly revenue to $500,000 by June 30
- B. Become the go-to platform for small business customers ✓
- C. Send 1,000 marketing emails each week
- D. Complete the CRM migration project by Q3
Why: A good Objective is qualitative, inspiring, and memorable. Option B describes a meaningful direction without a specific number. The other options are either quantitative (A), activity-based (C), or closer to a task than an aspirational goal (D).
Q3. What is the primary purpose of Key Results in an OKR framework?
- A. To list the tasks the team must complete
- B. To assign blame when goals are missed
- C. To measure progress toward the Objective with measurable outcomes ✓
- D. To describe the company's mission statement
Why: Key Results are specific, measurable outcomes that indicate whether the Objective has been achieved. They focus on results rather than activities or tasks.
Q4. Which statement best describes a Key Result?
- A. A vague aspiration about company culture
- B. A daily to-do list for employees
- C. A measurable outcome with a clear target, such as 'Reduce customer churn from 8% to 4%' ✓
- D. A financial budget allocation
Why: Key Results must be measurable and time-bound, with a clear starting point and target. Reducing churn from 8% to 4% is a concrete, verifiable outcome.
Q5. How many Key Results is a typical Objective associated with?
- A. One to two Key Results is most effective, and no more than about five ✓
- B. Exactly ten Key Results
- C. As many as possible to cover every detail
- D. There should be no Key Results, only Objectives
Why: Most OKR practitioners recommend between two and five Key Results per Objective. Too many dilutes focus, and each Key Result should meaningfully indicate success of the Objective.
Module 2
Module 2: Writing Compelling Objectives
Writing Compelling Objectives
Knowledge check
Q1. Which of the following is the best example of a well-written OKR objective?
- A. Increase revenue by 20% by Q4 through new enterprise contracts
- B. Become the most trusted customer support team in our market ✓
- C. Use the new CRM software for all sales calls
- D. Complete 50 tasks on the project backlog this quarter
Why: A strong objective is qualitative, inspiring, and memorable. Option B describes a clear, aspirational outcome without embedding metrics, which belong in key results. Option A mixes in numbers that should be key results, Option C describes an activity rather than an outcome, and Option D is a task count rather than a meaningful goal.
Q2. What is the primary purpose of an objective in the OKR framework?
- A. To list every task the team must complete
- B. To define a qualitative direction the team wants to move toward ✓
- C. To measure the exact numerical outcome of a project
- D. To assign individual responsibilities to team members
Why: Objectives state where you want to go in qualitative, motivating terms. Measurement is handled by key results, task lists are a separate planning tool, and assigning responsibilities is an ownership decision rather than the purpose of the objective itself.
Q3. Which characteristic makes an objective easier for a team to rally around?
- A. It contains as many specific metrics as possible
- B. It is written in inspiring, memorable language that is easy to understand ✓
- C. It covers every department's priorities at once
- D. It is written in technical jargon to sound authoritative
Why: Objectives work best when they are inspiring and clear, so people can recall and act on them. Packing in metrics, trying to cover everything, or using jargon all make objectives harder to understand and less motivating.
Q4. Which of these objectives is too vague to be useful?
- A. Make our onboarding experience delightful for new customers
- B. Reduce customer churn by improving the first 30 days of use
- C. Get better at things this quarter ✓
- D. Launch a beta version of the mobile app to early adopters
Why: Option C has no clear direction or context, so the team cannot tell what success looks like or what to focus on. The other options are specific enough to guide action while still being qualitative and inspiring.
Q5. How should an objective relate to its key results?
- A. Key results should restate the objective in different words
- B. Key results should be measurable evidence that the objective has been achieved ✓
- C. Key results should be a list of unrelated tasks
- D. Key results should be set after the quarter ends
Why: Key results are the measurable outcomes that show whether the objective was achieved. Restating the objective adds no information, unrelated tasks don't demonstrate progress, and key results are set at the start of the cycle so they can guide the work.
Module 3
Module 3: Designing Measurable Key Results
Designing Measurable Key Results
Knowledge check
Q1. Which of the following is the best example of a measurable key result?
- A. Improve customer happiness
- B. Increase Net Promoter Score from 32 to 45 by the end of the quarter ✓
- C. Make the product feel more modern
- D. Be the best team in the company
Why: A measurable key result has a specific metric, a starting value, a target value, and a deadline. Option B states a clear baseline (32), target (45), and timeframe (quarter), so progress can be objectively tracked. The other options are subjective or vague.
Q2. What is the main difference between an objective and a key result?
- A. An objective is measurable, while a key result is inspirational
- B. An objective describes what you want to achieve qualitatively, while a key result defines how you will measure success ✓
- C. An objective is set by individuals, while key results are set by executives
- D. There is no meaningful difference; the terms are interchangeable
Why: Objectives are qualitative, directional, and inspiring statements of what to achieve. Key results are quantitative measures that show whether the objective has been achieved. Each objective typically has 2 to 5 key results.
Q3. Which key result is an output rather than an outcome?
- A. Reduce customer churn from 8% to 4% per month
- B. Increase weekly active users from 10,000 to 15,000
- C. Ship 12 new feature releases this quarter ✓
- D. Raise average order value from $40 to $55
Why: Shipping 12 features measures activity completed, which is an output. The other options measure changes in customer or business behavior, which are outcomes. Strong key results focus on outcomes because they show whether the work actually created value.
Q4. Why should a good key result be ambitious but achievable?
- A. So that teams never have to stretch themselves
- B. So that the key result is easy to report as complete
- C. So that teams are motivated to stretch while still believing success is possible ✓
- D. So that leadership can avoid setting targets altogether
Why: OKRs are designed to push teams beyond their comfort zone. Targets that are too easy provide no challenge, while impossible targets demotivate people. Aiming for roughly 70% achievement on ambitious key results is a common guideline.
Q5. A team wants to improve software quality. Which key result is best designed to be measurable?
- A. Make the codebase cleaner and easier to maintain
- B. Work hard to reduce bugs as much as possible
- C. Reduce production-reported bugs from 40 per month to 15 per month by the end of Q3 ✓
- D. Ensure developers feel good about the quality of their work
Why: Option C includes a specific metric (production bugs), a baseline (40), a target (15), and a deadline (end of Q3). Vague phrases like 'as much as possible' or 'feel good' cannot be objectively verified, so they fail the measurability test.
Module 4
Module 4: Aligning OKRs Across Teams
Aligning OKRs Across Teams
Knowledge check
Q1. What is the primary purpose of aligning OKRs across teams?
- A. To ensure every team works on identical objectives
- B. To ensure team objectives contribute to shared company-level goals ✓
- C. To eliminate the need for individual team planning
- D. To reduce the total number of objectives each company sets
Why: Alignment ensures that each team's objectives connect to and support higher-level company goals, while still allowing teams to set their own specific objectives. It does not require identical objectives across teams.
Q2. Which term describes an OKR that a team sets because it supports an objective from another team or the company?
- A. Stretch goal
- B. Cascaded objective ✓
- C. Key result
- D. Committed objective
Why: A cascaded objective is one that flows down from a higher-level objective, showing how a team's work supports broader goals. Stretch goals are ambitious targets, key results are measurable outcomes, and committed objectives are must-achieve items.
Q3. Two teams have objectives that conflict over the same shared resource. What is the best first step?
- A. Ignore the conflict until the end of the quarter
- B. Let the team with more headcount win by default
- C. Surface the conflict and discuss it with leaders or cross-team partners to find a resolution ✓
- D. Remove both objectives from the OKR cycle
Why: Transparency and collaboration are key in OKR alignment. Surfacing conflicts early allows leaders and teams to negotiate priorities and trade-offs rather than letting problems grow unnoticed.
Q4. Which of the following is a good example of a well-aligned key result for a support team whose company objective is to improve customer retention?
- A. Attend three team social events
- B. Reduce average first-response time for customer tickets from 24 hours to 4 hours ✓
- C. Complete the new office renovation
- D. Update the team's internal wiki
Why: A strong aligned key result is measurable and directly tied to the company objective. Faster response times plausibly improve customer retention, while the other options are either unmeasurable or unrelated.
Q5. Why do many organizations hold regular cross-team OKR check-ins?
- A. To replace the need for quarterly reviews
- B. To share progress, spot dependencies, and adjust alignment as priorities change ✓
- C. To assign blame for missed key results
- D. To increase the number of objectives each team carries
Why: Cross-team check-ins help teams stay coordinated, surface dependencies early, and adapt to shifting priorities. Their purpose is collaboration and course correction, not blame or added workload.
Module 5
Module 5: Setting Cadence and Check-Ins
Setting Cadence and Check-Ins
Knowledge check
Q1. What is the most common recommended cadence for reviewing progress on OKRs at the team level?
- A. Once a year, during annual planning
- B. Weekly or biweekly check-ins ✓
- C. Only at the end of each quarter
- D. Daily, through formal status reports
Why: Weekly or biweekly check-ins keep teams aware of progress on key results and allow them to adjust course early, without the overhead of daily formal reporting.
Q2. What is the primary purpose of a weekly OKR check-in?
- A. To assign blame for missed targets
- B. To review progress, surface blockers, and decide on quick adjustments ✓
- C. To write the final grade for each objective
- D. To replace the quarterly planning process
Why: Weekly check-ins are meant to be lightweight working sessions focused on progress, obstacles, and small course corrections rather than evaluation or blame.
Q3. When in the quarter should teams typically hold their formal OKR review and retrospective?
- A. At the start of the quarter, before any work begins
- B. In the middle of the quarter only
- C. At the end of the quarter, to assess results and learn for the next cycle ✓
- D. Only when leadership requests it
Why: An end-of-quarter review lets teams score their key results, reflect on what worked, and carry lessons into planning the next cycle.
Q4. Why are mid-cycle check-ins valuable in an OKR process?
- A. They allow teams to change objectives freely without reason
- B. They reveal whether key results are on track while there is still time to change direction ✓
- C. They replace the need for end-of-quarter scoring
- D. They are required by most OKR frameworks to lock in targets
Why: A mid-cycle check-in provides an early signal on whether key results are trending toward success, giving the team time to adjust tactics or resources before the cycle ends.
Q5. Which practice best supports healthy OKR check-ins?
- A. Tying scores directly to individual performance reviews
- B. Keeping check-ins focused on learning and transparency rather than punishment ✓
- C. Holding check-ins only with senior executives
- D. Updating progress only when a key result is fully complete
Why: When check-ins feel safe and focus on learning, people report progress honestly and surface risks early, which is what makes the OKR cadence effective.
Module 6
Module 6: Scoring and Grading Progress
Scoring and Grading Progress
Knowledge check
Q1. In the OKR framework, what is the typical scoring range used to grade a key result at the end of a cycle?
- A. Pass or fail
- B. 0.0 to 1.0 ✓
- C. 1 to 5 stars
- D. A percentage from 0% to 200%
Why: OKR progress is commonly graded on a 0.0 to 1.0 scale, where 1.0 means fully achieved and lower values indicate partial progress. This scale encourages ambitious targets rather than punishing stretch goals.
Q2. A team sets a key result to increase customer retention from 80% to 90%, and at the end of the quarter retention reached 85%. What is the score for this key result?
- A. 0.25
- B. 0.50 ✓
- C. 0.85
- D. 0.90
Why: Progress is measured as the distance achieved toward the target: (85 - 80) / (90 - 80) = 5 / 10 = 0.5. Simply reporting the final value would ignore the starting baseline.
Q3. What score is generally considered a healthy result for an ambitious OKR, where the goal is meant to stretch the team?
- A. 1.0 every time
- B. Around 0.6 to 0.7 ✓
- C. Below 0.2
- D. Exactly 0.5
Why: Ambitious OKRs are designed so that teams often achieve roughly 60-70% of their targets. Consistently scoring 1.0 suggests goals were not ambitious enough, while very low scores may signal unrealistic targets or poor execution.
Q4. Why is it recommended to score OKRs using a 0.0 to 1.0 scale rather than a simple completed or not completed binary?
- A. It makes the scores easier to hide from leadership
- B. It captures partial progress and rewards effort toward ambitious goals ✓
- C. It eliminates the need to set measurable key results
- D. It ensures every team receives the same score
Why: A graded scale reveals meaningful partial progress, so teams that move substantially toward a stretch goal are recognized rather than marked as failures. This supports learning and honest reflection.
Q5. Which of the following best describes the purpose of progress check-ins during an OKR cycle?
- A. To assign blame for missed targets
- B. To review current scores, identify risks, and adjust actions as needed ✓
- C. To rewrite the objectives entirely every week
- D. To wait until the final day to measure results
Why: Regular check-ins allow teams to monitor progress against key results, surface blockers early, and course-correct. Scoring is ongoing, not a single event at the end of the cycle.
Module 7
Module 7: Common OKR Pitfalls and How to Avoid Them
Common OKR Pitfalls and How to Avoid Them
Knowledge check
Q1. Which of the following is a common OKR pitfall where teams write key results that are simply task lists rather than measurable outcomes?
- A. Setting too many objectives at once
- B. Confusing activities with outcomes ✓
- C. Setting objectives that are too ambitious
- D. Failing to review OKRs quarterly
Why: Key results should measure outcomes or impact, not list tasks to complete. Writing 'launch a new website' is an activity; a key result should describe the measurable result, such as 'increase conversion rate from 2% to 3.5%'.
Q2. What is the main risk of setting too many objectives in a single quarter?
- A. Leadership will have nothing to review
- B. Teams spread their focus thin and make little progress on any one priority ✓
- C. Key results become automatically achievable
- D. The company will exceed its budget
Why: Limiting the number of objectives, typically to three to five per team, keeps focus sharp. Too many objectives dilute attention and resources, so nothing important gets the depth of effort it needs.
Q3. A team sets a key result of 'maintain current customer satisfaction.' What is the most likely problem with this key result?
- A. It is too ambitious
- B. It has no clear measure of progress or a target to reach ✓
- C. It is too narrowly focused on one team
- D. It depends on an external vendor
Why: Good key results are specific, measurable, and include a target. 'Maintain' describes a status quo rather than progress, and no numeric target shows what success looks like, so the team cannot tell whether they are improving.
Q4. Why is it a pitfall to treat OKRs as a performance evaluation tool tied directly to compensation?
- A. It makes OKRs too complicated to write
- B. People may set safe, easily achievable goals to protect their rewards, discouraging ambition ✓
- C. It causes managers to stop reviewing OKRs
- D. It requires external auditors to verify results
Why: When OKR scores drive pay, employees have an incentive to sandbag goals and pick targets they know they can hit. OKRs are meant to encourage stretch goals, so separating them from compensation helps keep ambition high.
Q5. Which practice best helps teams avoid setting OKRs that are disconnected from company priorities?
- A. Writing OKRs in isolation and submitting them at the end of the quarter
- B. Aligning team objectives with higher-level company objectives so each supports the next ✓
- C. Copying the OKRs of a competitor
- D. Assigning OKRs only to the executive team
Why: Alignment ensures that team-level objectives contribute to the organization's top priorities. Without it, teams can work hard on goals that do not move the company forward, wasting effort even when their own key results are met.