APM Agile Product Strategy and OKRs 1 — Questions and Answers
Question 1: In the OKR framework, what does the 'O' stand for, and how is it best characterized?
- Objective — a qualitative, inspirational goal defining what you want to achieve (Correct answer)
- Output — a measurable deliverable produced by the team each sprint
- Outcome — a quantitative result directly tied to business revenue
- Opportunity — a potential area identified for product improvement
Correct answer: Objective — a qualitative, inspirational goal defining what you want to achieve
In OKRs, the 'O' stands for Objective, which is a qualitative, ambitious, and inspirational goal that defines what the team wants to achieve.
Question 2: What distinguishes Key Results from tasks or initiatives in the OKR framework?
- Key Results are assigned to individuals while initiatives are team-wide
- Key Results are measurable outcomes signaling progress toward the Objective, not activities (Correct answer)
- Key Results describe the work to be done while initiatives describe the expected outcomes
- Key Results are set annually while initiatives are defined each sprint
Correct answer: Key Results are measurable outcomes signaling progress toward the Objective, not activities
Key Results must be measurable outcomes that signal progress toward the Objective — they answer 'how will we know we succeeded,' not 'what will we do.'
Question 3: How many Objectives does the most widely adopted OKR methodology recommend a team maintain per quarter?
- 1–2
- 3–5 (Correct answer)
- 6–8
- 10–12
Correct answer: 3–5
Most OKR practitioners, including Google, recommend 3–5 objectives per quarter to maintain strategic focus without spreading team effort too thin.
Question 4: What is the recommended achievement rate for OKRs that signals the goals were appropriately ambitious?
- 50–60%
- 70–75% (Correct answer)
- 90–100%
- Exactly 100%
Correct answer: 70–75%
A 70–75% achievement rate is the widely accepted ideal, indicating goals were stretch targets — ambitious without being impossible.
Question 5: How do OKRs fundamentally differ from traditional KPIs (Key Performance Indicators)?
- OKRs are used only for engineering teams while KPIs are used for business teams
- OKRs are time-boxed, aspirational change drivers while KPIs are ongoing health-monitoring metrics (Correct answer)
- KPIs drive innovation while OKRs measure operational efficiency
- OKRs are set by executives while KPIs are defined by individual contributors
Correct answer: OKRs are time-boxed, aspirational change drivers while KPIs are ongoing health-monitoring metrics
OKRs are time-boxed, aspirational goals designed to drive improvement and change, while KPIs are ongoing metrics used to monitor the health of business-as-usual operations.
Question 6: What is 'cascading' in the context of an organizational OKR implementation?
- Breaking down sprint goals into daily standup tasks
- Aligning team and individual OKRs to higher-level company objectives so everyone works toward shared goals (Correct answer)
- Rolling over unfinished OKRs automatically to the next quarter
- Documenting OKRs in a hierarchical product roadmap for stakeholder review
Correct answer: Aligning team and individual OKRs to higher-level company objectives so everyone works toward shared goals
Cascading OKRs means aligning team and individual objectives to company-level OKRs, ensuring organizational coherence across all levels.
Question 7: In agile product strategy, what does a 'North Star Metric' represent?
- The single most important metric that captures the core value a product delivers to customers (Correct answer)
- The quarterly revenue target set by the finance department
- The number of features shipped per sprint cycle
- The Net Promoter Score benchmark for the industry sector
Correct answer: The single most important metric that captures the core value a product delivers to customers
A North Star Metric is the single key measure that best captures the core value your product delivers to customers and most reliably predicts long-term business success.
APM Agile Product Strategy and OKRs 1
In the OKR framework, what does the 'O' stand for, and how is it best characterized?