The Enterprise PM's Advantage: Why Systems-Thinking Makes You Better at Consumer Products

When you've built a TMS, you understand why the bank has that rule

At Mahindra Logistics, I built a Transportation Management System from scratch. SAP Ariba integration for invoicing, MapMyIndia for track-and-trace, a load optimizer that had to account for Mahindra's specific auto and farm sector requirements. Nobody was going to use this product casually. It had to work, within constraints, every time.

That experience gave me something consumer-first PMs sometimes lack: genuine respect for constraints. When I now build financial wellness features inside Chase's connected banking platform, and someone from compliance says "we can't show that number without this disclosure," I don't treat it as a blocker to route around. I treat it as a system requirement. I ask: what's the underlying concern? Can we achieve the user goal within the constraint, or does the constraint need to be renegotiated at a higher level?

That's a muscle that enterprise builds. Not learned in a workshop.

Thinking about the plumbing

At Wipro, I worked on Google Maps Business APIs. My job involved geocoding accuracy, ML pipelines for address creation, and experiment design that could show a 6–10% improvement across millions of data points. I was thinking about infrastructure, not just interface.

When I now look at a consumer banking feature, I instinctively think about the backend. What does the data model look like? How is this transaction categorized? What latency is acceptable before this screen becomes a frustrating experience? Those are questions that a PM who only ever thought about user stories sometimes misses until the sprint review — and by then, the architecture has already baked in the wrong answer.

Understanding the plumbing doesn't mean you should design for the plumbing. The user doesn't care about your data pipeline. But knowing how it works means you can make better tradeoffs when you have to.

NPS is a business outcome, not just a survey

At IBM, we tracked NPS seriously. We moved it 35 points over two years. That wasn't because we ran satisfaction surveys and then nodded at the results. It was because we treated user friction as a product defect. Every session review was a debugging exercise: where did they hesitate? What did they try that didn't work? What did they stop using?

That discipline — treating experience metrics as product signals rather than vanity numbers — is exactly the skill consumer PM teams say they want. The difference is that in enterprise, you often have more direct access to the user (they're your colleagues, or they're in a customer success channel), which forces honesty. Consumer PMs can sometimes hide in aggregate data. Enterprise PMs rarely get that luxury.

The journey isn't from inferior to superior — it's additive

I don't think enterprise PMs are better than consumer PMs, or vice versa. I think the two modes teach you different things, and the people who've done both tend to be the most dangerous PMs in the room.

Consumer taught me to hold the user experience with more care than any enterprise role ever asked me to. Enterprise taught me to respect constraints, understand systems, and treat metrics as signals rather than decorations.

The product I'm trying to build now needs both. Most products do, if they're honest about it.