FOUNDATIONS

OF PRODUCT
MANAGEMENT
CHAPTER 2
LEARNING OBJECTIVES
LEARNING OBJECTIVES
1. Conduct the role of a product manager.
2. Understand the core responsibilities of a product manager.
3. Apply the skills and qualities of effective product
managers.
4. Trace the evolution of the product management discipline.
What Does a
Product
Manager Do?
Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.
Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.

Engineers write the code.

Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.

Designers craft the interface.

Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.

Marketers tell the story.

Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.

Salespeople close the deals.

Product Manager as an Orchestra Conductor
A conductor does not play an instrument —
they make sure every section plays in harmony.

The Product Manager coordinates them all — making sure

everyone is aligned to a single product vision.
Roles of a Product
Manager
Role 1: Strategic Vision
• Defining where the product
is going — and why it
matters
Role 1: Strategic Vision
• A product manager without
a clear strategic vision is
like a GPS without a
destination.
Role 1: Strategic Vision
• The team might move
quickly, ship features, and
look busy — but they will
waste time, resources, and
momentum heading in the
wrong direction.
Role 1: Strategic Vision
• The vision ensures every
decision moves the product
closer to its intended
destination.
Strategic Vision in Action:
Apple
Apple's product managers
did not just decide to build "a
better phone." In 2007, Steve
Jobs and the product team
articulated a strategic vision:
eliminate the keyboard,
combine a phone, an iPod,
and the internet into one
device, and make it so
intuitive a child could use it.
Strategic Vision of Apple
The Vision
"An iPod, a phone, and an internet communicator — are you
getting it?" — Steve Jobs, iPhone launch 2007.
The Strategy
Every feature decision, every design choice, every engineering
trade-off flowed from that singular, customer-centered vision.
The Result
A product that redefined an entire industry — because the
vision was clear before a single line of code was written.
Role 2: Product Planning
• Turning vision into a
concrete, prioritized plan of
action
Role 2: Product Planning
• If strategic vision is the
destination, product
planning is the map. This is
where product managers
turn the big idea into a
concrete, actionable plan —
deciding which features to
build, in what order, and
with which resources.
Product Planning in Action:
Amazon’s Working Backwards
Amazon’s product managers
famously begin product
planning by writing a mock
press release for the finished
product—before any
development begins—a method
known as “Working
Backwards.”
Product Planning in Action:
Amazon’s Working Backwards
They describe what the product
does and why customers will
love it, then work backward to
figure out what needs to be
built.
Product Planning in Action:
Amazon’s Working Backwards
This approach forces PMs to
prioritize only what creates
genuine customer value,
eliminating features that sound
good internally but don't
matter to users.
Role 3: Project Management
• Keeping development on
track — on time, on budget,
and on target
Role 3: Project Management
• Think of a product manager
running a project like a film
director managing a movie
set — they do not act in the
film or operate the camera,
but nothing gets filmed
without their coordination
and decision-making.
Project Management in Action:
Spotify
Spotify is world-renowned for
its product development
model. Their product
management teams use
"Squads, Tribes, and Guilds"
— an organizational structure
that keeps development
nimble while maintaining
coordination at scale.
 Project Management in Action:
Spotify
Squad Tribe
A small, cross-functional team A collection of squads
(6–12 people) owning a specific working on related areas.
feature area — like Search or
Provides coordination
Playlists. The PM leads the squad.
without bureaucracy.
Guild
A community of practice (e.g., all designers) that
shares knowledge across squads.

This model allows product managers of Spotify to

move fast and independently while staying
aligned with company-wide priorities — a
masterclass in agile project management.
Role 4: User Experience (UX) Design
• Advocating for the person
who actually uses the
product
 Role 4: User Experience (UX) Design

Usability Testing Design Reviews User Journey Mapping

PMs organize and observe PMs review design PMs help map every step
sessions where real users mockups and prototypes, of the customer's
interact with the product. asking: "Does this match experience — identifying
Every point of confusion is what users actually need?" pain points and
a data point for — not just "Does it look opportunities to create
improvement. nice?" moments of delight.
UX Design Advocacy in Action:
Airbnb
In Airbnb's early days,
listings were failing to
convert because the property
photos were low quality.
UX Design Advocacy in Action:
Airbnb
Product managers and
designers identified a critical
UX breakdown: guests could
not trust what they were
booking.
UX Design Advocacy in Action:
Airbnb
The product manager's
solution was not a technical
feature — it was hiring
professional photographers
to reshoot listings in New
York.
UX Design Advocacy in Action:
Airbnb
Bookings doubled in those
listings almost immediately.
UX Design Advocacy in Action:
Airbnb
Lesson: Great UX thinking is
not always about code.
Sometimes the best product
decision is deeply human —
and product managers need
the creativity to see that.
Role 5: Market Launch
• Bringing the product to the
world — with strategy, not
just excitement
Market Launch in Action:
Netflix
When Netflix launched its
original content strategy
(starting with House of Cards
in 2013), the product
manager and marketing
teams executed a masterclass
in go-to-market strategy.
Market Launch in Action:
Netflix
• Positioning: "Premium TV
you can't get anywhere
else"
• Messaging: All 13 episodes
dropped at once —
redefining how TV is
consumed
Market Launch in Action:
Netflix
• Timing: Valentine's Day
weekend release,
maximizing co-viewing
behavior
• Monitoring: Netflix tracked
watch time, completion
rates, and subscriber
growth in real time
Market Launch in Action:
Netflix
• The launch did not just
work — it changed an
industry and gave Netflix a
differentiation advantage
that persists today.
Role 6: Performance Analysis
• Measuring what matters —
and using data to keep
improving
 Key Metrics

User Engagement Revenue Metrics

Daily/Monthly Active Users (DAU/MAU), session Monthly Recurring Revenue (MRR), Average
length, feature adoption rates. Are users actually Revenue Per User (ARPU), conversion rate from
using the product consistently? free to paid. Is the product generating business
value?

Customer Satisfaction Retention & Churn

Net Promoter Score (NPS), Customer Satisfaction What percentage of users return after Day 1, Day
Score (CSAT), app store reviews. Are customers 7, Day 30? Churn rate reveals if the product
happy enough to stay — and recommend you? delivers enough ongoing value to keep people
coming back.
Performance Analysis in Action:
Netflix's A/B Testing Culture
• Netflix runs hundreds of
A/B tests simultaneously.
Their PMs don't guess what
thumbnail artwork will get
more clicks — they test
different versions with
different user groups and
measure results.
Performance Analysis in Action:
Netflix's A/B Testing Culture
• This data-driven approach
extends to everything:
content recommendations,
UI layout, onboarding flows,
and even which shows to
produce.
Performance Analysis in Action:
Netflix's A/B Testing Culture
• The result? Netflix's
recommendation engine
drives over 80% of all
content watched on the
platform — a direct
outcome of relentless
performance analysis and
iteration.
Role 7: Stakeholder Communication
• Acting as the bridge
between customers,
executives and teams to
keep everyone informed and
aligned
Role 7: Stakeholder Communication
• The product manager is the
product's spokesperson —
internally and externally.
 Role 7: Stakeholder Communication
Customers Executives
The ultimate stakeholders. Their Want to know: Is the product on
needs drive all decisions. strategy? What are the risks?

Sales Engineering
Needs product updates and Need clarity on priorities and
competitive intel to close technical constraints to build
deals effectively. effectively.
Marketing Design
Needs product knowledge to Needs customer insight and
craft accurate, compelling business context to create the
campaigns. right experience.
Stakeholder Communication in
Action: Slack
• Slack’s product management
teams became famous for
their "changelog"
communication culture. Every
product update — no matter
how small — was
communicated to internal
teams and customers through
detailed, plain-language
release notes.
Stakeholder Communication in
Action: Slack
• This created three powerful
outcomes:
oSales always knew what was
new and could reference it in
deals
oCustomers felt respected and
informed — building loyalty
oInternal teams stayed aligned
without endless meetings
Responsibilities of a
Product Manager
 Role vs. Responsibility

Role Responsibility
“What hat are you wearing?” “What are you accountable for?”
 Role vs. Responsibility

Role Responsibility
The part you play in the system The tasks and outcomes you
own
Responsibility 1: Market Research
•Gathering information about
customers, competitors, and
market trends to make
informed product decisions.
 Responsibility 1: Market Research

Customer Needs Market Trends

What problems are users Where is the industry heading?
trying to solve? What What technologies or
frustrates them today? behaviors are emerging?

Competitive Landscape
Who else is solving this problem? How are they doing it, and where
do they fall short?
Grab: Listening to Filipino
Commuters
What Grab’s Product
Manager Did
•Grab's product managers
studied Filipino commuters
— analyzing transportation
habits, pricing sensitivity,
and route preferences —
before designing their ride-
hailing features.
Grab: Listening to Filipino
Commuters
What Grab’s Product
Manager Did Research On
•How do Filipinos typically
commute? (tricycle, jeepney,
MRT, car)
•What is the average
acceptable fare for different
income brackets?
Grab: Listening to Filipino
Commuters
What Grab’s Product
Manager Did Research On
•How does traffic congestion
affect booking behavior?
•What features do
competitors like Angkas or
JoyRide offer?
Grab: Listening to Filipino
Commuters
The Result
•Affordable fare tiers for
budget-conscious users
•Motorcycle taxi (GrabBike)
for traffic-heavy areas
•Cash payment option for
unbanked riders
Responsibility 2: Product Strategy
•A long-term plan that defines
what the product will
achieve, for whom, and how it
will win in the market.
Responsibility 2: Product Strategy
•Without a strategy, building a
product is like leaving on a
road trip without a
destination — you might
drive fast, but you'll never
know if you've arrived.
 Responsibility 2: Product Strategy
Who is it for? What problem does How does it beat
Target customers it solve? competitors?
Core value Competitive
proposition advantage
 foodpanda: A Local-First Delivery
Strategy
Local Restaurant Logistics
Partnerships Optimization
Onboarded small, Adapted delivery routes
for Manila's congested
neighborhood eateries
streets and island
— not just big chains geography

Payment Flexibility — Peak timing around

Cash on delivery Filipino meal culture
remains king for many (merienda, late-night
Filipinos orders)
Responsibility 3: Product Planning
•Working with cross-
functional teams —
engineers, designers,
marketers — to decide what
gets built, in what order, and
why.
 GCash: Prioritizing Features for
Filipino Users
GCash's Product
Planning Choices
Product managers of
GCash prioritized features
that matched how Filipinos
actually use money — not
what was trendy globally.

Mobile Payments Bill Splitting Remittance Services

Fast QR-based checkout for Group expense sharing for Easy OFW money transfers
sari-sari stores everyday Filipinos — a top Filipino need
Responsibility 4: User Experience
Design
•Partnering with designers to
build interfaces that are easy
to use, culturally relevant,
and accessible to the target
audience.
Responsibility 4: User Experience
Design
•A product manager is like an
architect who does not lay
the bricks, but ensures the
building makes sense for the
people who will live in it.
Lazada: Designing for Every Filipino
Shopper
Product managers of Lazada
worked with designers to
ensure the platform worked
for all Filipinos — not just
tech-savvy urban users.
Lazada: Designing for Every Filipino
Shopper
Multi-Language Support
Filipino, English, and regional dialects
to reach all users

Flexible Payments
Cash on delivery, GCash, credit cards —
options for every buyer

Smart Shipping Options

Routes tailored to island geography and
provincial logistics
Responsibility 5: Go-to-Market
Strategy
•It is the plan for how a
product reaches its target
customers — including how
it will be marketed, sold,
priced, and supported to
reach the right users at the
right time.
Responsibility 5: Go-to-Market
Strategy
•It is not just about
advertising — it is about
coordinating marketing,
sales, customer support, and
distribution to create a
successful launch moment.
Mobile Legends: Launching with
Filipino Culture
How Mobile Legends Nailed
Its Philippine Launch
The PM coordinated a culturally
tailored launch campaign that
spoke directly to Filipino
gamers.
Mobile Legends: Launching with
Filipino Culture
How Mobile Legends Nailed
Its Philippine Launch
•Grassroots Engagement
Through Esports & Events
•Partnered with Filipino
influencers and streamers
Responsibility 6: Performance
Analysis
•Using data and user feedback
to measure how well the
product is performing — and
identifying what to improve
next.
Responsibility 6: Performance
Analysis
Common Metrics Product
Managers Track
oDaily/Monthly Active Users
(DAU/MAU)
oRetention rate — do users
come back?
oConversion rate — do users
take action?
oNet Promoter Score (NPS) —
would users recommend it?
 Facebook PH: Measuring
What Matters Locally
Facebook's local product team tracks
performance metrics specific to Filipino
users — not just global averages.

92% 4.5hrs DAU

Internet Users Daily Social Key Metric
on Facebook Media Use Tracked
Philippines has one Average time Daily active users +
of the world's Filipinos spend on engagement with
highest Facebook social platforms per localized content
penetration rates day
Responsibility 7: Stakeholder
Communication
•Acting as the bridge between
all parties — customers,
engineers, designers, sales,
and executives — to ensure
everyone is aligned and
informed.
Responsibility 7: Stakeholder
Communication
•A product manager is
constantly communicating —
upward to executives,
sideways to engineering and
design teams, and outward to
customers. Each audience
needs a different message,
tone, and level of detail.
Responsibility 7: Stakeholder
Communication
•The product manager is the
translator in a room where
everyone speaks a different
language — business, tech,
and customer service.
Without them, no one
understands each other.
Responsibility 7: Stakeholder
Communication
•Executives want progress,
risks, and business impact
•Engineering teams need clear
requirements and technical
context
•Customers need empathy
and reassurance that
feedback is heard
 PLDT: Keeping Everyone in the
Loop
What PLDT’s Product
Manager Does
A product manager at
PLDT acts as a
communication hub —
translating signals between
all stakeholders.

Customers → Engineering Progress → Executives Teams → Alignment

Relays feedback on signal quality Updates leadership on product Ensures marketing, tech, and ops
and app bugs milestones and market shifts move toward one goal
 Evolution of Product
Management Discipline
 Evolution of Product Management
Through Eras
01 02
1950s–1980s 1980s–1990s
Early Stages: Engineering & Lifecycle Software Products: Users Enter the Picture

03 04
1990s–2000s 2000s–Present
Internet & Digital: Everything Goes Online Data-Driven: Numbers Tell the Story

05 06
2010s–Present Present
Lean & Product-Led Growth New Industries, CX & Design Thinking
Early Stages (1950s – 1980s)
The Birth of Dedicated
Product Roles
As companies like Procter &
Gamble grew massive product
portfolios in the 1930s–50s, no
single team owned a product
end-to-end.
Early Stages (1950s – 1980s)
The Birth of Dedicated
Product Roles
P&G's solution? Assign a "brand
man" — a dedicated person
responsible for one product's
entire journey. This became the
blueprint for product
management.
Early Stages (1950s – 1980s)
The Birth of Dedicated
Product Roles
P&G's Neil McElroy wrote a
1931 memo arguing for
dedicated brand managers.
That memo became the
foundation of modern product
management — even inspiring
the founders of HP.
 What Did Early PMs Actually Do?

Define Oversee Manage Gather Market

Specs Manufacturing Lifecycle Research
The job was deeply operational. Success meant getting the product out the door on time, within budget, and
meeting quality standards. The customer was important — but secondary to engineering execution.
Introduction of Software Products
(1980s – 1990s)
When IBM launched the
Personal Computer in 1981,
and Apple launched the
Macintosh in 1984, a new
question arose: How do you
manage a product you cannot
hold in your hands?
Introduction of Software Products
(1980s – 1990s)
Software behaved differently
from physical goods.
oYou couldn't "touch" it before
buying
oIt could be updated after
purchase
oUsers needed to learn how to
use it
Introduction of Software Products
(1980s – 1990s)
This demanded a new kind of
product thinking: start with the
user's experience, not the
engineer's blueprint.
Introduction of Software Products
(1980s – 1990s)
The Rise of the Software
Product Manager
The rise of software products
created a new breed of product
manager — one focused on
users, not just manufacturing.
The shift to user-centric design
changed everything.
 Key Concepts Introduced

User-Centric Design Agile Methodologies

Design around the user's needs and pain Scrum and Kanban enabled iterative
points — not just technical capability. development and fast adaptation.

Cross-Functional Teams Market Validation

Engineers, designers, QA, and marketers Gathering real user feedback early —
working together in one product team. before fully building the product.
User-Centric Design
•It means asking users what
they struggle with — and
designing your product to solve
that, not just what's technically
impressive.
User-Centric Design
•When Apple launched the Mac,
it introduced a graphical user
interface (GUI) with icons and a
mouse. Before that, computers
required memorizing typed
commands. Apple asked: "What
if anyone could use this?"
User-Centric Design
•The Mac did not win on
specifications. It won because
normal people could actually
use it.
 Key Concepts Introduced

User-Centric Design Agile Methodologies

Design around the user's needs and pain Scrum and Kanban enabled iterative
points — not just technical capability. development and fast adaptation.

Cross-Functional Teams Market Validation

Engineers, designers, QA, and marketers Gathering real user feedback early —
working together in one product team. before fully building the product.
Agile Methodology
Think of Building a Product
Like Cooking
Old way (Waterfall): Plan the entire
recipe. Buy all ingredients. Cook for 6
months. Serve. Hope people like it.

Agile way: Cook a small dish. Let guests

taste it. Adjust seasoning. Serve more.
Repeat.

Agile methodologies like Scrum and

Kanban allowed software teams to ship
fast, get feedback, and improve — in
short cycles called sprints.
Microsoft Word: A Masterclass in
Iteration
How Microsoft Used Software
PM Principles
Microsoft Word launched in
1983. It was clunky and hard to
use. But unlike a physical
product, Microsoft could
update, patch, and re-release it.
Microsoft Word: A Masterclass in
Iteration
How Microsoft Used Software
PM Principles
By listening to users and
iterating rapidly, Word evolved
into the world's most-used
word processor.
Microsoft Word: A Masterclass in
Iteration
How Microsoft Used Software
PM Principles
By Word 5.0 (1991), Microsoft
had incorporated hundreds of
user-requested features. The
iterative model — driven by a
dedicated software PM team —
was central to its dominance.
 Key Concepts Introduced

User-Centric Design Agile Methodologies

Design around the user's needs and pain Scrum and Kanban enabled iterative
points — not just technical capability. development and fast adaptation.

Cross-Functional Teams Market Validation

Engineers, designers, QA, and marketers Gathering real user feedback early —
working together in one product team. before fully building the product.
Rise of Internet and Digital
Products (1990s – 2000s)
The mid-1990s brought the
World Wide Web into homes
and offices. Suddenly, products
did not need shelves,
salespeople, or shipping trucks.
They just needed a URL.
Rise of Internet and Digital
Products (1990s – 2000s)
The mid-1990s brought the
World Wide Web into homes
and offices. Suddenly, products
did not need shelves,
salespeople, or shipping trucks.
They just needed a URL.
 Rise of Internet and Digital
Products (1990s – 2000s)
From Physical Shelves to Digital Platforms

E-Commerce Platforms Digital Services Web Applications

Amazon (1994) proved you Services like online banking, Software moved from CDs to
could sell products entirely streaming media, and social browsers. Products could
online — disrupting brick- networking emerged — reach millions of users
and-mortar retail products with no physical overnight with a single
permanently. form at all. deployment.
Amazon: The Product Management
Blueprint of the Internet Era
Jeff Bezos built Amazon as a
data-first, customer-centered
product organization.
Amazon: The Product Management
Blueprint of the Internet Era
They solve problems no one had
solved before:
oHow do you build trust for
online payments?
oHow do you display millions of
products clearly?
oHow do you make returning a
book feel easy?
Amazon: The Product Management
Blueprint of the Internet Era
These were user experience
problems — not engineering
problems. A new kind of
product management thinking.
Amazon: The Product Management
Blueprint of the Internet Era
Every page, every
recommendation, every
checkout step was tested,
measured, and optimized by
product teams.
Amazon: The Product Management
Blueprint of the Internet Era
Amazon pioneered practices —
like A/B testing at scale — that
became standard product
management tools across the
industry.
Shift to Data-Driven Decision-
Making (2000s – Present)
In the 2000s, product managers
stopped guessing what users
wanted. With big data and
analytics, they could observe
real behavior and make
decisions backed by evidence —
not intuition alone.
The Power of Watching What Users
Actually Do
Before data, product managers
relied on surveys and gut
feelings. The problem? People
say one thing and do another.
The Power of Watching What Users
Actually Do
With data tools, PMs could
watch real behavior:
oWhich buttons users clicked
oWhere they dropped off
oWhat features they ignored
 The PM Data Toolkit

A/B Testing Cohort Analysis

Compare two versions of a feature to see which performs Group users by behavior or signup date. Track how each
better. Like a controlled science experiment for your product. group behaves over time to understand retention patterns.

Predictive Analytics Behavior Tracking

Use historical data to forecast future behavior — who's about Heatmaps, event tracking, and session recordings reveal
to churn, who's ready to upgrade. exactly how users interact with your product.
Netflix: Every Decision Is a Data
Decision
How Netflix Uses Data to Drive
Product Decisions
Netflix runs over 250 A/B tests
per year. Everything — thumbnail
images, title descriptions,
autoplay timing — is tested. Their
recommendation engine, powered
by cohort analysis and predictive
models, drives 80% of all content
watched.
Netflix: Every Decision Is a Data
Decision
How Netflix Uses Data to Drive
Product Decisions
When Netflix tested personalized
artwork for each user (showing
different thumbnails based on
your watch history), they saw a
measurable uplift in engagement.
Data, not designers, made the call.
 The PM Data Toolkit

A/B Testing Cohort Analysis

Compare two versions of a feature to see which performs Group users by behavior or signup date. Track how each
better. Like a controlled science experiment for your product. group behaves over time to understand retention patterns.

Predictive Analytics Behavior Tracking

Use historical data to forecast future behavior — who's about Heatmaps, event tracking, and session recordings reveal
to churn, who's ready to upgrade. exactly how users interact with your product.
Cohort Analysis
Cohort
•A group of users who share
something in common — like
when they signed up.
Cohort Analysis
•It asks: “Of everyone who signed
up in January, how many are still
using the app in June?”
Cohort Analysis
•Spotify tracks cohorts of users
who joined during specific
campaigns. If a July promotion
cohort churns faster than an
organic cohort, the product team
investigates and fixes the
onboarding experience for that
group.
 The PM Data Toolkit

A/B Testing Cohort Analysis

Compare two versions of a feature to see which performs Group users by behavior or signup date. Track how each
better. Like a controlled science experiment for your product. group behaves over time to understand retention patterns.

Predictive Analytics Behavior Tracking

Use historical data to forecast future behavior — who's about Heatmaps, event tracking, and session recordings reveal
to churn, who's ready to upgrade. exactly how users interact with your product.
Rise of Lean Startup and Product-
Led Growth (2010s – Present)
•Eric Ries published The Lean
Startup in 2011 and changed how
founders and product managers
think about building products.
Stop planning. Start
experimenting. Learn faster than
your competitors.
Lean Startup
The Core Idea
Eric Ries asked a
deceptively simple
question:
“What if most of what we
think we know about
Build MVP Measure Learn & Pivot building products is
wrong?”
Lean Startup
The Core Idea
His answer: Stop guessing.
Start testing.

Build MVP Measure Learn & Pivot

Lean Startup
The Core Idea
Your first idea is almost
always wrong. The goal is
not to execute a perfect
plan — it is to learn as fast
as possible what actually
Build MVP Measure Learn & Pivot works.
Lean Startup
The Core Idea
Instead of spending two
years building a "perfect"
product, you spend two
weeks building the
Minimum Viable Product
Build MVP Measure Learn & Pivot that solves a real problem.
Then you put it in front of
real users and watch what
happens.
Lean Startup
The Core Idea
If users love it — invest
more. If they do not —
change direction. This
prevents companies from
building the wrong thing
Build MVP Measure Learn & Pivot at massive cost.
Minimum Viable Product (MVP)
•It is the simplest version of
your product that still solves
the core problem for users —
enough to learn from, not
enough to be "perfect."
Minimum Viable Product (MVP)
Don't Build a Car. Start With a
Skateboard.
If your user needs to get from A
to B, don't spend 2 years
building a car. Give them a
skateboard (MVP). It solves the
core problem. Learn from how
they use it. Then build a bike,
then a car.
Minimum Viable Product (MVP)
Don't Build a Car. Start With a
Skateboard.
Each version delivers value AND
generates learning. That's the
MVP mindset: minimum
features, maximum learning.
Minimum Viable Product (MVP)
In 2007, before building
Dropbox, founder Drew
Houston wasn't sure people
would pay for cloud storage. His
MVP? A 3-minute demo video
explaining the product.
Minimum Viable Product (MVP)
Overnight, signups went from
5,000 to 75,000. He had not
built the product yet — but he'd
validated that people wanted it.
Minimum Viable Product (MVP)
The video was the MVP. They
validated demand before
writing a single line of code.
 When the Product Sells Itself
Traditional Sales-Led Product-Led Growth (PLG)
Sales team pitches product → User discovers product → tries it
closes deal → customer onboards free → gets immediate value →
→ maybe uses it → maybe upgrades → invites team → viral
renews growth
 Product-Led Growth (PLG)
Users Sign Up Experience Value
Self-serve — no They hit the
Salesperson required "aha moment" quickly

Convert & Grow Invite Others

Free users upgrade. The product itself
Revenue grows drives sharing
organically.
 How Slack Grew Without a
Traditional Sales Force
Slack launched in 2013 with a free tier that let small teams try it
instantly. No sales call. No demo. Just sign up and start messaging.
Teams loved it so much they brought it into their companies —
from the bottom up. Within 24 hours of launch, 8,000 companies
signed up.

8K $27B
Companies Acquired
Signed up on launch day alone By Salesforce in 2020
How Slack Grew Without a Traditional
Sales Force
Slack's growth was almost
entirely product-led. Their PM
team focused over onboarding,
notifications, and integrations
— making the product so
"sticky" that users naturally
pulled their entire organization
in.
Expansion into New
Industries and Domains
(Present)
Product Management Goes
Everywhere
Product management was once the
exclusive domain of tech companies.
Not anymore.
Expansion into New
Industries and Domains
(Present)
Product Management Goes
Everywhere
Today, hospitals, banks, schools, and
entertainment companies all have
product teams — applying the same
playbook to radically different
problems.
 Product Management Is No Longer
Just a Tech Job

Healthcare Finance Education Entertainment

PMs manage telemedicine Fintech PMs build mobile EdTech PMs design PMs at Disney+, Spotify,
platforms, patient apps, banking apps, robo- learning experiences on and YouTube manage the
and hospital management advisors, and payment platforms like Coursera features, algorithms, and
systems — where poor systems that millions use and Duolingo, applying experiences that keep
UX can have life-or-death daily — like Venmo and gamification and data to billions of users engaged.
consequences. Robinhood. drive engagement.
Emphasis on Customer Experience and
Design Thinking (Present)
The Customer Is Now Central
to Everything
Today's most successful product
managers don't just build
features — they architect
experiences.
Emphasis on Customer Experience and
Design Thinking (Present)
The Customer Is Now Central
to Everything
The shift to Customer
Experience (CX) and Design
Thinking marks the most
human-centered chapter in
product management history.
Customer Experience
•It is every single interaction a
customer has with your
product — from seeing an ad,
to signing up, to using a feature,
to calling support, to canceling.
 Customer Experience (CX) Journey
Awareness
First time they hear about you
Consideration
Comparing you to alternatives
Onboarding
First impression inside the product
Regular Use
Habit formation and value delivery
Advocacy
They recommend you to others
Why CX Matters in Numbers
89% 5x
of Customers Cost More
Switch to a competitor after To acquire a new customer
a poor experience (Gartner) vs. retain an existing one
Customer Experience
Apple is the defining case study
in customer experience. Every
detail — the unboxing, the feel
of the device, the simplicity of
setup, even the way the box
opens — is intentionally
designed to evoke emotion.
Customer Experience
Steve Jobs famously said:
"Design is not just what it looks
like. Design is how it works."
Apple’s product managers own
the experience from first touch
to final sale.
Design Thinking

Empathize Define Ideate Prototype Test

Design thinking is a problem-solving mindset.

Design Thinking

Empathize Define Ideate Prototype Test

Design thinking forces PMs to start with the user's reality before
jumping to solutions.
Design Thinking

Empathize Define Ideate Prototype Test

The goal: solve the right problem, not just build a feature.
 Three Key Design Thinking Tools

Empathy Mapping Journey Mapping Prototyping & Testing

Document what users Visualize every step a Build rough, fast, cheap
think, feel, say, and do customer takes — and versions of ideas and
to surface unspoken every emotion they feel test them with real
needs and frustrations — to find the moments users before
beneath the surface. that make or break the committing to full
experience. development.
 Three Key Design Thinking Tools

Empathy Mapping Journey Mapping Prototyping & Testing

Example: An empathy Example: Airbnb used Example: IDEO
map for a banking app journey mapping to famously prototyped a
might reveal that users discover that guests hospital patient
feel anxious every time were most anxious in experience by acting as
they check their the 48 hours before patients themselves —
balance — unlocking a check-in — leading to a and discovered insights
redesign opportunity. redesigned pre-arrival no survey could have
communication flow. revealed.
Airbnb: Design Thinking That Saved
a Startup
The $40 Camera That
Changed Everything
In 2009, Airbnb was struggling.
Revenue was flat. The founders
used design thinking to
investigate: they personally
visited hosts in New York and
empathized with their reality.
Airbnb: Design Thinking That Saved
a Startup
The $40 Camera That
Changed Everything
Discovery: photos were
terrible. Nobody trusted listings
with blurry phone photos.
Airbnb: Design Thinking That Saved
a Startup
The $40 Camera That
Changed Everything
Solution: Airbnb rented a
camera and took professional
photos for their first NYC hosts.
Revenue doubled within a
week. A $40 decision. An
observation only empathy
could have surfaced.
 The Big Picture:
How It All Fits Together
1950s–1980s 1
One Clear Direction
Engineering & Lifecycle Focus
2 1980s–1990s Every era moved
Software & Agile Methods Product Management
1990s–2000s 3
in the same direction:
Internet & Digital Products
4 2000s–Present
closer to the
Data-Driven Decisions customer.
2010s–Present 5
Lean & Product-Led Growth
6 Present
CX, Design Thinking &
New Industries
 The Big Picture:
How It All Fits Together
1950s–1980s 1
One Clear Direction
Engineering & Lifecycle Focus
2 1980s–1990s From managing factory
Software & Agile Methods outputs → to managing
1990s–2000s 3 user experiences. From
Internet & Digital Products internal engineering
4 2000s–Present
meetings → to empathy
Data-Driven Decisions
5 maps and user
2010s–Present
Lean & Product-Led Growth interviews. From
6 Present shipping products → to
CX, Design Thinking & delivering value.
New Industries
 The Big Picture:
How It All Fits Together
1950s–1980s 1
One Clear Direction
Engineering & Lifecycle Focus
2 1980s–1990s The PM discipline will
Software & Agile Methods keep evolving — AI,
1990s–2000s 3 voice interfaces, and AR
Internet & Digital Products are already reshaping
4 2000s–Present
the field. But the core
Data-Driven Decisions
5 principle won't change:
2010s–Present
Lean & Product-Led Growth understand your user
6 Present deeply, then build the
CX, Design Thinking & right thing.
New Industries
The Through-Line of 70 Years of
Product Management

Build for people.

Always.