Understanding Product Management

Product management is not a single skill or a narrowly defined job. It is a complex, multi-faceted discipline that evolved to solve a hard problem: how to build products that deliver maximum value to users while meeting business goals and operating within technical constraints.

This balancing act is the entire profession in one line. Most aspiring PMs underestimate the diversity of skills involved and the accountability that comes with the role. You will hear many definitions, but the actual job is to own the success of the product end-to-end — from ideation through development to market launch and continuous improvement.

That means mastering business strategy, user experience design, and technical understanding — all at once.

The diversity of skills bundled in product management

When I first heard the term Product Management and its attached responsibilities, my immediate thought was: where do you find a single person who possesses all these diverse skill sets? And if you do, they would be insanely expensive.

The reality is that product management evolved quickly into a bundle of roles, each emphasizing different skills. The Product Manager role itself typically owns the intersection of business strategy, design, and engineering. But it overlaps with others like Product Marketing and Technical Product Management. What makes the Product Manager unique is the responsibility and accountability for the product’s success.

Here is a simplified view of the main roles within product management:

The Technical PM is the most common role in India’s startup ecosystem. They work closely with engineering teams and need technical chops along with product sense. The Product Strategist role is rarer and often exists in large companies with dedicated strategy teams. Product Marketing tends to be a separate function but is sometimes combined with PM responsibilities.

You will see companies using these titles differently. The key is to know what skills your role demands and where you add the most value.

What product management actually does

At its core, product management is about managing the product life cycle to maximize value for users and the business. This involves:

• Ideation: Identifying user problems worth solving, validating ideas, and defining product vision.
• Development: Collaborating with design and engineering to build solutions, managing trade-offs, and removing blockers.
• Launch: Planning go-to-market strategies, supporting sales and marketing, and ensuring successful adoption.
• Ongoing management: Monitoring performance, iterating based on feedback, and evolving the product over time.

The PM is accountable for outcomes — revenue, user growth, engagement, retention — not just outputs like features shipped or tickets closed.

This accountability means you must balance conflicting priorities. For example, Facebook earns revenue from advertisers but its users want an ad-free experience. The PM’s job is to find the right balance to maximize overall value.

How product management balances user and business needs

Consider Facebook’s model: users consume content, but advertisers pay the bills. Ads interrupt user experience, yet the business cannot survive without them. The art of product management is to maximize value for both sets of users — content consumers and ad publishers — within technical and business constraints.

This balancing act requires skills across market research, UX design, branding, and technical understanding. The PM must know when to prioritize user delight and when to push for revenue goals.

This broad skill set explains why product management is challenging and why it attracts people from diverse backgrounds.

The origins of product management

Product management is not a new concept. It traces back to 1931 when Neil McElroy, then at Procter & Gamble, wrote an 800-word memo describing the need for Brand Managers responsible end-to-end for a product’s success — from tracking sales to defining product features and promotions.

This customer-centric role laid the foundation for modern product management. It emphasized accountability for the whole product, not just a piece or a function.

Many companies, including Hewlett-Packard, were influenced by this early thinking and built product roles around it.

The product is the sum of its parts — and those parts can be products too

Modern products are complex systems made of many subsystems, each valuable on its own. Instagram is a prime example.

Instagram is the product users pay for via their attention. Features like image feed, filters, and hashtags are components inside Instagram. Internally, these features are often treated as independent products with their own product managers.

This is because as a product grows, its subsystems become complex and valuable enough to require dedicated management. The value of the whole product is the sum of the value delivered by its subsystems plus how they are assembled.

A PM managing the entire product must coordinate these subsystems, ensuring they work together to deliver a cohesive user experience.

The product manager’s unique accountability

Product management overlaps with many roles, but the key differentiator is accountability for the product’s success.

The clearest way to think about it: the PM owns the value delivered. The project manager owns the delivery plan. The engineering manager owns the team that builds.

How product management roles differ by company and product

Not all PM roles are the same. The daily work changes depending on product type, company stage, and market.

The title varies — some companies call B2B PMs “Product Owners.” Platform PMs may be “Technical Product Managers.” The name matters less than understanding what you actually do.

In India, B2B PM roles are growing fastest as the ecosystem matures beyond consumer apps.

The evolution and maturity of product management in India

Product management as a distinct profession is younger in India than many realize. Before 2015, most Indian tech companies had project managers, not true PMs. The role borrowed heavily from Silicon Valley but was often reduced to coordination and documentation.

The profession has passed through three waves:

• Wave 1 (pre-2015): Project managers with product titles. Focus on delivery, no user research or data analysis.
• Wave 2 (2015-2021): The PM gold rush. Rapid startup growth, many PM roles created, but many were glorified project management.
• Wave 3 (2022-now): Market correction. Layoffs hit PMs; the role sharpens to focus on owning outcomes, not pushing tickets.

AI and automation accelerate this shift by taking over coordination tasks. The PM who owns product outcomes remains critical.

The actual job of a product manager

Let me be direct about this: the actual job is to decide what to build, get it built, and make sure it works.

1. Decide what to build. Not what the CEO says or what the loudest customer demands, but what creates the most value given your constraints. This requires user research, data analysis, market understanding, and a point of view.

2. Get it built. Align engineering, design, QA, and data teams around a shared understanding. Remove ambiguity. Make trade-offs. Unblock.

3. Make sure it works. Ship is not the finish line. Measure impact. Did it change the metrics as predicted? Did users adopt it? If not, learn and iterate.

Everything else — roadmaps, PRDs, sprint planning, stakeholder management — is downstream of these three responsibilities.

The trap of confusing PM with project management

In many Indian IT companies, PMs are treated as glorified project managers. The difference is one question: Should we build this at all?

Project managers manage timelines and dependencies. They do not decide what to build.

A PM without opinions about what to build is a project manager with a fancier title. This is the trap to avoid.

The PM’s role in influencing without authority

You will hear PMs called “mini-CEOs of the product.” This is misleading.

A CEO has authority — budgets, hiring, firing, strategy changes. A PM has influence — convincing engineering, design, leadership — without positional authority.

This is what makes the role hard. You are accountable for outcomes you do not fully control. You ship through other people’s hands.

If you need authority to get things done, the role will frustrate you.

The PM is the person in the room who cares most about the customer’s problem and can make trade-offs across business, technology, and design.

How organizational context shapes the PM role

Before worrying about PM types, ask: is your company business-driven or product-driven?

Most Indian startups start business-driven and mature into product-driven. Knowing where your company sits tells you what kind of PM work you will do, regardless of job title.

The profession is younger and evolving

Many Indian companies still confuse PM with project management or product ownership. The profession is evolving rapidly, especially with AI automating coordination tasks.

The PM who owns outcomes, makes trade-offs, and leads without authority will thrive.

Supporting media

Test yourself: The roadmap ambush

You’re two months into your PM role at a B2B SaaS startup. You spent three weeks on user research and built a roadmap focused on fixing onboarding drop-off — your biggest churn driver. Monday morning, product review meeting.

Your CEO says: "The Jio team needs SSO by March. Move it to P0. They’re 40% of our ARR." Your engineering lead looks at you.

What do you say?

• "That's a big call. Let me pull the data on SSO vs onboarding impact and come back tomorrow with options."
• "We can build SSO by March, but we'd need to drop onboarding work. That means churn stays at 12%. Want me to model both scenarios?"
• "Got it. We'll reprioritize and get SSO into this sprint."

Where to go next

• If you want to develop the PM mindset and decision-making skills: Product Thinking
• If you want to understand how to conduct user research effectively: User Research Methods
• If you want to learn how to prioritize and build roadmaps: Product Prioritization
• If you want to prepare for PM interviews: PM Interviews
• If you want to master metrics and evaluating product success: Metrics and KPIs
• If you want to understand product strategy in AI-driven products: AI Product Strategy