Learn to write strong OKRs: ambitious Objectives, measurable Key Results, and OKR review language.
0 / 10 completed
1 / 10
What is the structure of a well-written OKR?
OKRs separate direction from measurement: the Objective answers 'where are we going?' — it should be inspiring and directional. Key Results answer 'how will we know we got there?' — they must be specific, measurable, and achievable by the period end. Example: O: Make our API the fastest in the industry. KR1: Reduce p99 latency from 500ms to 100ms. KR2: Pass industry benchmark top 5.
2 / 10
What is the difference between an 'output' KR and an 'outcome' KR?
Output KR: 'Ship the mobile onboarding redesign by Q2.' This measures delivery, not value. Outcome KR: 'Increase mobile Day-7 retention from 23% to 35% by Q2 end.' This measures the result. Outcome KRs focus the team on impact, not just activity — preventing OKRs from becoming a task list.
3 / 10
What does 'ambitious but not crazy' mean in OKR philosophy?
In the OKR tradition (Andy Grove, John Doerr), a 70% achievement score on a Key Result is considered success. If you always hit 100%, your OKRs are too conservative. If you never hit 50%, they are unrealistic. 70% achievement on a stretched goal often produces more value than 100% on a conservative one.
4 / 10
What is 'OKR cascade' in organisational vocabulary?
OKR cascade: Company OKRs → Department OKRs → Team OKRs → Individual OKRs. Each level's OKRs should directly support the level above. Good cascade also allows bottom-up input: teams identify OKRs that are necessary preconditions for company objectives even if not explicitly called out top-down.
5 / 10
What is 'OKR grading' or 'scoring' in quarterly review vocabulary?
OKR grading: at period end, each KR is scored (0.0 = no progress, 1.0 = fully achieved; typically 0.7 = success). The goal is learning, not judgment. Low scores prompt: was the goal wrong? Did external factors change? Did we under-resource? High scores prompt: were we ambitious enough? Scores feed into the next cycle's planning.
6 / 10
Sarah (Senior Backend Engineer) is reviewing a pull request for a new API endpoint. The PR description states: 'Implement user authentication using JWT.' She notices the developer hasn't included any Key Results to measure success. Which of the following best describes the missing element?
Option A: The PR should be rewritten in Python.
Option B: The developer needs to add Key Results related to the API's performance and security.
Option C: The PR description is too verbose and needs shortening.
Option D: The authentication method is incorrect; it should use OAuth2.
This scenario highlights the importance of connecting objectives with measurable results. Key Results provide a specific way to track progress towards an objective. Simply implementing JWT doesn't tell us if it's working effectively or securely – that's where Key Results come in. Option B is correct because it directly addresses this gap.
7 / 10
Mark (Product Manager) sends a Slack message to the team: 'Our objective for Q3 is to increase user engagement. Key Result 1: Achieve a 20% increase in daily active users.' Which of the following accurately describes the relationship between the objective and the key result?
Option A: The key result defines *how* we achieve the objective.
Option B: The key result measures the success of achieving the objective.
Option C: The objective is more important than the key result.
Option D: The key result should be adjusted if daily active users don't increase.
This question tests understanding of the core relationship between objectives and Key Results. An objective sets a desired outcome, while a Key Result provides a concrete metric to assess whether that outcome has been reached. Option B is correct because it defines this fundamental connection—measuring success is the purpose of a KR.
8 / 10
David (Engineering Lead) is drafting a PR description for a new feature. He writes: 'Implement improved error logging.' Which statement best reflects how David should refine this to align with OKR principles?
Option A: The description should focus solely on the technical implementation details.
Option B: He should add a Key Result like 'Reduce critical errors by 15%' to provide measurable progress.
Option C: The description should include an estimated development time for the feature.
Option D: He should prioritize user experience over technical improvements.
A good OKR-aligned PR description focuses on *what* needs to be achieved, not *how*. Adding a Key Result provides the measurable target. Option A is correct because it emphasizes defining the desired outcome – reducing errors – rather than just detailing the technical steps.
9 / 10
Elena (Head of Development) explains the 'OKR cascade' to her team. Which of the following BEST describes this concept?
Option A: It's a complex database system used for tracking OKRs.
Option B: It refers to cascading Key Results down from company objectives to individual teams and projects, ensuring alignment.
Option C: It's a method for automatically generating random OKRs each quarter.
Option D: It's a formal process requiring approval from the CEO before setting any OKRs.
The OKR cascade ensures that everyone is working towards the same overall goals. It involves breaking down high-level company objectives into smaller, team-specific Key Results. This creates alignment and avoids duplicated effort – option B accurately describes this process.
10 / 10
Tom (Project Manager) is preparing for the quarterly OKR review. The team achieved its objective of 'Improve Customer Satisfaction.' However, one of the Key Results – 'Increase Net Promoter Score by 10%' – was not met. Which action should Tom primarily focus on during the review?
Option A: Blame the development team for failing to meet the KR.
Option B: Analyze *why* the KR wasn't achieved and identify actions to improve in the next cycle.
Option C: Immediately set a new, more ambitious KR for the next quarter.
Option D: Ignore the missed KR as long as the overall objective was met.
OKR grading is about learning from both successes and failures. The primary focus during a review isn't simply on whether the KR was achieved but *why* it wasn't. This allows for adjustments to be made in the next cycle—option B correctly identifies this critical step.
What will I learn from the "OKR Writing — Objectives and Key Results Language" exercise?
Learn to write strong OKRs: ambitious Objectives, measurable Key Results, and OKR review language.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Roadmap & OKR exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss roadmap & okr topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Roadmap & OKR exercises?
See the full Roadmap & OKR exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.