The Job of Product Management Is Not to Be Liked
The Myth of the Popular PM
In the early days at Intugine, I watched product managers try to navigate the tension between sales teams and engineering. The path of least resistance was always to say yes. Yes to the custom integration that only one client wanted, yes to the complex dashboard tweak that broke the load balancer, and yes to the tight deadline the engineering lead already flagged as impossible. They wanted to be liked. They wanted the stakeholders to leave the meeting happy. In doing so, they optimized for comfort rather than product integrity.
Being a product manager is fundamentally an adversarial role. If you are doing your job correctly, you will frequently be the person who brings bad news. You are the filter that sits between infinite customer demands and finite development cycles. If your team thinks you are the most agreeable person in the company, you are likely failing the product.
The job of a product manager is to absorb the discomfort of trade-offs so that the engineering team can build with clarity.
Why Consensus Kills Innovation
In the Indian enterprise SaaS ecosystem, the temptation to over-customize is high. You land a marquee client who pays a significant annual contract value, and they demand a specific feature that is entirely tangential to your core value proposition—in our case, real-time supply chain visibility. If you are seeking approval, you build the feature. You add technical debt. You bloat the product. You lose focus.
Building a world-class product requires saying no to ninety percent of requests. When you say no, people get annoyed. They might even complain to your boss. That is the cost of doing the job. You aren't there to be a project coordinator or a glorified note-taker for sales meetings; you are there to protect the integrity of the product roadmap.
Defining Your Role as a Utility, Not a Friend
To move from being a 'liked' PM to a 'useful' PM, you need to shift your mental model. Your utility isn't measured by the number of people who smile after a sprint planning session. It is measured by:
- Risk Mitigation: How effectively did you identify that a feature would create an infinite support loop for the operations team?
- Outcome Focus: Did you push back on a UI change because it looked pretty, even though the data showed that the existing workflow was faster for the warehouse supervisor on the ground?
- Conflict Resolution: Did you navigate the friction between sales incentives and engineering capacity without letting the product quality degrade?
The Anatomy of Hard Decisions
True product leadership is about absorbing uncertainty. Your engineering team craves stability, and your customers crave certainty. When you act as a human shield against scope creep, you are providing a service. You are buying them the quiet, focused time required to ship high-quality code. When I look back at our most successful deployments—those where we integrated with complex ERP systems across hundreds of transit points—it was never because we made everyone happy. It was because we were decisive about what we would not do.
Next time you find yourself nodding along to a request you know is wrong just to avoid a difficult conversation, pause. Ask yourself if you are building a legacy or just managing a social dynamic. If you want to be liked, go buy your team lunch. If you want to build something that actually moves the needle, be prepared to sit with the discomfort of being the person who said no.