Product Management Certification Program Product Management Certification Program 4 — Questions and Answers
Question 1: What is the key difference between a 'leading indicator' and a 'lagging indicator' in product metrics?
- Leading indicators measure past performance; lagging indicators predict future trends
- Leading indicators predict future outcomes; lagging indicators confirm past results (Correct answer)
- Leading indicators are for revenue; lagging indicators are for engagement
- There is no meaningful difference between the two
Correct answer: Leading indicators predict future outcomes; lagging indicators confirm past results
Leading indicators (e.g., feature adoption) predict future outcomes like retention, while lagging indicators (e.g., churn rate) confirm what already happened.
Question 2: A product team is debating between building a highly requested feature for 5% of power users versus a moderate improvement for 95% of casual users. Which framework BEST guides this decision?
- Kano model analysis of user segments (Correct answer)
- MoSCoW prioritization
- Eisenhower Matrix
- OKR alignment check
Correct answer: Kano model analysis of user segments
The Kano model categorizes features by their impact on user satisfaction across segments, making it ideal for comparing value across different user types.
Question 3: What is 'technical debt' and why should a PM care about it?
- Money owed to software vendors — PMs should track it for budget purposes
- Shortcuts taken in code that slow future development and increase bug risk (Correct answer)
- The backlog of unbuilt features requested by engineers
- Documentation gaps that slow onboarding of new team members
Correct answer: Shortcuts taken in code that slow future development and increase bug risk
Technical debt accumulates when quick solutions are chosen over proper ones, eventually slowing velocity and increasing instability, which PMs must balance against feature work.
Question 4: Which discovery method is BEST for understanding how users actually behave in their natural environment versus how they say they behave?
- Surveys with Likert-scale questions
- Contextual inquiry / ethnographic observation (Correct answer)
- Focus groups with a moderator
- In-app NPS polls
Correct answer: Contextual inquiry / ethnographic observation
Contextual inquiry reveals real behavior in context, eliminating the gap between what users self-report and what they actually do.
Question 5: What is a 'North Star Metric' (NSM) in product management?
- The primary revenue target set by the CFO each quarter
- A single metric that best captures the core value the product delivers to users (Correct answer)
- The NPS score reported to the board
- The sprint velocity target for the engineering team
Correct answer: A single metric that best captures the core value the product delivers to users
The North Star Metric aligns the entire team around the one number that best reflects user value and sustainable growth.
Question 6: During a product review, an engineer says a feature is 'technically impossible.' How should a PM respond?
- Immediately remove the feature from the roadmap
- Accept the constraint and find an alternative solution or validate the claim with more context (Correct answer)
- Escalate to the CTO to override the engineer
- Push back and insist the team find a way
Correct answer: Accept the constraint and find an alternative solution or validate the claim with more context
PMs should explore constraints collaboratively — understanding WHY it's difficult often reveals alternative approaches or trade-offs worth considering.
Question 7: What is 'feature flagging' used for in product management?
- Marking deprecated features for removal in the next release
- Controlling feature visibility to specific users or groups without separate deployments (Correct answer)
- Flagging bugs reported by users in production
- A legal process for trademarking product features
Correct answer: Controlling feature visibility to specific users or groups without separate deployments
Feature flags let teams deploy code to production while controlling which users see a feature, enabling gradual rollouts, A/B tests, and instant kill switches.
What is the key difference between a 'leading indicator' and a 'lagging indicator' in product metrics?