PREMIUM STUDY GUIDE

PRODUCT MANAGEMENT
The Complete Guide to the Product Manager Role

Definitions • Frameworks • Metrics • Case Studies • Exam Preparation

Undergraduate & Postgraduate Study Notes

Suitable for BBA / MBA / BCom / MCom / PGDM / Product Management Courses

Compiled as an Academic Reference — 2026 Edition

 Product Management — Premium Study Guide

Table of Contents
(Right-click the list below and choose "Update Field" in Word to refresh page numbers.)

TOC \h \o "1-3"

Page 2 of 40
 Product Management — Premium Study Guide

Chapter 1: Introduction to Product Management

1.1 Simple Definition

DEFINITION
A Product Manager (PM) is the professional who identifies customer needs and business goals that a product or
feature will satisfy, defines what should be built, and works with engineering, design, marketing, and sales teams
to bring that product to life and make it successful in the market.

In one line: A Product Manager decides WHAT to build and WHY, while engineers decide HOW to build it. The
Product Manager does not usually write code or design pixels; instead, the PM acts as the bridge between
customers, business strategy, and the technical team that builds the solution.

1.2 Meaning in Easy Language

Imagine a company wants to build a mobile banking app. Someone has to answer questions such as: Which
features should the app have first? Who are we building this for? What problem are we solving? How will we
know if it is successful? That 'someone' is the Product Manager.

The Product Manager is often described using the phrase "CEO of the Product". This does not mean the PM has
formal authority over people the way a CEO does over a company. It means the PM feels the same level of
ownership and responsibility for the product's success — even though the PM must influence and persuade
people (engineers, designers, marketers, sales staff) rather than directly command them, because those people
usually report to other managers, not to the PM.

A simple way to remember the PM's job is the three-circle model: the PM sits at the intersection of Business (is it
viable and profitable?), Technology (is it feasible to build?), and User Experience (is it desirable and usable?). A
good product idea must satisfy all three circles at once.

Fig 1.1 — The Product Management Sweet Spot

______________
/
BUSINESS \
/ (Viable) \
( ___________\_______
\ / \
\ / PRODUCT \
\ / MANAGER \
\/ (Sweet Spot) )
/\ /
/ \ /
TECHNOLOGY ( \____________________/ ) USER EXPERIENCE
(Feasible) \ / (Desirable)
\___________________________/

The PM's core job is to find ideas that are simultaneously desirable to users, feasible for engineering, and viable for the
business.

Page 3 of 40
 Product Management — Premium Study Guide

1.3 Background and Introduction

The discipline of product management traces its roots to 1931, when Neil H. McElroy, a marketing executive at
Procter & Gamble, wrote a famous internal memo proposing that individual 'brand men' should be assigned full
responsibility for a single product's performance — from research to advertising to sales results. This is widely
regarded as the birth of modern brand/product management.

The concept evolved through the mid-20th century in consumer packaged goods (CPG) companies such as P&G
and Unilever, where Brand Managers owned the profit and loss (P&L) of a product line.

With the rise of the software and technology industry in the 1980s-2000s, the role transformed. Companies like
Microsoft, HP, and later Google, Facebook (Meta), and Amazon adapted the concept for digital products,
creating the modern Technical/Digital Product Manager role that focuses on features, user experience, data, and
rapid iteration rather than physical goods and advertising campaigns.

Today, product management is one of the most sought-after careers in the global technology industry, and the
discipline has expanded into a formal body of knowledge taught in business schools, with certifications,
frameworks, and dedicated career ladders (Associate PM → PM → Senior PM → Group PM → Director → VP →
Chief Product Officer).

1.4 Why Product Management Is Important

Product management matters because it aligns three groups that otherwise pull in different directions: customers
(who want their problems solved), the business (which wants growth and profit), and engineering (which wants
clear, buildable requirements). Without this alignment role, companies waste resources building things nobody
wants.

• Prevents wasted engineering effort: Without a PM validating ideas first, expensive engineering time can be
spent building features that customers never use.
• Keeps the company customer-centric: PMs continuously talk to users and analyse data, ensuring decisions
are based on evidence, not opinions.
• Connects strategy to execution: PMs translate a company's high-level vision (e.g., "become the leading
fintech app in India") into a concrete, prioritised list of features and releases.
• Drives measurable business outcomes: PMs are responsible for metrics such as revenue, retention, and
engagement, not just for shipping features.
• Balances competing stakeholder interests: Sales wants a feature for one big client; engineering wants to fix
technical debt; the CEO wants a new market. The PM prioritises objectively.
• Reduces risk in new product launches: Through frameworks like MVP (Minimum Viable Product) testing,
PMs validate ideas cheaply before large-scale investment.

1.5 Key Stakeholders a PM Works With

Stakeholder What the PM Needs From Them What They Need From the PM

Feasibility estimates, technical Clear requirements, prioritised

Engineering / Developers
trade-offs backlog, timely decisions

User flows, prototypes, usability User research insights, business

UX / UI Designers
testing constraints, feedback

Marketing Go-to-market plans, positioning Product messaging, target

Page 4 of 40
 Product Management — Premium Study Guide

Stakeholder What the PM Needs From Them What They Need From the PM

support audience, launch timelines

Customer/market feedback, deal Product roadmap visibility,

Sales
requirements competitive positioning

Recurring issues, customer pain Fixes, FAQs, early access to

Customer Support
points upcoming changes

Progress reports, business impact of

Leadership / Executives Strategic direction, budget approval
the roadmap

A product that solves their real

Customers / Users Feedback, usage data, pain points
problems

Memory Tip

MNEMONIC — "BEST" Stakeholders

Business leaders, Engineering, Sales & Support, Target users (customers) — the four groups every PM must keep
aligned every single day.

Page 5 of 40
 Product Management — Premium Study Guide

Chapter 2: Role, Responsibilities, Skills, and Types of Product

Managers

2.1 Core Responsibilities of a Product Manager

A Product Manager's responsibilities span the entire product lifecycle, from the first spark of an idea to its
retirement from the market. The exact duties vary by company size and industry, but the following are common
everywhere:

• Market and user research: Conducting interviews, surveys, and competitive analysis to understand
customer pain points and market gaps.
• Defining product vision and strategy: Setting a long-term direction for the product that supports overall
business goals.
• Writing requirements: Creating Product Requirement Documents (PRDs), user stories, and acceptance
criteria that engineers and designers can build from.
• Prioritisation: Deciding what gets built next using frameworks such as RICE, MoSCoW, or the Kano Model
(explained in Chapter 4).
• Roadmap ownership: Maintaining a time-phased plan of upcoming features and releases, and
communicating it to stakeholders.
• Cross-functional leadership: Coordinating designers, engineers, QA testers, marketers, and support staff
without having direct authority over them (this is called "leading through influence").
• Go-to-market planning: Working with marketing and sales to plan the launch, pricing, and positioning of
the product.
• Data analysis and metrics tracking: Monitoring KPIs such as adoption, retention, churn, and revenue, and
making data-driven decisions.
• Post-launch iteration: Gathering feedback after launch and planning the next improvement cycle.

2.2 Skills Required to Become a Successful PM

(a) Hard / Technical Skills
• Data analysis (SQL, Excel, analytics tools such as Google Analytics, Mixpanel, Amplitude)
• Basic technical literacy (APIs, databases, software development lifecycle) — enough to talk credibly with
engineers
• Wireframing and prototyping tools (Figma, Balsamiq)
• Project/roadmap tools (Jira, Trello, Asana, Productboard)
• A/B testing and experimentation design
• Financial literacy — understanding P&L, unit economics, and pricing

(b) Soft Skills

• Communication and storytelling — explaining complex ideas simply to different audiences
• Empathy — genuinely understanding user pain points
• Negotiation and influence without authority

Page 6 of 40
 Product Management — Premium Study Guide

• Critical thinking and structured problem-solving

• Prioritisation and decisiveness under uncertainty
• Leadership and stakeholder management

REMEMBER
The best PMs are often called "T-shaped" professionals: they have a broad general understanding across business,
design, technology, and data (the top of the T), combined with deep expertise in one or two of these areas (the
stem of the T).

2.3 Product Manager vs Related Roles (Comparison Table)

Students frequently confuse the Product Manager role with similar-sounding titles. The table below clarifies the
differences, which is a very common exam question.

Role Primary Focus Key Question Answered Typical Scope

Strategy, vision,
"Are we building the right
Product Manager (PM) What to build and why prioritisation for a
thing?"
product

Tactical execution
Backlog management in "What should the team build
Product Owner (PO) within one Scrum
Agile/Scrum next sprint?"
team

Delivery of a
Timelines, budget, resources, "Are we building the thing on defined project
Project Manager
execution time and on budget?" with a start and
end

Cross-project/
Coordinating multiple related "Are all these related projects
Program Manager cross-team
projects moving together?"
coordination

Go-to-market and
Product Marketing Manager Positioning, messaging, "How do we tell the market
communication
(PMM) launch about it?"
strategy

Design of screens,
User interface and
UX Designer "How should it look and feel?" flows, and
experience design
interactions

Exam Tip: A very common mistake is treating "Product Owner" and "Product Manager" as identical. In many
organisations (especially large ones using Scrum) the Product Owner is a specific Agile role focused on the sprint
backlog, while the Product Manager owns the broader strategy — sometimes the same person does both jobs in
smaller companies, but conceptually they are distinct.

2.4 Types / Classifications of Product Managers

As the profession has matured, several specialised types of PM roles have emerged. Each has a distinct focus,
though the core skill set overlaps.

Page 7 of 40
 Product Management — Premium Study Guide

Type Definition Typical Focus Area Example

A PM with strong engineering

Backend systems, PM for a cloud
Technical Product background who manages highly
developer tools, computing API at
Manager (TPM) technical products, APIs, or
platforms AWS
infrastructure.

PM optimising
Focuses on user acquisition, activation,
Funnels, A/B tests, sign-up
Growth Product Manager retention, and revenue growth using
virality loops conversion at a
experimentation.
SaaS company

Builds internal or external PM for Stripe's

Reusable infrastructure,
Platform Product Manager platforms/APIs used by other teams or payment API
developer experience
third-party developers. platform

Manages products sold to businesses;

Enterprise needs, PM for
must handle enterprise sales cycles,
B2B Product Manager compliance, Salesforce CRM
contracts, and fewer but larger
customisation modules
customers.

Manages products used directly by PM for an app

Consumer psychology,
B2C Product Manager individual consumers; focuses on mass- like Instagram or
scale, virality
market UX and engagement. Swiggy

Data pipelines, machine PM for a

Manages data platforms, analytics
Data Product Manager learning models, recommendatio
products, or AI/ML-driven features.
dashboards n engine

A rapidly growing 2025-2026 role Prompt design, model PM for an AI

AI Product Manager managing products built around evaluation, responsible chatbot assistant
generative AI and LLMs. AI feature

An entry-level PM role, often via Fresh graduate

Associate Product Learning the craft under
structured rotational programmes (e.g., joining a big-tech
Manager (APM) mentorship
Google APM Program). APM programme

The most senior product leader, owning Head of Product

Chief Product Officer Company-wide product
product strategy across the entire reporting to the
(CPO) vision and P&L
organisation. CEO

Memory Tip

MNEMONIC — "GTBD" Types

Growth, Technical, B2B/B2C, Data/AI — the four broad flavours of specialised PM roles you are most likely to be
asked about in exams.

Page 8 of 40
 Product Management — Premium Study Guide

Chapter 3: Product Life Cycle and the Product Development

Process

3.1 Product Life Cycle (PLC) — Definition

DEFINITION
The Product Life Cycle is a model describing the stages a product passes through, from its introduction into the
market, through growth and maturity, to eventual decline — and the strategic actions a Product Manager should
take at each stage.

Understanding which stage a product is in helps the PM decide whether to invest in awareness building,
aggressive growth, defending market share, or planned retirement (sunsetting).

Fig 3.1 — The Product Life Cycle Curve

Sales/Revenue
| ____________
| ,-' MATURITY `-.
| ,-' `-.
| ,-' `-. DECLINE
| ,-' GROWTH `-.
| ,-' `-.
,-' |
| ,-'
|,-' INTRODUCTION
+-------------------------------------------------------------> Time

Revenue is low and slow during Introduction, rises sharply in Growth, plateaus in Maturity, and falls in Decline.

Stage Characteristics PM's Strategic Focus Example

Low sales, high marketing cost, few A newly

Validate product-market fit, gather
Introduction competitors, product awareness launched
early feedback, MVP iteration
building fintech app

A food
Rapid sales increase, growing Scale infrastructure, add features, delivery app
Growth
competition, brand building expand marketing, acquire users fast expanding to
new cities

WhatsApp in
Sales peak and stabilise, intense Differentiate, optimise retention, mature
Maturity
competition, price pressure defend market share, improve margins messaging
markets

Older
feature
Falling sales, reduced demand, Harvest revenue, cut costs, or
Decline phones after
possible obsolescence sunset/replace the product
smartphone
s arrived

Page 9 of 40
 Product Management — Premium Study Guide

3.2 The Product Development Process (Idea to Launch)

While the Product Life Cycle explains the market journey of a product, the Product Development Process
explains the internal workflow a PM follows to actually build and ship something. Most modern PM teams follow
a version of the flow below.

Fig 3.2 — Product Development Workflow

[1] Discover [2] Define [3] Prioritise
Idea/Problem --> PRD & user --> RICE / MoSCoW
Research stories scoring
| |
v v
[6] Measure <-- [5] Launch <-- [4] Design & Build
KPIs, feedback GTM plan, Wireframes, dev,
loop back to [1] release QA testing

This is a continuous loop, not a one-time line — insights from Measure feed back into the next Discovery phase.

Step-by-Step Explanation
• 1. Discover: The PM identifies a customer problem or business opportunity through user interviews,
surveys, support tickets, sales feedback, and market/competitor research.
• 2. Define: The PM writes a clear problem statement, a Product Requirement Document (PRD), user stories
("As a ___, I want ___, so that ___"), and success metrics.
• 3. Prioritise: Since resources are limited, the PM ranks competing ideas using frameworks such as RICE or
MoSCoW (Chapter 4) and builds a roadmap.
• 4. Design & Build: Designers create wireframes/prototypes; engineers estimate effort and build the
feature; QA tests it against acceptance criteria.
• 5. Launch: The PM coordinates a Go-To-Market (GTM) plan with marketing, sales enablement, and support
documentation, then releases the feature (often to a small % of users first).
• 6. Measure & Iterate: The PM tracks KPIs (adoption, retention, revenue impact), gathers qualitative
feedback, and feeds learnings back into the next Discover phase — this is why product development is
described as a continuous, iterative loop rather than a straight line.

3.3 Common Mistakes at This Stage

• Skipping discovery: Jumping straight to building a solution without validating that the problem is real and
significant enough.
• Feature-factory mindset: Measuring success by number of features shipped rather than by
business/customer outcomes achieved.
• No success metrics defined before launch: Making it impossible to objectively evaluate whether the launch
worked.
• Ignoring the decline stage: Continuing to invest heavily in a product long after the market has moved on,
instead of sunsetting or pivoting.

Page 10 of 40
 Product Management — Premium Study Guide

Chapter 4: Product Management Frameworks and Models (Part

A — Prioritisation)
Because a PM always has far more ideas than resources to build them, prioritisation frameworks are among the
most heavily tested topics in product management courses. This chapter covers each major framework in the
required format: Definition, Features, Advantages, Disadvantages, Applications, and Example.

4.1 RICE Scoring Model

DEFINITION
RICE is a quantitative prioritisation framework that scores each feature idea on four factors — Reach, Impact,
Confidence, and Effort — to produce a single comparable score.

Features
• Reach: How many users/customers will this impact in a given time period (e.g., per quarter)?
• Impact: How much will it move the needle for each user, usually scored on a scale (3 = massive, 2 = high, 1
= medium, 0.5 = low, 0.25 = minimal).
• Confidence: How sure are you about your Reach and Impact estimates, expressed as a percentage (100%,
80%, 50%).
• Effort: Estimated person-months required from design and engineering to deliver the idea.

Advantages
• Brings objectivity and reduces political/opinion-based prioritisation.
• Easy to compare very different types of ideas on one scale.
• Forces the team to explicitly state assumptions (which can later be tested).

Disadvantages
• Scores can still be subjective/guessed if data is unavailable.
• Can undervalue strategic "big bet" projects that have low near-term reach but high long-term value.
• Effort estimates from engineering can be imprecise early on.

Applications
• Sprint and quarterly roadmap planning.
• Comparing a long backlog of small feature requests.

Example
A checkout-page redesign might score: Reach = 8,000 users/quarter, Impact = 2 (high), Confidence = 80%, Effort =
4 person-months. RICE Score = (8000 × 2 × 0.8) / 4 = 3,200. This number can then be compared directly against
the RICE score of a completely different idea, such as adding a new payment method.

Page 11 of 40
 Product Management — Premium Study Guide

4.2 MoSCoW Method

DEFINITION
MoSCoW is a qualitative prioritisation technique that sorts requirements into four buckets: Must have, Should
have, Could have, and Won't have (this time).

Features
• Must have: Non-negotiable requirements — the product fails or is unusable/illegal without them.
• Should have: Important but not vital; the product works without them, though with reduced value.
• Could have: Desirable "nice-to-have" items with small impact if left out.
• Won't have (this time): Explicitly agreed to be out of scope for the current release, preventing scope creep.

Advantages
• Very simple and fast to communicate to non-technical stakeholders.
• Creates clear, shared expectations about what is guaranteed to ship.
• Useful when time is fixed (e.g., a hard launch deadline) and scope must flex.

Disadvantages
• Not quantitative — no numeric score to compare two "Must have" items against each other.
• Stakeholders often try to label everything "Must have", diluting the technique's usefulness.

Applications
• Fixed-deadline releases (e.g., a regulatory compliance deadline).
• Scoping a Minimum Viable Product (MVP).

Example
For a hospital appointment-booking app launch: Must have = book/cancel appointment; Should have = SMS
reminders; Could have = doctor ratings; Won't have (this time) = video consultation, deferred to a later release.

4.3 Kano Model

DEFINITION
The Kano Model, developed by Professor Noriaki Kano in the 1980s, classifies product features based on how they
affect customer satisfaction, plotting Investment/Functionality against Customer Satisfaction.

Fig 4.1 — Kano Model Chart

Satisfaction
^
| Delighters
| .-' (Excitement)
| .-'
| Performance
| (More = Better) ------> Functionality

Page 12 of 40
 Product Management — Premium Study Guide

|______________________
| Basic/Must-be
| (Expected, invisible
| when present, painful
| when absent)

Features (Categories)
• Basic/Must-be needs: Expected baseline features. Users don't notice them when present but are very
dissatisfied when absent (e.g., a banking app that doesn't crash).
• Performance needs: Satisfaction increases linearly with how well the feature is delivered (e.g., faster page-
load speed).
• Delighters/Excitement needs: Unexpected features that create disproportionate delight when present, but
no dissatisfaction when absent (e.g., a surprise cashback offer).
• Indifferent needs: Features that customers do not care about either way.

Advantages
• Helps teams avoid over-investing in features customers take for granted.
• Encourages a healthy mix of reliability (basics) and differentiation (delighters).

Disadvantages
• Requires structured customer surveys (the Kano questionnaire), which take time and resources.
• Customer expectations shift over time — today's delighter becomes tomorrow's basic need (e.g., GPS
navigation in ride-hailing apps).

Applications
• Deciding which features differentiate a product from competitors.
• Balancing a roadmap between "keep the lights on" work and innovative bets.

Example
For a food delivery app: real-time order tracking is now a Basic need; faster average delivery time is a
Performance need; a free surprise dessert on a birthday order is a Delighter.

4.4 Comparison: RICE vs MoSCoW vs Kano

Framework Type Best Used For Output

A numeric score for

RICE Quantitative Ranking many diverse backlog items
each idea

MoSCoW Qualitative Fixed-deadline scope negotiation Four labelled buckets

Categorisation
Customer-perception
Kano Model Deciding feature type/investment mix (Basic/Performance/Del
based
ighter)

Memory Tip

MNEMONIC

Page 13 of 40
 Product Management — Premium Study Guide

"Rich Managers Know Priorities" → RICE, MoSCoW, Kano, Prioritisation — the three big prioritisation frameworks
in order of how often they appear in exams.

Page 14 of 40
 Product Management — Premium Study Guide

Chapter 4 (Part B): Strategic Analysis Models Used in Product

Management
Beyond deciding which feature to build next, a Product Manager must also set broader strategy — deciding
which markets to enter, how to position against competitors, and where to invest company resources. The
following classic strategy models are frequently used by PMs and are common exam topics.

4.5 SWOT Analysis

DEFINITION
SWOT Analysis is a strategic planning framework that evaluates a product/company's internal Strengths and
Weaknesses, along with external Opportunities and Threats.

Fig 4.2 — SWOT Matrix

HELPFUL HARMFUL
+------------------+------------------+
INTERNAL | STRENGTHS | WEAKNESSES |
| (advantages) | (limitations) |
+------------------+------------------+
EXTERNAL | OPPORTUNITIES | THREATS |
| (favourable | (external risks) |
| trends) | |
+------------------+------------------+

Features
• Strengths and Weaknesses come from inside the organisation (controllable).
• Opportunities and Threats come from the external market environment (largely uncontrollable).

Advantages
• Simple, quick, and requires no special tools or data.
• Works at product, team, or company level.
• Good communication tool for aligning stakeholders on strategic context.

Disadvantages
• Very generic; can produce vague, unprioritised lists without disciplined facilitation.
• Does not by itself tell you what action to take — needs to be paired with a decision framework.

Applications
• Early-stage strategic planning before entering a new market.
• Annual product strategy reviews.

Page 15 of 40
 Product Management — Premium Study Guide

Example
A ride-hailing startup's SWOT might show: Strength = strong local driver network; Weakness = limited cash
reserves; Opportunity = government push for EV adoption; Threat = a well-funded global competitor entering the
market.

4.6 Porter's Five Forces

DEFINITION
Developed by Michael Porter (1979), this model analyses the competitive intensity and attractiveness of an
industry through five forces: Competitive Rivalry, Threat of New Entrants, Threat of Substitutes, Bargaining
Power of Suppliers, and Bargaining Power of Buyers.

Fig 4.3 — Porter's Five Forces

Threat of New Entrants
|
v
Bargaining Power --> COMPETITIVE <-- Bargaining Power
of Suppliers RIVALRY of Buyers
^
|
Threat of Substitute Products

Features / Components
• Competitive Rivalry: Intensity of competition among existing players in the industry.
• Threat of New Entrants: How easily new competitors can enter the market (barriers to entry).
• Threat of Substitutes: Availability of alternative solutions to the same customer problem.
• Bargaining Power of Suppliers: How much control suppliers have over price/quality of inputs.
• Bargaining Power of Buyers: How much control customers have to demand lower prices or better quality.

Advantages
• Provides a structured, holistic view of industry attractiveness before launching a product.
• Helps identify where to build defensible competitive advantage (a "moat").

Disadvantages
• Assumes a relatively stable industry structure — less effective in fast-changing digital markets.
• Static snapshot; does not capture how forces evolve over time.

Applications
• Deciding whether to enter a new industry or product category.
• Informing competitive/pricing strategy.

Example
For a new electric-scooter-sharing product: high threat of new entrants (low capital barriers in some cities) and
high buyer power (customers can easily switch apps) suggest the company must build loyalty through pricing and
city-level network effects.
Page 16 of 40
 Product Management — Premium Study Guide

4.7 BCG (Growth-Share) Matrix

DEFINITION
Created by the Boston Consulting Group, this model classifies a company's product portfolio into four categories
based on market growth rate and relative market share.

Fig 4.4 — BCG Matrix

High |------------------------|------------------------|
Market | STAR | QUESTION MARK |
Growth | (high growth, | (high growth, |
Rate | high share) | low share) |
|------------------------|------------------------|
| CASH COW | DOG |
Low | (low growth, | (low growth, |
| high share) | low share) |
|------------------------|------------------------|
High Low
Relative Market Share

Features (Quadrants)
• Stars: High growth, high market share — invest heavily to maintain leadership (e.g., a fast-growing flagship
product).
• Cash Cows: Low growth, high market share — mature products generating stable profit; "milk" them to
fund other products.
• Question Marks: High growth, low market share — uncertain; decide whether to invest more or divest.
• Dogs: Low growth, low market share — usually candidates for discontinuation or sunsetting.

Advantages
• Useful for allocating resources across a multi-product portfolio.
• Simple, visual, and widely understood by executives.

Disadvantages
• Oversimplifies strategy to just two dimensions, ignoring synergies between products.
• Market share and growth data can be hard to measure precisely.

Applications
• Portfolio-level strategic reviews in large multi-product companies.

Example
At a company like Google/Alphabet: Search/Ads is a Cash Cow; Google Cloud may be treated as a Star or
Question Mark; declining legacy products can be Dogs slated for sunset.

4.8 Ansoff Matrix

DEFINITION

Page 17 of 40
 Product Management — Premium Study Guide

The Ansoff Matrix (H. Igor Ansoff, 1957) is a strategic planning tool that maps four growth strategies along two
dimensions: new vs existing products and new vs existing markets.

Existing Products New Products

Market Penetration — sell more of the same Product Development — create new products
Existing Markets
product to current customers for current customers

Market Development — take the existing Diversification — new products in new

New Markets
product to new markets/segments markets (highest risk)

Advantages
• Clarifies the risk level of different growth strategies (penetration is lowest risk; diversification is highest).
• Helps a PM decide where the next big investment should go.

Disadvantages
• Does not account for competitive response or execution capability.
• Binary "new vs existing" framing can oversimplify partially-new markets/products.

Applications
• Deciding whether to expand a product to a new country, or build an entirely new product line.

Example
A food-delivery app practising Market Penetration by offering loyalty discounts to existing users; the same
company practising Diversification by launching a completely new grocery-delivery product in a new city.

Memory Tip

MNEMONIC
"Smart PMs Build Advantage" → SWOT, Porter's Five Forces, BCG Matrix, Ansoff Matrix — the four classic strategy
tools every PM should recall together.

Page 18 of 40
 Product Management — Premium Study Guide

Chapter 4 (Part C): Process and Methodology Frameworks

4.9 Design Thinking

DEFINITION
Design Thinking is a human-centred, iterative problem-solving methodology with five stages: Empathise, Define,
Ideate, Prototype, and Test, popularised by the design firm IDEO and Stanford's [Link].

Fig 4.5 — Design Thinking Cycle

Empathise --> Define --> Ideate --> Prototype --> Test
^ |
|_________________________________________________|
(iterate based on findings)

Features
• Empathise: Deeply understand users through observation and interviews.
• Define: Synthesise research into a clear problem statement.
• Ideate: Brainstorm a wide range of possible solutions without judging them early.
• Prototype: Build quick, low-cost mock-ups of the top ideas.
• Test: Get real user feedback on the prototype and iterate.

Advantages
• Keeps solutions grounded in real user needs rather than assumptions.
• Encourages creative, out-of-the-box ideation before narrowing down.
• Cheap to fail fast at the prototype stage rather than after full development.

Disadvantages
• Can feel slow/unstructured for teams under tight deadlines.
• Requires facilitation skill and genuine user access, which not all teams have.

Applications
• New product or feature ideation.
• Redesigning a poor user experience.

Example
A hospital app team observes that elderly patients struggle to book appointments (Empathise), defines the
problem as "low-literacy users need a simpler booking flow" (Define), brainstorms voice-based booking (Ideate),
builds a paper/clickable prototype (Prototype), and tests it with real elderly users (Test).

Page 19 of 40
 Product Management — Premium Study Guide

4.10 Agile and Scrum

DEFINITION
Agile is a set of values and principles (from the 2001 Agile Manifesto) for iterative, incremental software
development. Scrum is the most popular framework implementing Agile, organising work into fixed time-boxed
iterations called Sprints (usually 1-4 weeks).

Features
• Product Backlog: A prioritised list of all desired work, owned by the Product Owner/PM.
• Sprint Planning: The team selects backlog items to complete in the upcoming sprint.
• Daily Stand-up: A short daily sync on progress and blockers.
• Sprint Review: Demonstrating completed work to stakeholders at the end of the sprint.
• Sprint Retrospective: The team reflects on what went well and what to improve.

Advantages
• Delivers working software frequently, allowing fast feedback and course correction.
• Increases transparency and team accountability.
• Adapts well to changing requirements compared to rigid "waterfall" planning.

Disadvantages
• Can lead to short-term thinking if long-term vision/roadmap is neglected.
• Requires disciplined ceremonies; poorly run Scrum becomes just meetings without real agility.

Applications
• Software product development teams of almost every size.

Example
A PM maintains a backlog of 40 items; the team picks the top 8 for a two-week sprint, holds daily 15-minute
stand-ups, demos the finished features to stakeholders on Friday, and discusses process improvements in the
retrospective.

4.11 Lean Startup and Minimum Viable Product (MVP)

DEFINITION
The Lean Startup methodology (Eric Ries, 2011) advocates building a Minimum Viable Product (MVP) — the
smallest version of a product that lets the team test a core hypothesis with real customers — and iterating through
a Build-Measure-Learn feedback loop.

Fig 4.6 — Build-Measure-Learn Loop

BUILD -------------> MEASURE
^ (create MVP) |
| | (collect data)
| v

Page 20 of 40
 Product Management — Premium Study Guide

'------------- LEARN <---'

(validated learning informs next build)

Features
• Focus on validated learning over polished features.
• Encourages hypothesis-driven development ("we believe X will happen; we will know we are right if Y").
• MVP can be as simple as a landing page, a manual/concierge process, or a basic working prototype.

Advantages
• Reduces wasted investment on unvalidated ideas.
• Speeds up time-to-market and learning cycles.
• Well suited to high-uncertainty, early-stage environments (startups, new markets).

Disadvantages
• A poorly designed MVP can give a bad first impression and hurt brand trust.
• Risk of over-simplifying and missing what actually makes the product valuable.

Applications
• Startup product validation.
• Testing a risky new feature inside an established product before full investment.

Example
Before building a full grocery-delivery app, a company might first test demand with a simple WhatsApp-based
ordering process (an MVP) to learn if customers actually want the service before investing in app development.

4.12 Jobs-To-Be-Done (JTBD) Framework

DEFINITION
Jobs-To-Be-Done, popularised by Clayton Christensen, states that customers don't simply buy products — they
"hire" products to get a specific job done in their life, and understanding that underlying job (functional,
emotional, and social) is key to building the right product.

Features
• Focuses on the customer's underlying motivation/goal rather than surface-level feature requests.
• Distinguishes between functional job (the practical task), emotional job (how they want to feel), and social
job (how they want to be perceived).

Advantages
• Reveals real, sometimes surprising, competitors (e.g., a milkshake competes with a banana or a boring
commute snack, per Christensen's famous study).
• Helps identify unmet needs even when customers can't articulate them directly.

Page 21 of 40
 Product Management — Premium Study Guide

Disadvantages
• Requires skilled, in-depth qualitative interviewing, which is time-consuming.
• Harder to quantify than data-driven frameworks like RICE.

Applications
• Early product discovery and positioning.
• Identifying whitespace opportunities competitors have missed.

Example
Customers don't just "buy a drill" — the job they are hiring it for is "make a hole in the wall," which is why some
companies now sell holes as a service or wall-mounting kits instead of the drill itself.

Memory Tip

MNEMONIC
"Designers Always Love Jobs" → Design Thinking, Agile/Scrum, Lean Startup/MVP, Jobs-To-Be-Done — the four
process/methodology frameworks in this section.

Page 22 of 40
 Product Management — Premium Study Guide

Chapter 4 (Part D): Growth and Goal-Setting Frameworks

4.13 AARRR — Pirate Metrics

DEFINITION
AARRR, coined by investor Dave McClure, is a growth framework that breaks the customer journey into five
measurable stages: Acquisition, Activation, Retention, Referral, and Revenue (the name "Pirate Metrics" comes
from the sound "Aaarrr!").

Fig 4.7 — AARRR Funnel

ACQUISITION ---->
How do users find us?
|
ACTIVATION ----> Do they have a great first experience?
|
RETENTION ----> Do they come back again?
|
REFERRAL ----> Do they tell others about us?
|
REVENUE ----> Do they pay us / generate income?

Features
• Acquisition: Channels through which new users discover the product (SEO, ads, referrals, social).
• Activation: Whether a new user experiences the product's core value quickly ("Aha moment").
• Retention: Whether users return and keep using the product over time.
• Referral: Whether existing users bring in new users (virality, word-of-mouth).
• Revenue: Whether user activity converts into money for the business.

Advantages
• Gives a simple, end-to-end lens on the entire customer lifecycle.
• Helps teams identify exactly where the biggest funnel drop-off ("leaky bucket") is happening.

Disadvantages
• Treats the journey as fairly linear, while real user behaviour can be non-linear or cyclical.
• Can over-emphasise acquisition growth while under-emphasising retention, which is usually more valuable
long-term.

Applications
• Growth PM roles; diagnosing where a product's growth funnel is leaking.

Example
A subscription app might discover that Acquisition and Activation are strong (many people sign up and try it), but
Retention is weak (most churn after week one) — pointing the team toward onboarding and habit-formation
improvements rather than more ad spend.

Page 23 of 40
 Product Management — Premium Study Guide

4.14 OKRs (Objectives and Key Results)

DEFINITION
OKRs is a goal-setting framework (popularised by Intel and later Google) consisting of a qualitative Objective (an
ambitious, inspiring goal) paired with 2-5 quantitative Key Results (measurable outcomes that indicate the
objective has been achieved).

Features
• Objective: Qualitative, memorable, and time-bound (e.g., "Delight our new users").
• Key Results: Specific, measurable, usually numeric targets (e.g., "Increase week-1 retention from 40% to
55%").
• Often set at company, team, and individual levels, cascading downward.

Advantages
• Aligns everyone in the company around a shared, measurable definition of success.
• Encourages ambitious ("moonshot") goals rather than sandbagging.
• Makes it easy to see, at a glance, whether initiatives actually delivered results.

Disadvantages
• Can become a rigid, bureaucratic exercise if not tied to real strategic thinking.
• Setting Key Results poorly (vanity metrics) undermines the whole system.

Applications
• Quarterly/annual strategic planning at company and team level.

Example
Objective: "Become the most trusted online payments product in our market." Key Results: (1) Reduce failed-
transaction rate from 3% to 1%; (2) Achieve an app-store rating of 4.6+; (3) Increase repeat-payment users by
25%.

4.15 North Star Metric (NSM)

DEFINITION
The North Star Metric is the single metric that best captures the core value a product delivers to customers, and
which is believed to best predict the company's long-term sustainable growth.

Features
• Must reflect real customer value, not just company revenue (revenue is a lagging outcome, not the NSM
itself).
• Should be leading (predictive of future growth), measurable, and actionable by product teams.
• Usually broken down into supporting input metrics that teams can directly influence.

Page 24 of 40
 Product Management — Premium Study Guide

Advantages
• Focuses the whole company on one unifying, customer-centred number instead of siloed departmental
metrics.
• Makes trade-off decisions easier — "does this initiative move our North Star?"

Disadvantages
• Choosing the wrong North Star Metric can misdirect the entire organisation.
• A single metric may oversimplify a complex, multi-sided business.

Applications
• Company-wide product strategy and metric alignment.

Example
Airbnb's North Star Metric is often cited as "nights booked"; Spotify's is "time spent listening"; Facebook's early
North Star was "daily active users." Each reflects genuine value delivered, not just revenue.

4.16 Summary Table — All Frameworks at a Glance

Framework Category One-Line Purpose

RICE Prioritisation Score features by Reach x Impact x Confidence / Effort

MoSCoW Prioritisation Bucket requirements as Must/Should/Could/Won't

Kano Model Prioritisation Classify features as Basic, Performance, or Delighter

Assess internal Strengths/Weaknesses & external

SWOT Strategy
Opportunities/Threats

Porter's Five Forces Strategy Analyse industry competitiveness

Classify products as Stars, Cash Cows, Question Marks,

BCG Matrix Strategy/Portfolio
Dogs

Ansoff Matrix Strategy/Growth Choose a growth path across products x markets

Design Thinking Process Human-centred 5-stage innovation process

Agile/Scrum Process Iterative delivery in fixed sprints

Lean Startup/MVP Process Build-Measure-Learn to validate ideas cheaply

Jobs-To-Be-Done Discovery Understand the real job customers hire a product for

AARRR Growth/Metrics Track Acquisition to Revenue funnel

OKRs Goal-setting Align teams via Objectives and Key Results

North Star Metric Goal-setting One metric reflecting core customer value

Page 25 of 40
 Product Management — Premium Study Guide

Chapter 5: Key Product Metrics, Formulas, and Worked

Numerical Examples
Product Managers are expected to be comfortable with quantitative reasoning. This chapter lists the most
important formulas a PM must know, explains every variable, states when to use each formula, and works
through five solved examples ranging from easy to difficult.

5.1 Important Formulas

FORMULA 1 — RICE Score

RICE Score = (Reach x Impact x Confidence) / Effort
Reach = number of users affected per time period
Impact = effect per user (0.25 to 3 scale)
Confidence = certainty in estimate, as a decimal (e.g., 80% = 0.8)
Effort = person-months of work required
Use when: comparing many different feature ideas on one common scale.

FORMULA 2 — Net Promoter Score (NPS)

NPS = %Promoters − %Detractors
Promoters = customers scoring 9-10 (on a 0-10 'would you recommend us' question)
Passives = customers scoring 7-8 (excluded from the formula, but counted in total)
Detractors = customers scoring 0-6
Use when: measuring customer loyalty and satisfaction over time.

FORMULA 3 — Customer Acquisition Cost (CAC)

CAC = Total Sales & Marketing Cost / Number of New Customers Acquired
Total Sales & Marketing Cost = all spend on ads, salaries, tools, campaigns in the period
New Customers Acquired = count of first-time paying customers gained in that period
Use when: evaluating whether growth spending is efficient.

FORMULA 4 — Customer Lifetime Value (LTV / CLV)

LTV = Average Purchase Value x Purchase Frequency x Average Customer Lifespan
Average Purchase Value = average revenue per transaction
Purchase Frequency = average number of purchases per customer per period
Average Customer Lifespan = average number of periods a customer stays active
Use when: judging how much a company can profitably spend to acquire a customer.

Page 26 of 40
 Product Management — Premium Study Guide

FORMULA 5 — LTV : CAC Ratio

LTV:CAC Ratio = LTV / CAC
A ratio of 3:1 or higher is generally considered healthy for a SaaS/subscription business
A ratio below 1:1 means the company loses money on every customer acquired
Use when: assessing overall business-model sustainability.

FORMULA 6 — Churn Rate

Churn Rate (%) = (Customers Lost in Period / Customers at Start of Period) x 100
Use when: measuring what percentage of customers stop using/paying for the product.

FORMULA 7 — Conversion Rate

Conversion Rate (%) = (Number of Users Completing Action / Total Number of Users) x 100
Use when: measuring effectiveness of a funnel step (e.g., sign-up page to paid subscription).

5.2 Worked Numerical Examples (Easy to Difficult)

Example 1 (Easy) — RICE Score
Given: A feature idea will reach 5,000 users this quarter. Estimated Impact = 2 (high). Confidence = 100% (1.0).
Estimated Effort = 5 person-months.

Required: Calculate the RICE score.

Solution: RICE = (5,000 x 2 x 1.0) / 5 = 10,000 / 5 = 2,000.

Interpretation: A score of 2,000 can now be directly compared against other backlog ideas — the higher the
score, the higher the priority.

Example 2 (Easy-Medium) — Net Promoter Score

Given: A survey of 200 customers found 120 Promoters (score 9-10), 50 Passives (score 7-8), and 30 Detractors
(score 0-6).

Required: Calculate the NPS.

Solution: %Promoters = 120/200 = 60%. %Detractors = 30/200 = 15%. NPS = 60% − 15% = +45.

Interpretation: NPS ranges from −100 to +100. A score of +45 is generally considered excellent, indicating strong
customer loyalty.

COMMON MISTAKE
Students often forget to exclude Passives from the subtraction, or forget to convert counts into percentages before
subtracting. Passives are counted in the total (denominator) but never subtracted.

Example 3 (Medium) — Customer Acquisition Cost

Given: In Q1, a company spent ₹10,00,000 on sales and marketing and acquired 2,000 new paying customers.

Page 27 of 40
 Product Management — Premium Study Guide

Required: Calculate CAC.

Solution: CAC = ₹10,00,000 / 2,000 = ₹500 per customer.

Interpretation: The company spends ₹500, on average, to acquire each new paying customer — this number is
only meaningful when compared against LTV.

Example 4 (Medium-Hard) — Customer Lifetime Value and LTV:CAC Ratio

Given: Continuing Example 3 — the average purchase value is ₹1,000, customers purchase on average 2 times
per year, and the average customer stays active for 3 years.

Required: Calculate LTV, and then the LTV:CAC ratio using the CAC of ₹500 found in Example 3.

Solution: LTV = ₹1,000 x 2 x 3 = ₹6,000. LTV:CAC Ratio = ₹6,000 / ₹500 = 12:1.

Interpretation: A ratio of 12:1 is very healthy (well above the 3:1 benchmark), meaning the company earns far
more from a customer than it spends to acquire that customer — signalling room to invest further in growth.

Example 5 (Difficult) — Combined Funnel and Churn Analysis

Given: A subscription app starts the month with 10,000 active subscribers. During the month, 800 subscribers
cancel, and 1,200 new users sign up, of whom only 300 convert from the free trial to a paid plan (out of 3,000
free-trial users who started that month).

Required: Calculate (a) the monthly churn rate, and (b) the free-trial-to-paid conversion rate.

Solution (a): Churn Rate = (800 / 10,000) x 100 = 8%.

Solution (b): Conversion Rate = (300 / 3,000) x 100 = 10%.

Interpretation: An 8% monthly churn rate is quite high for most subscription businesses (annualised, this
compounds to a large loss of customers if uncorrected), while a 10% trial-to-paid conversion rate would need to
be benchmarked against industry norms (SaaS free-trial conversion often ranges from 15-25%, so 10% may signal
an onboarding problem worth investigating).

COMMON MISTAKE
A frequent error is calculating churn using the number of new sign-ups (1,200) as the denominator instead of the
customers present at the start of the period (10,000). Always match the denominator to the base population
specified in the question.

5.3 Metrics Summary Table

Metric Formula (Short) Good Benchmark (Typical SaaS)

RICE Score (Reach x Impact x Confidence)/Effort Compare relatively; no fixed benchmark

NPS %Promoters − %Detractors > 50 = excellent, 0-30 = good, < 0 = poor

CAC Total S&M Spend / New Customers Lower is better; compare to LTV

LTV Avg Purchase x Frequency x Lifespan Higher is better

LTV:CAC Ratio LTV / CAC 3:1 or higher is healthy

Churn Rate (Lost / Starting Customers) x 100 < 5% monthly is generally healthy for B2C

Page 28 of 40
 Product Management — Premium Study Guide

Metric Formula (Short) Good Benchmark (Typical SaaS)

SaaS

Conversion Rate (Converted / Total) x 100 Varies widely by funnel stage and industry

Page 29 of 40
 Product Management — Premium Study Guide

Chapter 6: Real-World Case Studies and Practical Applications

6.1 Case Study 1 — Netflix: From DVD Rentals to Streaming Product

Netflix began as a DVD-by-mail rental service. As broadband internet adoption grew, Netflix's product
organisation recognised a shift in the Product Life Cycle of DVD rentals (approaching maturity/decline) and used
Jobs-To-Be-Done thinking — customers were not hiring Netflix for "a DVD" but for "convenient entertainment on
demand." This insight drove the pivot to streaming.

• PM lesson — Product Life Cycle: Recognising decline signals early allowed proactive reinvention instead of
reactive decline.
• PM lesson — Data-driven personalisation: Netflix's recommendation algorithm is a Growth-PM discipline,
using retention metrics (e.g., watch-time, completion rate) to continuously refine the product.
• PM lesson — A/B testing culture: Netflix famously tests even small UI changes (thumbnail images, row
ordering) using rigorous experimentation before rolling out globally.

6.2 Case Study 2 — Airbnb: Solving Trust Through Product Design

Early Airbnb faced a core adoption barrier: would strangers trust each other enough to stay in / rent out a home?
The PM team identified this using qualitative research (a Design Thinking "Empathise" step) and solved it through
product features — professional photography, verified reviews, and secure payments — rather than only
marketing.

• PM lesson — Empathise before building: The founders famously went door-to-door photographing hosts'
listings themselves to understand the real friction points.
• PM lesson — North Star Metric: Airbnb's focus on "nights booked" aligned every team (search, pricing,
trust & safety) around one shared outcome.

6.3 Case Study 3 — Slack: Growth Through Activation, Not Just Acquisition
Slack's growth team discovered, using the AARRR framework, that teams which sent 2,000+ messages had
extremely high retention — this became their activation "Aha moment" benchmark. Product and growth teams
then redesigned onboarding to help new teams reach that message threshold quickly.

• PM lesson — Activation over pure acquisition: Optimising only for sign-ups (Acquisition) without fixing
Activation and Retention leads to a "leaky bucket" of churned users.
• PM lesson — Metric-driven onboarding redesign: A single, well-chosen internal metric shaped product
design decisions across multiple teams.

6.4 Case Study 4 — Indian Market: UPI and the BHIM/PhonePe/Google Pay
Ecosystem
India's Unified Payments Interface (UPI) transformed digital payments. Product teams at PhonePe and Google Pay
applied MVP thinking — launching simple peer-to-peer payment flows first, then layering on bill payments,
merchant payments, and financial services (mutual funds, insurance) once core trust and habit were established.

• PM lesson — MVP and iteration: Starting with a narrow, reliable core use case built the trust needed to
expand into a full financial "super app."

Page 30 of 40
 Product Management — Premium Study Guide

• PM lesson — Localisation for B2C growth: Regional language support and cash-back incentives (referral
loops, matching AARRR's "Referral" stage) drove mass adoption across urban and rural India.

6.5 Practical Applications in Business and Industry

Industry How Product Management Is Applied

Optimising search, recommendations, checkout conversion, and delivery logistics as

E-commerce
a product

Balancing regulatory compliance with user-friendly digital banking and payments

FinTech / Banking
experiences

Building patient-facing apps and provider tools with strict data-privacy (e.g., HIPAA-
Healthcare
type) requirements

Designing engaging, outcome-driven learning products and measuring course

EdTech
completion metrics

Managing complex B2B products with long sales cycles, integrations, and enterprise
SaaS / Enterprise Software
customisation

Gaming Balancing monetisation, player retention loops, and live-service content updates

Applying product thinking to hardware + software combined products (smart

Manufacturing / IoT
devices)

6.6 Common Tools Used by Product Managers

Category Example Tools Purpose

Track features, sprints, and release

Roadmapping / Backlog Jira, Productboard, Aha!, Trello
plans

Create wireframes and interactive

Design & Prototyping Figma, Balsamiq, Sketch
prototypes

Track user behaviour and product usage

Analytics Google Analytics, Mixpanel, Amplitude
metrics

Run controlled experiments and feature

Experimentation / A-B Testing Optimizely, LaunchDarkly, VWO
flags

Collect surveys, in-app feedback, and

Customer Feedback Typeform, Intercom, UserVoice, Hotjar
session recordings

Write PRDs and collaborate with cross-

Communication / Docs Confluence, Notion, Google Docs, Slack
functional teams

Track customer relationships, especially

Customer Data / CRM Salesforce, HubSpot
for B2B PMs

Page 31 of 40
 Product Management — Premium Study Guide

6.7 Recent Developments and Trends (2025-2026)

• Rise of the AI Product Manager: With the mainstream adoption of generative AI and large language models
(LLMs), a specialised AI PM role has emerged, focused on prompt design, model evaluation,
hallucination/quality control, and responsible-AI guardrails, alongside traditional PM skills.
• AI copilots inside PM workflows: PMs increasingly use AI tools to draft PRDs, summarise user interviews,
generate synthetic user personas, and analyse large volumes of customer feedback faster than manual
review allows.
• Outcome-driven roadmaps replacing feature roadmaps: More organisations in 2025-2026 are shifting
roadmap communication away from listing specific features toward describing customer/business
outcomes, giving teams more flexibility in how they solve a problem.
• Composable and platform-based products: Businesses increasingly build on top of platforms (payment
APIs, AI model APIs, cloud infrastructure) rather than building everything from scratch, increasing demand
for Platform PMs.
• Privacy-first and regulation-aware product design: With tightening data-protection regulations globally
(and India's Digital Personal Data Protection Act), PMs must increasingly design consent flows and data
handling as core product requirements, not afterthoughts.
• Growing use of continuous discovery: Popularised by product coach Teresa Torres, teams are moving from
periodic "big research phases" toward weekly customer touchpoints woven continuously into the product
process.

Memory Tip

MNEMONIC — 2025-2026 Trends

"AI Owns Product Roadmaps Continuously" → AI PM roles, Outcome-driven roadmaps, Platform products,
Regulation-aware design, Continuous discovery.

Page 32 of 40
 Product Management — Premium Study Guide

Chapter 7: Common Mistakes, Glossary, and Summary

7.1 Common Mistakes Students and New PMs Make

• Confusing Product Manager with Project Manager: Remember — PM decides WHAT and WHY; Project
Manager (and Program Manager) focuses on WHEN and delivery logistics.
• Treating frameworks as rigid checklists rather than thinking tools: Frameworks like SWOT or RICE are
meant to structure judgement, not replace it — exam answers should show application and reasoning, not
just definitions.
• Forgetting to mention real examples: University examiners reward answers that connect theory (e.g., BCG
Matrix) to a real or plausible company example.
• Mixing up NPS calculation: Forgetting to exclude Passives from the subtraction, or not converting counts to
percentages first.
• Ignoring the iterative nature of product development: Presenting product development as a strict one-way
line rather than the continuous Build-Measure-Learn or Discover-Define-Prioritise-Build-Launch-Measure
loop.
• Overlooking soft skills: Many students focus only on tools/frameworks and forget that communication,
empathy, and influence are equally examinable and equally important in practice.
• Assuming PM = coder: Product Managers generally do not write production code; confusing this with a
Software Engineer or Technical Lead role is a common conceptual error.

7.2 Glossary of Important Keywords

Term Meaning

Product Requirement Document — a document specifying what a feature should do

PRD
and why

Minimum Viable Product — the smallest version of a product that tests a core
MVP
hypothesis

Backlog The prioritised list of all work/ideas a product team could potentially build

A fixed time-boxed period (commonly 1-4 weeks) in Agile/Scrum during which a set of
Sprint
work is completed

Key Performance Indicator — a specific measurable value showing how effectively

KPI
goals are being achieved

Churn The rate at which customers stop using or paying for a product

Retention The rate at which customers continue to use a product over time

An experiment comparing two versions (A and B) to see which performs better on a

A/B Test
chosen metric

Roadmap A time-phased visual plan of upcoming product initiatives and releases

Stakeholder Any person or group with an interest in, or influence over, the product's outcome

Page 33 of 40
 Product Management — Premium Study Guide

Term Meaning

GTM Go-To-Market — the plan for launching and promoting a product to its target audience

Sunset (a product) To formally discontinue or retire a product or feature

A toggle allowing a feature to be turned on/off for specific users without a new
Feature Flag
deployment

Product-Market Fit The degree to which a product satisfies strong market demand

7.3 Short Summary

A Product Manager is the person who identifies the right problems to solve, defines what should be built and
why, and coordinates cross-functional teams — engineering, design, marketing, sales, and support — to deliver
value to customers and the business. The role emerged from 1930s brand management at P&G and evolved into
the modern technology-industry discipline it is today.

PMs are distinguished from Product Owners (tactical Agile role), Project Managers (execution/timeline focus),
and Program Managers (cross-project coordination). Effective PMs blend hard skills (data analysis, technical
literacy, prototyping) with soft skills (communication, empathy, influence).

The discipline relies on a toolkit of well-established frameworks: prioritisation frameworks (RICE, MoSCoW,
Kano), strategy frameworks (SWOT, Porter's Five Forces, BCG Matrix, Ansoff Matrix), process frameworks (Design
Thinking, Agile/Scrum, Lean Startup/MVP, Jobs-To-Be-Done), and growth/goal-setting frameworks (AARRR, OKRs,
North Star Metric).

PMs must also be numerically literate, comfortable calculating and interpreting metrics such as RICE score, NPS,
CAC, LTV, LTV:CAC ratio, churn rate, and conversion rate. Real-world case studies from Netflix, Airbnb, Slack, and
India's UPI ecosystem show these concepts applied in practice. Looking ahead to 2025-2026, the profession is
being reshaped by AI-native products, AI-assisted PM workflows, outcome-driven roadmaps, and a growing
emphasis on privacy-aware, continuously-discovered product design.

7.4 Conclusion
Product Management sits at a unique crossroads of business strategy, technology, and human psychology. It is
not a role defined by a single skill but by the ability to synthesise customer needs, business goals, and technical
realities into decisions that create real value. As digital products continue to shape nearly every industry, the
discipline of product management will remain one of the most influential — and most examined — topics in
modern business and technology education. Mastery of its definitions, frameworks, metrics, and real-world
applications equips a student not only to answer examination questions with confidence, but to understand how
successful products are actually built in the real world.

Page 34 of 40
 Product Management — Premium Study Guide

Chapter 8: Exam Preparation — Questions and Answers

8.1 Frequently Asked Exam Questions (with Short Answers)

1. What is a Product Manager? A professional who identifies customer needs and business goals, defines
what a product should do, and coordinates teams to build and launch it successfully.
2. What is the difference between a Product Manager and a Product Owner? A PM owns strategy and vision
across the product; a Product Owner is a tactical Agile/Scrum role managing the sprint backlog, often for
one team.
3. What is an MVP? The Minimum Viable Product — the smallest version of a product that lets a team test a
core hypothesis with real users at minimal cost.
4. What does RICE stand for? Reach, Impact, Confidence, Effort — a scoring framework for prioritising
features.
5. What is the Kano Model used for? Classifying features as Basic, Performance, or Delighter needs, based on
their effect on customer satisfaction.
6. What are the four stages of the Product Life Cycle? Introduction, Growth, Maturity, and Decline.
7. What is a North Star Metric? The single metric that best reflects the core value a product delivers to
customers and predicts long-term growth.
8. What is the formula for NPS? NPS = %Promoters − %Detractors.
9. What is the BCG Matrix used for? Classifying a company's products into Stars, Cash Cows, Question Marks,
and Dogs based on market growth and relative market share.
10. What are OKRs? A goal-setting framework combining a qualitative Objective with measurable Key Results.
11. What is Product-Market Fit? The degree to which a product satisfies a strong market demand, often seen
as the milestone that justifies scaling a business.
12. What is the difference between Agile and Scrum? Agile is a broader philosophy/set of values for iterative
development; Scrum is a specific, popular framework that implements Agile using sprints and defined roles.
13. What is the AARRR framework? A growth framework covering Acquisition, Activation, Retention, Referral,
and Revenue.
14. What is Jobs-To-Be-Done? A framework stating customers "hire" products to accomplish a specific
functional, emotional, or social job in their lives.
15. What is churn rate? The percentage of customers who stop using or paying for a product during a given
period.
16. Why is prioritisation important in product management? Because resources (time, engineering capacity,
budget) are always limited relative to the number of ideas a team could pursue.
17. What is a PRD? A Product Requirement Document that specifies what a feature should do, why it matters,
and how success will be measured.
18. What is the Ansoff Matrix used for? Selecting a growth strategy across combinations of new/existing
products and new/existing markets.

Page 35 of 40
 Product Management — Premium Study Guide

8.2 Multiple Choice Questions (20) with Answers

19. Who is credited with writing the founding memo of modern brand/product management? (a) Peter Drucker
(b) Neil H. McElroy (c) Michael Porter (d) Eric Ries — Answer: (b)
20. RICE stands for Reach, Impact, Confidence, and ______? (a) Execution (b) Effort (c) Engagement (d)
Evaluation — Answer: (b)
21. Which framework uses the categories Must have, Should have, Could have, and Won't have? (a) RICE (b)
Kano Model (c) MoSCoW (d) SWOT — Answer: (c)
22. In the Kano Model, a feature that causes major dissatisfaction when missing but is barely noticed when
present is called a: (a) Delighter (b) Basic/Must-be need (c) Performance need (d) Indifferent need —
Answer: (b)
23. Which of the following is NOT one of the four PLC stages? (a) Introduction (b) Growth (c) Validation (d)
Decline — Answer: (c)
24. SWOT stands for Strengths, Weaknesses, Opportunities, and: (a) Targets (b) Threats (c) Trends (d) Tactics —
Answer: (b)
25. Porter's Five Forces model was developed by: (a) Michael Porter (b) Igor Ansoff (c) Eric Ries (d) Dave
McClure — Answer: (a)
26. In the BCG Matrix, a product with high market growth and high market share is a: (a) Dog (b) Cash Cow (c)
Star (d) Question Mark — Answer: (c)
27. The Ansoff Matrix strategy of selling more existing products to existing markets is called: (a) Diversification
(b) Market Development (c) Product Development (d) Market Penetration — Answer: (d)
28. Which framework has the five stages Empathise, Define, Ideate, Prototype, Test? (a) Lean Startup (b)
Design Thinking (c) Agile (d) JTBD — Answer: (b)
29. A fixed time-boxed iteration in Scrum is called a: (a) Cycle (b) Sprint (c) Phase (d) Stage — Answer: (b)
30. The Build-Measure-Learn loop belongs to which methodology? (a) Design Thinking (b) Lean Startup (c) Agile
(d) Kano Model — Answer: (b)
31. Jobs-To-Be-Done was popularised by: (a) Eric Ries (b) Clayton Christensen (c) Dave McClure (d) Michael
Porter — Answer: (b)
32. In AARRR, the second 'A' stands for: (a) Acquisition (b) Activation (c) Advocacy (d) Analytics — Answer: (b)
33. An OKR consists of an Objective and: (a) Key Results (b) Key Requirements (c) Key Roadmaps (d) Key
Revenue — Answer: (a)
34. NPS is calculated as: (a) Promoters + Detractors (b) %Promoters − %Detractors (c) Promoters / Detractors
(d) %Passives − %Detractors — Answer: (b)
35. CAC stands for: (a) Customer Acquisition Cost (b) Customer Activity Count (c) Customer Approval Cycle (d)
Cost Adjusted Conversion — Answer: (a)
36. A healthy LTV:CAC ratio benchmark is generally considered to be around: (a) 1:1 (b) 3:1 or higher (c) 10:1
minimum (d) 0.5:1 — Answer: (b)
37. Who is typically responsible for maintaining the Scrum backlog on a day-to-day basis? (a) Project Manager
(b) Product Owner (c) Scrum Master only (d) CEO — Answer: (b)
38. Which role focuses primarily on APIs and internal/external developer-facing products? (a) Growth PM (b)
Platform PM (c) B2C PM (d) Product Marketing Manager — Answer: (b)

Page 36 of 40
 Product Management — Premium Study Guide

8.3 Short Answer Questions (15)

39. Define Product Management in one sentence.
40. List any four responsibilities of a Product Manager.
41. Differentiate between a Product Manager and a Project Manager.
42. What is the significance of the RICE scoring model?
43. Explain the concept of an MVP with one example.
44. What are the four quadrants of the BCG Matrix?
45. List the five forces in Porter's Five Forces model.
46. What is the purpose of a Product Requirement Document (PRD)?
47. Explain the term 'North Star Metric' with one example.
48. What is the difference between Retention and Churn?
49. Name any three tools used by Product Managers and their purpose.
50. What are the four stages of the AARRR framework beyond Acquisition?
51. What is meant by 'leading through influence' in the PM role?
52. Explain the Kano Model's 'Delighter' category with an example.
53. What is meant by the term 'Product-Market Fit'?

8.4 Long Answer Questions (15)

54. Explain the role and responsibilities of a Product Manager in detail, with suitable examples.
55. Compare and contrast Product Manager, Product Owner, Project Manager, and Program Manager roles.
56. Describe the Product Life Cycle with a diagram and explain the PM's strategic focus at each stage.
57. Explain the RICE, MoSCoW, and Kano Model prioritisation frameworks, including their advantages and
disadvantages.
58. Discuss SWOT Analysis and Porter's Five Forces as strategic tools for product decision-making, using a real
or hypothetical company example.
59. Explain the BCG Matrix and Ansoff Matrix with diagrams, and describe how a company can use them
together for portfolio strategy.
60. Describe the Design Thinking process and explain how it differs from the traditional Agile/Scrum approach.
61. Explain the Lean Startup methodology and the Build-Measure-Learn loop, with a real-world example.
62. Discuss the Jobs-To-Be-Done framework and explain why it is considered more insightful than simple
feature requests.
63. Explain the AARRR (Pirate Metrics) framework in detail, describing each stage with examples.
64. Describe how OKRs and North Star Metrics are used together to align an organisation's product strategy.
65. Explain the key formulas (RICE, NPS, CAC, LTV, Churn) a Product Manager should know, with one worked
example each.
66. Discuss any two real-world product management case studies and the lessons they demonstrate.
67. Explain the different types of Product Managers (Technical, Growth, Platform, B2B, B2C, AI) with examples.

Page 37 of 40
 Product Management — Premium Study Guide

68. Discuss recent trends shaping product management in 2025-2026, including the rise of AI Product
Managers.

8.5 Numerical Problems (Practice)

69. A feature has Reach = 12,000 users/quarter, Impact = 1 (medium), Confidence = 90%, and Effort = 6 person-
months. Calculate its RICE score.
70. Out of 500 survey respondents, 280 are Promoters, 150 are Passives, and 70 are Detractors. Calculate the
NPS.
71. A company spent ₹25,00,000 on marketing in a quarter and acquired 5,000 new customers. Calculate the
CAC.
72. A customer's average purchase value is ₹800, they purchase 4 times a year, and stay active for 2.5 years on
average. Calculate the LTV. If CAC is ₹1,200, calculate the LTV:CAC ratio and comment on whether it is
healthy.
73. A product starts the month with 8,000 subscribers and loses 640 during the month. Calculate the monthly
churn rate.
(Answers can be derived using the formulas and worked examples provided in Chapter 5, Section 5.2.)

8.6 Viva / Oral Exam Questions

• Why is a Product Manager often called the "CEO of the Product," and in what ways is that comparison
misleading?
• If you had to cut one of the four RICE factors, which would you keep least important, and why?
• Can a single product be in different Product Life Cycle stages in different countries at the same time?
Explain.
• How would you decide between using MoSCoW versus RICE for a given prioritisation situation?
• What is one product feature you personally use that you would classify as a Kano 'Delighter,' and why?
• Explain, in your own words, why Retention is often considered more important than Acquisition for long-
term growth.
• How might Generative AI change the day-to-day workflow of a Product Manager in the next few years?
• What ethical considerations should a PM keep in mind when designing a product that collects personal user
data?

Page 38 of 40
 Product Management — Premium Study Guide

Chapter 9: One-Page Quick Revision Notes

QUICK REVIEW — PRODUCT MANAGER

Definition: Owns WHAT to build & WHY; bridges Business, Tech, and UX.
History: Born 1931 (Neil McElroy memo, P&G brand management).
Vs Product Owner: PM = strategy/vision; PO = sprint backlog (tactical).
Vs Project Manager: PM = what/why; PjM = time/budget/delivery.
PLC Stages: Introduction -> Growth -> Maturity -> Decline.
Dev Process: Discover -> Define -> Prioritise -> Design/Build -> Launch -> Measure (loop).

PRIORITISATION FRAMEWORKS
RICE = (Reach x Impact x Confidence) / Effort
MoSCoW = Must / Should / Could / Won't have
Kano = Basic / Performance / Delighter / Indifferent needs

STRATEGY FRAMEWORKS
SWOT = Strengths, Weaknesses, Opportunities, Threats
Porter's 5 Forces = Rivalry, New Entrants, Substitutes, Supplier Power, Buyer Power
BCG Matrix = Stars, Cash Cows, Question Marks, Dogs
Ansoff Matrix = Market Penetration, Product Development, Market Development, Diversification

PROCESS FRAMEWORKS
Design Thinking = Empathise -> Define -> Ideate -> Prototype -> Test
Agile/Scrum = Backlog -> Sprint Planning -> Daily Standup -> Review -> Retro
Lean Startup/MVP = Build -> Measure -> Learn (loop)
JTBD = Customers 'hire' products to do a functional/emotional/social job

GROWTH & GOAL FRAMEWORKS

AARRR = Acquisition -> Activation -> Retention -> Referral -> Revenue
OKRs = Objective (qualitative) + Key Results (measurable)
North Star Metric = single metric reflecting core customer value

KEY FORMULAS
NPS = %Promoters - %Detractors
CAC = Total S&M Cost / New Customers Acquired

Page 39 of 40
 Product Management — Premium Study Guide

LTV = Avg Purchase Value x Purchase Frequency x Avg Lifespan

LTV:CAC healthy benchmark = 3:1 or higher
Churn Rate (%) = (Customers Lost / Customers at Start) x 100
Conversion Rate (%) = (Users Completing Action / Total Users) x 100

TYPES OF PMs
Technical PM, Growth PM, Platform PM, B2B PM, B2C PM, Data PM, AI PM, APM, CPO

2025-2026 TRENDS
Rise of AI Product Managers; AI copilots in PM workflows; outcome-driven roadmaps; platform/composable
products; privacy & regulation-aware design; continuous discovery.

Page 40 of 40