Product Management balances conflicting priorities to maximize the value users can derive within business constraints.
Product management is taking a product through its full lifecycle — from ideation, development, deployment, marketing, to customer feedback — and then repeating the cycle to maximize the value customers get within the constraints of the business. This is the actual job: continuously creating value while balancing competing demands.
The trap is to think product management is only about building features or writing specs. It is a cross-functional leadership challenge that requires a broad skill set — from market research to user experience to branding to technical understanding.
Let me illustrate the art of product management with a real-world example. Facebook makes money by selling ads. Ads are fundamentally a poor experience for users since they interrupt their usage. The ideal experience would be a news feed with no ads or promotional material. After all, who wants to see the 10 millionth cat video from a random stranger?
But if Facebook removed all ads, it wouldn’t make money and would have to shut down. This is the exact tension product management must solve: balancing the conflicting priorities of content consumers who want a delightful experience and ad publishers who pay for the platform. Product management is the discipline that navigates this balance to maximize overall value.
This is not a simple trade-off. It involves understanding who the real customers are. We, as users, consume content, but the paying customers are the advertisers. How to balance these two sets of users — content consumers and ad publishers — is the kind of problem product management solves every day.
The broad skills of product management
Product management requires a wide-ranging set of skills because the role touches every part of the product and business. To succeed, you need a combination of:
- Market research: Understanding the users, the competition, and the market size and opportunity.
- User experience (UX): Knowing how to design products that are usable, delightful, and solve real problems.
- Branding and marketing: Building a product’s identity and positioning it effectively in the market.
- Technical chops: A working understanding of the technology stack, APIs, and software development processes.
- Business acumen: Crafting business cases, pricing strategies, and aligning product goals with company objectives.
The core responsibility of product management is building a product that maximizes sales revenue, market share, and profit margins by maximizing the value users derive. This focus on user experience is part of the role’s origins.
Product management’s origins: a 1931 memo
Product management is not a new discipline. Its roots trace back to a memo written by Neil McElroy at Procter & Gamble in 1931. McElroy wrote an 800-word memo to justify hiring two new Brand Managers, defining their role as being absolutely responsible for a brand end to end — from tracking sales to defining the product to promotions.
This memo not only secured those hires but also set the direction for a customer-centric role that would evolve into modern product management. McElroy’s ideas influenced companies like Hewlett-Packard, shaping a discipline focused on ownership and accountability for the product’s success.
If you want to read more about this fascinating history, I recommend these articles:
- https://www.mindtheproduct.com/2015/10/history-evolution-product-management/
- http://queue.acm.org/detail.cfm?id=2683579
- https://www.oreilly.com/ideas/the-evolving-role-of-product-management
The complexity of the product manager role
When I first heard the term product management and its attached responsibilities, my first reaction was: where will I find a single individual who possesses all these diverse skills? And if I do find someone, they will be insanely expensive.
The reality is that product management has evolved into a diverse set of roles, each a bundle of particular skill sets. Only one of these roles is the traditional Product Manager, which we will discuss in detail in this course. Here, I want to introduce the various roles that have emerged within the product management domain.
The Product Manager: owning strategy, design, and engineering
The Product Manager typically owns the business strategy, product design, and engineering coordination. This role overlaps with Product Marketing but is distinct because the Product Manager is ultimately accountable for the success of the product.
The Product Manager decides what to build, works with design and engineering on how to build it, and aligns stakeholders on why it matters. This accountability for the product’s success sets the Product Manager apart.
The PM Triangle: understanding product management specialties
Product management can be visualized as a triangle with three corners, each representing a specialty:
| Corner | Focus Area | Common Titles |
|---|---|---|
| Technical | Deep technical knowledge, product definition, and engineering collaboration | Technical PM, Product Owner, Technical Strategist |
| Marketing | Driving market presence, sales enablement, and go-to-market execution | Tactical Product Marketing, Product Marketing Manager |
| Strategy | Business planning, market segmentation, and long-term product vision | Product Strategist, Strategic Product Marketing |
Technical Strategy: The Product Owner (PO)
Along the technical and strategy edge of the triangle lies the Product Owner role, well-known in Agile development. The PO focuses on defining the product, user stories, and guiding the development team. They own the short- and long-term roadmap, feature prioritization, and product evolution.
Titles like Strategic Product Manager, Roadmap Architect, and Technical Strategist describe this focus.
Technical Marketing: The Technical Product Marketer (TPM)
This role straddles marketing and technical domains. The TPM drives product definition and guides development while also owning product marketing efforts like launches, demos, and customer engagement.
They must balance business needs for market presence and sales with technical product knowledge. TPMs are often considered the ultimate product experts within many firms and may be called Product Marketing or Technical Market Planning.
Marketing Strategy: Strategic Product Marketing (SPM)
This corner focuses on market-facing strategy: business plans, go-to-market (GTM) strategies, buyer personas, launch planning, and sales enablement.
Unlike tactical product marketing, which is content-focused, strategic marketing adds broader business considerations, guiding a product through awareness, purchase, and advocacy stages.
Titles include Digital Product Marketing, Category Management, Business Management, and Strategic Product Marketing.
The PM Triangle in practice
Here is a complete view of the PM Triangle showing the concentration of various roles:
- Technical PMs focus heavily on engineering collaboration and product definition.
- Tactical Product Marketers focus on immediate marketing needs and customer engagement.
- Product Strategists focus on long-term vision and market positioning.
Understanding this model helps reduce role confusion in mid- to large-sized organizations. It is especially important to identify functional gaps and leverage each PM’s strengths to cover all corners and edges of the triangle.
The PM’s influence without authority
A common misconception is that Product Managers have authority over engineers, designers, and other stakeholders. The truth is the opposite.
No one reports to the Product Manager. Instead, the PM leads by influence — through subject matter expertise, clarity of vision, and effective communication.
This is why the term “Manager” is a misnomer. A better term is “Product Leader.” Your job is to lead people without formal authority, rallying opinions around the product’s value and aligning cross-functional teams.
This lack of direct authority is what makes the role challenging but also uniquely satisfying. You are accountable for the product’s outcome but must achieve it through influence.
The Product Manager is not a mini-CEO
You will often hear the phrase “Product Manager is the mini-CEO of the product.” This is misleading.
A CEO has authority — to hire, fire, set budgets, and make unilateral decisions. A Product Manager has influence but no direct authority over team members.
Your power comes from your expertise, your ability to synthesize inputs, and your clarity of vision. You must convince engineering, design, marketing, and business teams to align without formal power.
Understanding this distinction is crucial to succeeding in product leadership.
Product management deliverables and tasks
Product management covers a wide range of deliverables and tasks. Here are some common ones:
- Defining the product vision and strategy
- Conducting market and user research
- Writing product requirements and user stories
- Prioritizing features and managing the roadmap
- Coordinating cross-functional teams
- Launch planning and go-to-market support
- Measuring product performance and iterating
If some of these terms are unfamiliar, don’t worry. We will cover them in detail throughout this course.
The evolving landscape of product roles in organizations
Organizations define product roles differently. You will find titles like Product Manager, Program Manager, Project Manager, Product Marketing Manager, Product Designer, and Technical Product Manager.
The overlap and boundaries depend on company size, culture, and maturity.
Understanding where you fit in this spectrum and which skills you need to develop will help you succeed.
Additional reading
For deeper insights into product management roles and evolution, refer to this resource:
https://drive.google.com/file/d/0B3ULRtlpdQd2X1dBNF91WUp4V00/view
Test yourself: Role clarity at a growing startup
You join a Series A SaaS startup in Bangalore as their first Product Manager. The CEO expects you to handle product strategy, design inputs, engineering coordination, and marketing. The marketing head expects you to handle all product marketing. Engineering expects clear specs and timelines. You have limited resources and no direct reports.
The call: How do you prioritize your responsibilities and communicate your role boundaries to your stakeholders?
Your reasoning:
Where to go next
- If you want to understand how to think like a product leader: Product Thinking
- If you want to learn how to break into product management: Breaking Into PM
- If you want to develop your product strategy skills: Product Vision and Strategy
- If you want to master stakeholder management: Stakeholder Management
- If you want to learn about Agile product development: Agile Fundamentals