It is important to understand that as a product manager, you are only accountable for the product and do not have any authority over designers, developers and other stakeholders. You will typically be reporting to the CEO. And this is by design.
Product management is often misunderstood as a one-size-fits-all role with enormous authority. The reality is quite different. A product manager is the ultimate role accountable for the success or failure of the product — but with no direct authority over the engineers, designers, or other stakeholders who build it. This is by design.
Getting work done as a PM depends on influence, logical reasoning, and subject matter expertise. You earn respect and alignment by demonstrating command over the product space, not by issuing orders. The role is closer to that of a CEO without the power to hire, fire, or assign tasks. This tension is what makes the job daunting — and incredibly satisfying.
The product manager’s accountability is total, but authority is zero
You will typically report to the CEO or a senior leader, but no one reports to you. Imagine the dynamics if designers or engineers reported directly to the PM — they would not be truthful or open. Instead, your job is to lead through influence.
Your influence must be built on clarity of vision, data-backed decisions, and the ability to communicate value convincingly. You coordinate a cross-functional team — design, engineering, marketing, business — to deliver a product that meets user needs and business goals.
This may sound overwhelming. It is. But it is also the essence of product leadership.
The five skill buckets of a good product manager
Product managers need a broad and diverse skill set that spans multiple domains. Talvinder organizes these into five buckets — design, engineering, business, influencing, and synthesis — each crucial to the role.
Design Skills
- Understanding visual design patterns and human-computer interaction (HCI) guidelines
- Applying UX principles to create intuitive experiences
- Conducting advanced user research to uncover real needs
- Designing information architecture for clarity and discoverability
Engineering Skills
- Grasping how APIs work and how mobile and web apps function
- Understanding database architecture and notification systems
- Knowing the basics of AI/ML and A/B testing frameworks
- Familiarity with the MCP (Minimum Capability Product) framework for scoping
Business Skills
- Pricing strategies and evaluating market opportunities
- Creating and prioritizing business cases for ideas and features
- Segmenting users and understanding product-market fit
- Conducting market research, sizing, and competitive analysis
- Assessing product-organization fit and sustainability of the business model
Influencing Skills
- Rallying opinions around product value and evangelizing vision
- Active listening, conflict resolution, and decision making
- Establishing a common language between business, tech, and users
- Engaging stakeholders across levels, including CxO conversations
- Mastering storytelling, elevator pitches, and even 'Jedi Mind Tricks' for persuasion
- Personal leadership to inspire and guide teams without authority
Synthesis Skills
- Taking inputs from diverse sources and synthesizing them into a coherent vision
- Building product strategy grounded in research and innovation
- Collaborating with business analysts, designers, developers, and customers
- Maintaining a holistic view of the product lifecycle and market dynamics
Product leadership workshop at a Bangalore SaaS startup
You (PM): “Our engineering team raised concerns about the API latency impacting UX. Let’s prioritize that in the next sprint.”
Engineering Lead: “Agreed, but we need business buy-in since it affects timelines.”
You (PM): “I’ll coordinate with sales and marketing to align expectations and communicate the trade-offs clearly.”
Product Designer: “I’ll prepare updated wireframes to reflect the new flow once latency improves.”
This is how product managers synthesize inputs and lead cross-functional teams without direct authority.
Balancing technical constraints, business needs, and user experience
The “mini-CEO” myth: why PMs have accountability without authority
You will hear the phrase "Product Manager is the mini-CEO of the product" frequently. This is misleading and often harmful.
A CEO has authority — they can hire, fire, set budgets, and make unilateral decisions. A PM has influence — they must convince others to build what matters without positional power.
This lack of authority is the uncomfortable reality of the role. You are accountable for outcomes you do not fully control. You ship through other people's hands.
The actual job is to be the person in the room who cares most about the customer’s problem and has enough context about business, technology, and design to make trade-offs.
If you need authority to get things done, you will be frustrated. If you are comfortable with ambiguity and leading through influence, you will thrive.
How product managers differ from related roles
The product ecosystem includes many roles with overlapping responsibilities. Understanding the distinctions is key.
Product Manager vs Product Owner
The Product Owner role comes from Scrum methodology and focuses on backlog management, sprint planning, and iteration execution. Product Owners are internal-facing and ensure development runs smoothly.
The Product Manager is outward-facing, owning vision, market understanding, and product strategy. PMs direct Product Owners and define quarterly or yearly roadmaps.
| Product Manager | Product Owner |
|---|---|
| Owns vision | Owns implementation |
| Directs Product Owner | Takes direction from PM |
| Delivers release | Delivers iteration |
| Market sensing | Tracks internal deliveries |
| Release objectives | Iteration objectives |
| Strategic direction | Day-to-day direction |
| Market use cases | System use cases |
| Understands overall solution | Understands architecture & design |
| Roadmaps | User acceptance tests |
| Identifies market needs | Writes user stories and acceptance criteria |
Product Manager vs Project Manager
A Project Manager focuses on timelines, budgets, resource coordination, and risk management. They manage the how and when of delivery but do not decide what to build.
A Product Manager defines what to build, why, and for whom. They own business case, product strategy, market research, and customer advocacy.
| Product Manager Tasks | Project Manager Tasks |
|---|---|
| Win/Loss analysis | Scope and budget management |
| Customer visits | Risk planning |
| Tactical support | Coordinate execution |
| Product gap analysis | Monitoring and controlling |
| Business case creation | Completion and formalization |
| Market opportunity definition | |
| Persona creation and user stories | |
| Product requirements and roadmaps | |
| Pricing and product positioning | |
| Product launch planning |
Product Manager vs Product Designer
Product Designers answer "how should it be built?" They explore solution space, create wireframes, prototypes, and optimize user experience.
Product Managers answer "what should be built?" They deeply understand user needs, prioritize ideas, and ensure ROI.
The PM is the expert on the user’s needs; the designer is the second most knowledgeable, tasked with crafting the optimal product manifestation.
Program Manager (Technical PM)
Common in companies like Microsoft, Program Managers are technical product managers embedded in engineering teams. They write detailed specs, manage error cases, and focus on reliable software delivery.
They have less interaction with business and marketing compared to PMs.
The maturity model for product managers
Product leadership develops over time across six core competencies:
| Maturity Level | Description |
|---|---|
| Customer Experience Grounding | Designing customer-centric experiences throughout the user journey |
| Market Orientation | Understanding market trends, partner ecosystems, and competition |
| Business Acumen | Managing strategy, portfolio prioritization, pricing, and financial metrics |
| Technical Skills | Deep knowledge of technology, architecture, roadmaps, and development lifecycle |
| Soft Skills | Leading teams, communicating across functions, and influencing organizational change |
| Enablers | Fostering innovation through talent, culture, and organizational practices |
At senior levels, PMs focus more on strategic leadership and influencing; junior PMs spend more time on operational and tactical execution.
Archetypes of product managers
There are three dominant archetypes, each with distinct profiles and focus areas:
| Archetype | Profile | Focus | Product Type | Indian Company Examples |
|---|---|---|---|---|
| Technologist | Deeply technical | Technology solutions | Back-end platforms, complex B2B | Razorpay (infrastructure), Postman |
| Generalist | Technical depth + business savvy | User delight | B2C products, front-end B2B | Swiggy, Meesho |
| Business-oriented | Business background | Maximizing business metrics | B2C with external creative inputs | Flipkart, PhonePe |
Most companies have a mix depending on product lines.
A day in the life of a product manager is relentless context switching
PMs juggle urgent requests, strategic work, execution, meetings, and stakeholder communication daily.
Typical activities include:
- Attending daily standups and huddles
- Checking product performance and competitive news
- Developing detailed plans for upcoming releases
- Coordinating with partners and internal teams
- Handling last-minute requests and demos
Test yourself: The stakeholder influence challenge
You are a new PM at a Series B fintech (Razorpay scale). Your engineering lead is pushing to build a complex feature that sales believes will not close any deals. The sales lead wants you to prioritize quick wins for the upcoming quarter. The CEO is focused on the roadmap but has limited product knowledge.
The call: How do you decide what to build next, and how do you communicate your prioritization to engineering, sales, and the CEO?
Your reasoning:
You are a new PM at a Series B fintech (Razorpay scale). Your engineering lead is pushing to build a complex feature that sales believes will not close any deals. The sales lead wants you to prioritize quick wins for the upcoming quarter. The CEO is focused on the roadmap but has limited product knowledge.
Your task: How do you decide what to build next, and how do you communicate your prioritization to engineering, sales, and the CEO?
your reasoning:
Identify your current strengths and gaps in the five buckets of product management skills:
- Design: How well do you understand UX principles and user research?
- Engineering: Are you comfortable with technical concepts like APIs and A/B testing?
- Business: Can you evaluate market opportunities and build business cases?
- Influencing: How effective are you at stakeholder communication and persuasion?
- Synthesis: Can you integrate diverse inputs into a coherent product vision?
For each, write down one specific action you will take to improve this month (e.g., read an article, shadow a colleague, practice a pitch).
Where to go next
- If you want to deepen your understanding of product strategy: Product Vision and Strategy
- If you want to learn how to run discovery and user research: User Research Methods
- If you want to master stakeholder communication and influence: Stakeholder Management
- If you want to understand the technical side of products: Technical Fluency for PMs
PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, and Microsoft.