From OMS Consultant to Product Owner — What Actually Transferred

5 MINS

I started my career as a Sterling OMS consultant at Cognizant and IBM. Today I run roadmap and discovery for a fleet SaaS product at Verizon Connect. People assume the move from consultant to product owner is a clean break. In my experience, it isn't. Most of the muscles I use today were trained in the OMS years — I just didn't know what to call them.

What I thought transferred (and didn't)

I assumed my OMS knowledge — pick paths, alert frameworks, EAR builds, Cognos dashboards — would be the headline. It's not. Every product I've owned since has had a different domain. The deep technical knowledge of any specific platform fades within two years of leaving it.

What stays is the shape of how you think about a system.

A retail OMS taught me to think in events, not screens.

ETL migrations taught me to plan for the rollback before the rollout.

UAT in Sterling taught me that go/no-go decisions are political, not technical. Those reflexes show up every day in product ownership, even when the domain is fleet, in-flight retail, or compliance.

The consultant skill nobody talks about

The most underrated thing consulting taught me is *how to disagree with a senior stakeholder without losing the room*. As a consultant, you have no organisational power. You can't fire anyone, you can't promote anyone, and you don't own the budget. The only thing you have is the quality of your argument and the relationship.

That maps directly to being a product owner. A PO who tries to win by authority loses fast. A PO who can frame a hard truth in a way the stakeholder can repeat to their own boss — that PO ships things.

When I had to push back on a "just ship it" CARB compliance ask at Verizon, I didn't escalate. I framed the trade-off as a choice the leader could own publicly. They picked the right one. That move came straight from a Cognizant deck I wrote in 2013.

What I'd tell my younger self

If I could send a note back to 2014-me, mid-IBM, hammering on a Sterling EAR at 11 p.m., it would be three things:

The platform is not the career. The platform is the gym. The reps are what matter.

Pay attention to which decisions hurt later. Those are the architecture decisions, even if nobody calls them that. Especially the ones a PM signs off on under time pressure.

Write the user-facing story even when you're an engineer. It's the cheapest way to learn product without changing your job title.

The bridge

The bridge from OMS consultant to product owner wasn't a course or a certification — even the ones I did take. It was learning that the work is fundamentally the same: figure out what the business actually needs, translate it into something a team can build, and stay close enough to the user to know when the spec was wrong.

The job title changes. The job doesn't.

Why an EV Suitability Tool Was Worth Betting On

Discovery and Delivery Are Not the Same Sport

Projjal skipped presentations and built real AI products.

Projjal Dhar was part of the March 2026 cohort at Curious PM, alongside 17 other talented participants.