Master OKR writing vocabulary: Objective structure, Key Results, Initiative vs. task, OKR grading (0–1 scale), stretch goals, and committed vs. aspirational OKRs.
0 / 10 completed
1 / 10
In the OKR framework, what is the role of an Objective?
In OKRs, the Objective answers 'What do we want to achieve?' It should be qualitative, inspiring, and memorable — not a metric. Example: 'Become the most trusted payment platform for SMEs.' The measurable 'how we know we got there' comes from Key Results. John Doerr's rule: Objectives should be ambitious enough to be uncomfortable, yet clear enough to be directionally guiding.
2 / 10
A team writes: 'KR: Launch the mobile app.' Why is this a poorly written Key Result?
Key Results must be measurable outcomes, not tasks or outputs. 'Launch the mobile app' is an initiative (something you do). A well-written KR measures the result: 'Achieve 10,000 mobile app installs with a Day-7 retention rate of 40% by end of Q3.' The test: if a KR can be marked 100% complete just by doing a thing (regardless of impact), it is an initiative masquerading as a Key Result.
3 / 10
A company sets an OKR it is 100% confident it will achieve: 'Renew all current enterprise contracts.' Another OKR aims for a 10x improvement they have only a 50–70% chance of hitting. What are these two types called?
Committed OKRs are goals the team is confident it will achieve — failure is not acceptable (used for operational targets like renewals, SLA compliance). Aspirational OKRs (stretch goals / moonshots) target ambitious outcomes with a 50–70% achievement expectation. Google's OKR culture treats a 0.7 score on an aspirational OKR as a success; 1.0 might indicate the goal wasn't ambitious enough.
4 / 10
At the end of a quarter, a team scores its OKR Key Results on a 0–1 scale. KR1 = 0.4, KR2 = 0.7, KR3 = 1.0. Which interpretation of these scores follows standard OKR grading practice?
In OKR grading, 0.6–0.7 is considered the 'sweet spot' for aspirational Key Results — it means the team stretched hard but realistic. Below 0.4 warrants a root-cause conversation. A score of 1.0 on an aspirational KR often means the target was set too conservatively (the goal should have been harder). Committed OKRs, by contrast, are expected to hit 1.0 — anything lower is a concern.
5 / 10
What distinguishes an Initiative from a Key Result in OKR terminology?
An Initiative (sometimes called a 'project', 'task', or 'how') describes the work done to achieve a Key Result — it is an output. A Key Result measures the impact of that work — it is an outcome. Example: KR = 'Reduce API error rate from 2% to 0.5%'. Initiatives under that KR might include: 'implement circuit breakers', 'add retry logic', 'conduct load testing'. Confusing initiatives with KRs is the most common OKR writing mistake.
6 / 10
During a code review of Alex's pull request for the new user authentication module, Sarah comments: 'This section could be more concise. We're repeating logic here that's already handled by the validateUser() function.' Which of the following best describes Sarah's intention in this comment related to OKR terminology?
Sarah is focusing on a key result related to efficiency and reducing redundancy. OKRs are fundamentally about outcomes, and this comment directly addresses whether the team is achieving its objective of a streamlined user authentication process. The other options misinterpret her feedback as solely stylistic or unrelated to the overall OKR goals.
7 / 10
Liam sends this message in a Slack channel: 'Just finished implementing the new API endpoint for reporting user activity. We hit our KR of 80% of users successfully using it within the first week! 🎉' Considering OKR principles, what does Liam's message primarily demonstrate?
Liam's message showcases successful attainment of a key result – specifically, the percentage of users utilizing the new API. He's also proactively communicating this achievement. The other options represent potential misinterpretations or areas requiring more detailed analysis, not the immediate demonstration of a fulfilled KR.
8 / 10
You're writing the description for a pull request aimed at improving the performance of the image processing pipeline. You want to align it with your team's OKRs. Which of the following phrases best reflects this alignment?
The correct option directly links the change (reduced latency) to a specific key result and ultimately to the team's objective (faster loading times). The other options focus on technical details like refactoring or bug fixes without explicitly connecting them to measurable outcomes within the OKR framework.
9 / 10
During the daily stand-up, Maria says: 'I spent today working on resolving the issues reported in the latest build. We're making progress towards our KR for bug reduction.' What is Maria's primary contribution to the team's OKR discussion using this statement?
Maria's statement highlights her active participation in achieving a key result related to bug reduction. While she mentions resolving issues, the focus is on the progress towards the KR, not simply listing tasks. The other options represent less relevant contributions during a stand-up update.
10 / 10
A development team is working on an OKR: 'Increase user engagement by 20%.' They identify the following initiatives to support this objective: 'Conduct A/B testing of new onboarding flows,' 'Implement personalized recommendations,' and 'Run a targeted email campaign.' Which statement best describes the relationship between these initiatives and the key result?
Initiatives are actions taken *to* achieve a key result. In this case, the listed activities (A/B testing, recommendations, email campaigns) are designed to influence and drive user engagement, thereby contributing to the overall KR. The other options misrepresent the roles of initiatives within the OKR framework.
What will I learn from the "OKR Writing Vocabulary" exercise?
Master OKR writing vocabulary: Objective structure, Key Results, Initiative vs. task, OKR grading (0–1 scale), stretch goals, and committed vs. aspirational OKRs.
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.