Skip to content

Quiz: Product Management Foundations

Test your understanding of core PM vocabulary, frameworks, and strategic concepts with these review questions.

1. What are the four phases of the product lifecycle in the correct order?

  1. Introduction, Growth, Maturity, Decline
  2. Launch, Expansion, Optimization, Sunset
  3. Concept, Development, Deployment, Retirement
  4. Discovery, Validation, Scaling, Maintenance
Show Answer

The correct answer is A. The product lifecycle consists of four major phases: Introduction (focused on validating product-market fit), Growth (scaling the user base), Maturity (maximizing value through optimization), and Decline (managing the transition as the product loses relevance). Each phase demands different technical investments and PM priorities, as described in the chapter's lifecycle framework.

Concept Tested: Product Lifecycle

2. Which characteristic distinguishes a software product from a physical product according to the comparison table in this chapter?

  1. Software products require larger teams to develop
  2. Software products have near-zero marginal distribution cost
  3. Software products always generate higher revenue
  4. Software products are easier to design than physical products
Show Answer

The correct answer is B. The chapter's comparison table highlights several key differences between physical and software products. Among the most significant is that software products have near-zero marginal cost for distribution, compared to the significant per-unit cost of manufacturing and shipping physical goods. This enables global distribution through digital download and cloud delivery without the scaling costs that physical products face.

Concept Tested: Software Product

3. What does the term "technical literacy" mean in the context of a technical PM role?

  1. The ability to write production-quality code in at least one programming language
  2. The ability to understand and communicate about technology concepts at a level sufficient for effective collaboration with engineering teams
  3. The ability to design software architecture diagrams without assistance from engineers
  4. The ability to manage a team of software engineers and assign coding tasks
Show Answer

The correct answer is B. The chapter defines technical literacy as the ability to understand and communicate about technology concepts at a level sufficient for effective collaboration with engineering teams. This includes understanding how systems are built, how data flows through applications, what makes some technical approaches better than others, and how engineering constraints affect product decisions. It does not require writing production code.

Concept Tested: Technical Literacy

4. In the OKR framework, what is the role of Key Results?

  1. They are qualitative, inspirational goals that describe what you want to achieve
  2. They are 2-4 quantitative metrics that indicate whether you have achieved the objective
  3. They are the daily tasks engineers complete during a sprint
  4. They are the KPIs displayed on executive dashboards
Show Answer

The correct answer is B. The chapter explains that in the OKR (Objectives and Key Results) framework, Key Results are 2-4 quantitative metrics that indicate whether you have achieved the objective. Good key results are specific, time-bound, and measurable, so you can objectively determine whether you hit them. The Objective is the qualitative, inspirational goal, while Key Results provide the measurable evidence of progress.

Concept Tested: OKRs

5. Why does the chapter recommend that product roadmaps emphasize themes and outcomes rather than specific features and dates?

  1. Because stakeholders do not care about specific features
  2. Because engineering teams refuse to commit to fixed dates
  3. Because plans will evolve as the team learns more, and outcome-focused roadmaps accommodate that uncertainty
  4. Because themes are easier for marketing teams to communicate externally
Show Answer

The correct answer is C. The chapter states that modern roadmaps emphasize themes and outcomes over specific features and dates, acknowledging that plans will evolve as you learn more. This approach accommodates the inherent uncertainty in product development while still communicating priorities and expected milestones. It connects the product vision and strategy into a time-oriented plan without locking the team into commitments that may need to change.

Concept Tested: Product Roadmap

6. According to the stakeholder management framework, how should a PM communicate with a stakeholder who has high influence but low interest in the product?

  1. Manage closely with regular updates and proactive engagement
  2. Monitor with minimal effort
  3. Keep informed through newsletters, changelogs, and community forums
  4. Keep satisfied with periodic updates focused on their concerns
Show Answer

The correct answer is D. The chapter describes a stakeholder mapping framework with two dimensions: level of influence and level of interest. For stakeholders with high influence but low interest (such as a CFO or Legal team), the recommended strategy is to keep them satisfied with periodic updates focused on their specific concerns. This contrasts with high-influence, high-interest stakeholders who require close management with regular updates.

Concept Tested: Stakeholder Management

7. What are the four characteristics of good product metrics described in this chapter?

  1. Quantitative, qualitative, comparative, and predictive
  2. Simple, automated, real-time, and visual
  3. Actionable, accessible, auditable, and aligned
  4. Relevant, timely, accurate, and benchmarked
Show Answer

The correct answer is C. The chapter states that good product metrics share four characteristics: Actionable (the team can influence the metric through their work), Accessible (everyone on the team understands what it means), Auditable (the data source and calculation method are transparent), and Aligned (the metric connects to a strategic objective). These four criteria help teams choose metrics that drive better decisions rather than just tracking vanity numbers.

Concept Tested: Product Metrics

8. Which KPI is described as most relevant during the Growth phase of the product lifecycle?

  1. Lifetime Value (LTV)
  2. Monthly Active Users (MAU)
  3. Feature Adoption Rate
  4. Net Promoter Score (NPS)
Show Answer

The correct answer is B. The chapter's KPI table indicates that Monthly Active Users (MAU), which measures breadth of engagement, matters most during the Growth phase. While other KPIs like NPS and Feature Adoption Rate are relevant across all phases, and LTV is most important during the Maturity phase, MAU directly tracks the primary objective of the Growth phase: scaling the user base.

Concept Tested: Key Performance Indicators

9. A technical PM discovers that the engineering team is prioritizing scalability and infrastructure investments for a product that just launched its MVP two weeks ago and has only 50 users. Using the product lifecycle framework, what should the PM recommend?

  1. Support the engineering team's focus on scalability to prepare for future growth
  2. Redirect investment toward speed of iteration and validating product-market fit, since the product is in the Introduction phase
  3. Recommend equal investment in both scalability and new features to cover all bases
  4. Suggest pausing all development until user feedback is collected and analyzed
Show Answer

The correct answer is B. The chapter explains that each lifecycle phase demands different technical investments. During the Introduction phase, speed matters more than scalability because the priority is validating product-market fit, acquiring early adopters, and establishing core functionality. With only 50 users two weeks after MVP launch, the product is firmly in Introduction. The PM should advocate for the right engineering investments at the right time, redirecting focus toward rapid iteration.

Concept Tested: Product Lifecycle

10. Examining the relationship between product vision, product strategy, product roadmap, and sprint execution, which statement best describes how these elements connect?

  1. Each element operates independently, and teams choose which level to focus on based on their role
  2. They form a hierarchy from abstract to concrete, where vision guides strategy, strategy sets priorities for the roadmap, and the roadmap defines scope for execution
  3. The roadmap is the most important element because it directly determines what engineers build each week
  4. Vision and strategy are set once at company founding and remain unchanged, while the roadmap and execution adapt to market conditions
Show Answer

The correct answer is B. The chapter's "From Vision to Execution" framework describes a four-level hierarchy flowing from abstract to concrete. Product vision (3-5 year horizon) guides direction for product strategy (1-2 years), which sets priorities for the product roadmap (quarter to year), which defines scope for sprint execution (1-2 weeks). The chapter also notes that learnings flow upward through feedback arrows, informing strategy based on execution insights. This creates a coherent hierarchy from aspiration to execution.

Concept Tested: Product Vision