Product Management requires a broad set of skills—from market research to UX to branding to technical chops—with one core responsibility: building a product that maximizes value for users within business constraints.
Product Management is not simple. When I first heard the term and its attached responsibilities, my first reaction was: where will I find a single individual who possesses all these diverse skill sets? And if at all I find someone so capable, they will be insanely expensive.
The truth is, Product Management evolved quickly into a diverse set of roles, each a bundle of various skill sets. Only one of those roles is the Product Manager — which is the focus of this lesson.
Your actual job as a Product Manager is to own the success or failure of a product. That means owning the business strategy, design vision, and working closely with engineering. You are accountable for delivering value to users, balancing their needs with business constraints.
Product Management balances conflicting priorities to maximize value
Consider Facebook: it makes money by selling ads, which interrupt the user experience. The delightful experience would be a news feed without ads, but then Facebook would have no revenue and would shut down. This tension — balancing the demands of content consumers versus ad publishers — is exactly the kind of problem Product Management tries to solve.
This balancing act requires a broad set of skills, as diverse as market research, UX, branding, and technical understanding. But the core responsibility remains: building a product that maximizes sales revenue, market share, and profit margins by maximizing the value users can derive.
The Product Manager role is diverse and overlaps with other specialties
The Product Manager typically owns business strategy, design, and engineering skill sets. This role overlaps with others like Product Marketing, but what makes the Product Manager stand out is the accountability for product success.
The product management domain includes several focused specialties:
- Technical PM: Deep technical knowledge, often found in software companies.
- Product Strategist: Focused on long-term vision and market positioning, usually in large corporations.
- Tactical Product Marketing: Concentrates on go-to-market, messaging, and demand generation.
In many organizations, these roles might be combined or split differently, but understanding these distinctions helps reduce role confusion.
Product leadership offsite at a mid-sized Indian startup
Head of Engineering: “We have lots of feature requests from sales. Should we build them all?”
You (Product Manager): “Not all requests translate to user value. We need to validate which solve real problems before committing engineering time.”
Head of Sales: “But our clients are asking for them. Isn't that validation?”
You (Product Manager): “Client asks don’t always equal product success. We balance business, user, and engineering constraints to decide what to build.”
This conversation captures the essence of the PM role: mediator, decision-maker, and value owner.
Deciding what to build amid conflicting stakeholder demands
The product management lifecycle is end-to-end
Managing a product means guiding it through its entire lifecycle: ideation, development, deployment, marketing, customer feedback, and iteration. This continuous cycle aims to maximize the value that customers derive — within the constraints of the business.
You will hear a lot about “discovery” and “delivery.” Discovery is about understanding user needs and validating ideas. Delivery is about working with engineering and design to build and launch. Both are your responsibility.
The PM Triangle: understanding different PM focuses
The PM role can be visualized as a triangle with three corners representing core skill areas:
| Corner | Focus Area | Common Titles |
|---|---|---|
| Technical | Engineering collaboration, APIs, architecture | Technical PM, TPM |
| Strategy | Market analysis, business model, vision | Product Strategist, Group PM |
| Marketing | Go-to-market, positioning, demand generation | Product Marketing Manager |
Your strength or focus may lean more towards one corner, but great PMs understand and engage with all three.
Product Manager vs. other related roles
Many people confuse Product Management with other roles. Here is how they differ:
| Role | How it differs from PM |
|---|---|
| Project Manager | Manages timelines and delivery but does not decide what to build. PM defines the what and why. |
| Product Owner | Agile role focused on backlog management and sprint execution; often overlaps with PM but narrower in scope. |
| Business Analyst | Translates stakeholder requirements; PM pushes back based on user needs and strategic priorities. |
| UX Designer | Owns the user interface and experience; PM defines the problem and prioritizes features. |
| Engineering Manager | Manages engineering team and technical execution; PM owns product vision and trade-offs. |
The cleanest way to think about it: The PM owns the value delivered. The Project Manager owns the delivery plan. The Engineering Manager owns the people who build it.
What does a Product Manager actually do?
Your job breaks down into three core responsibilities:
-
Decide what to build. Not what the loudest stakeholder demands, but what creates the most value for users and the business. This requires user research, data analysis, and market understanding.
-
Get it built. You don’t write code or design screens. You align engineering, design, QA, and data teams around a shared understanding of the problem and solution. You remove blockers and make trade-offs.
-
Make sure it works. Shipping is not the finish line. You measure whether the feature actually changed the metrics you predicted, whether users adopted it, and what you learned. Then you iterate.
The origins of Product Management
Product Management’s roots go back to 1931, when Neil McElroy at Procter & Gamble wrote an 800-word memo defining "Brand Managers" who would be responsible end-to-end for their products — from sales tracking to product definition to promotions. This customer-centric role laid the foundation for modern product management.
Assessing product opportunities is a core PM skill
You will learn frameworks to source and evaluate product opportunities. The key questions are:
- How do we identify opportunities that matter?
- Which opportunities should we invest time and money in?
We analyze opportunity fit across three dimensions:
- Product-Market Fit: Does the product solve a meaningful problem for a target market?
- Product-Company Fit: Does the opportunity align with the company’s strengths and strategy?
- Product-Business Fit: Is the opportunity economically viable and scalable?
One framework to understand unmet needs is the Jobs to Be Done approach — focusing on the real tasks users hire a product to do.
The output of this assessment is an Opportunity Brief: a business case with a clear Go/No-Go recommendation to invest resources and start discovery.
Discovery and requirements definition are at the heart of product success
Once you identify a target opportunity, you lead an iterative process to:
- Discover user needs and validate hypotheses,
- Define and refine requirements,
- Prototype a Minimum Viable Product (MVP),
- Test with customers for functionality, usability, and business viability.
These early decisions often determine whether a product succeeds or fails.
You will learn to write user stories and Market Requirements Documents to communicate effectively.
Pick a product you use regularly. Apply the Product-Market, Product-Company, and Product-Business fit lenses. Write an Opportunity Brief recommending whether to invest in a new feature or product idea.
Test yourself: Prioritizing conflicting demands
You are a PM at a Series A fintech startup in Bangalore. The CEO wants a new dashboard for investors within two weeks. Sales is pressing for a feature requested by a key client, and engineering is blocked waiting for specs on a critical API migration.
The call: How do you prioritize these demands, and how do you communicate your decision to stakeholders?
Your reasoning:
You are a PM at a Series A fintech startup in Bangalore. The CEO wants a new dashboard for investors within two weeks. Sales is pressing for a feature requested by a key client, and engineering is blocked waiting for specs on a critical API migration.
Your task: How do you prioritize these demands, and how do you communicate your decision to stakeholders?
your reasoning:
The Product Manager is the ultimate owner of product success
This is what sets PMs apart: you are responsible for the success or failure of the product. That means you must:
- Collaborate with stakeholders across business, design, and engineering,
- Make trade-offs and decisions about what to build,
- Ensure the product delivers real value to users,
- Measure outcomes and iterate.
This accountability is the core of product management.
Where to go next
- If you want to learn how to think like a PM: Product Thinking
- If you want to master discovery and user research: User Research Methods
- If you want to understand how to measure success: Metrics and KPIs
- If you want to prepare for PM interviews: PM Interviews
PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, Amazon, and many other companies.