Consulting vs. Building — Why the Best Product Leaders Have Done Both

What consulting actually teaches you

The caricature of consulting is someone who produces decks and moves on before anything ships. That version exists. But the consulting work I did at IndusVed was fundamentally different: I was embedded with technology companies, helping them build operational muscle from the inside.

Here's what that experience gives you that most product roles don't:

You see the same problems in different companies simultaneously. A consulting career is a fast-forward through ten years of pattern recognition. You learn what "good product process looks like" not by reading about it but by watching three different companies fail at it in three different ways in the same quarter.

You get comfortable with diagnosis before prescription. The instinct to jump to solutions is the biggest anti-pattern in product management. Consulting trains you to spend the uncomfortable time in problem space before moving to solution space — because you're accountable for the recommendation, not just the idea.

You learn to make decisions with incomplete information, fast. Clients don't wait. Consultants who need perfect information before advising don't last long.

What building teaches you that consulting never can

Here's the equally honest truth: consulting alone produces PMs who are great at framing problems and weak on the accountability that comes from actually shipping.

When you're a founder or a product leader who owns the roadmap, the prioritization trade-offs become viscerally real. You can't recommend "invest in discovery" and move to the next client. You have to do the discovery, ship the feature, watch the metrics, and own the outcome when it doesn't move.

Building taught me what I'd call the weight of the decision. Every choice has a cost. Saying yes to a feature is saying no to three others. Consulting trains your diagnostic muscle; building develops your decision discipline.

The combination is the point

The product leaders I respect most have usually done both — not always in the same career, but often in the same role. The best PMs consult internally: they diagnose, they recommend, they align stakeholders. But they also build: they own the roadmap, they feel the pressure of shipping, they live with the decisions they made six months ago.

At Eccentric, I carry both hats every day. The Director of Strategy role asks me to zoom out, diagnose the market, and set direction. The Head of Product role asks me to zoom in, prioritize ruthlessly, and ship. The tension between those two orientations is, I've come to believe, exactly what makes the product better.

My advice to PMs choosing their path

If you're early in your career and have the option to do a stint in consulting — take it. Not because it's more prestigious, but because the exposure to multiple organizations and problem types compresses your learning curve dramatically.

If you're a consultant thinking about making the jump to a product role — do it. And when you do, commit fully to the accountability side of the job. The diagnosis skills will carry over. The ownership muscle needs to be built fresh.

The best version of a product leader is someone who can think like a consultant and act like a founder. That combination is rarer than it should be — and more valuable than almost anything else in the market.