Career guides

Product manager vs consultant: which work suits you?

Both jobs are about making decisions with incomplete information. The difference is ownership and pace. A consultant advises a client on one problem and moves to the next. A product manager owns one product and lives with the results of their decisions for months or years.

The work, side by side

Product managerConsultant
The core questionWhat should we build next, and why?What should this client do about this problem?
A typical weekTalking to users · choosing what to build · writing clear specsFraming a client’s problem · analysis against a deadline · presenting a recommendation
Who you work withEngineers, designers, users and your own company’s leadersYour project team and the client’s managers and staff
How long a problem lastsAs long as you own the productAs long as the engagement
What success looks likeUsers and the business are better off after what you shippedThe client acts on your recommendation

Try one decision from each

Product · sample decision

You’re the product manager for a budgeting app built for college students. Engineering has room for exactly one piece of work this month.

Your team can only build one feature this month. What would you prioritize?

The four options: fix onboarding, build bank sync, fix the login bug, or build the partner dashboard. Each one is reasonable, and the one you reach for first says something about how you think.

Try this decision free on Compass. It takes a few minutes, and nobody scores you.

How people in the role see it: Product managers make calls like this every week, usually with incomplete information. There’s rarely one right answer. What matters is how clearly you can explain the trade-off.

Consulting · sample decision

You’re on a team advising a national coffee chain. Profits have fallen sharply this year, and the partner wants your first view by tomorrow morning.

You have one day. Where do you start?

The four options: break down the numbers, talk to store managers, study the competition, or commit to a hypothesis. Each one is reasonable, and the one you reach for first says something about how you think.

Try this decision free on Compass. It takes a few minutes, and nobody scores you.

How people in the role see it: Consultants work to tight deadlines on unfamiliar problems. Much of the job is deciding what to look at first, and what to ignore.

Signals to compare

After trying both, ask yourself which call you wanted to keep thinking about. If owning the outcome and going deep energised you, that points towards product. If the speed of a new problem and making the case energised you, that points towards consulting. These are signals, not verdicts. The decision stays yours.

Strategy consulting vs product management

If you’re weighing strategy consulting specifically, the contrast is sharper: strategy work stays at the level of “what should the company do”, while product work goes all the way to “what exactly do we build, and is it working”. Try writing both a one-page recommendation and a one-page feature plan, and see which you enjoyed finishing.

Common questions

Which pays more?

It depends on the company, the city and the level, and figures online are often out of date. Your college’s placement report and seniors’ recent offers are better guides than averages.

Can you move from consulting to product later?

Some people do. Structuring problems and making a case carry over well. Moving the other way happens too. Choose the one you’d enjoy first, not the one you think keeps the most doors open.

Try the work before you choose it

Compass lets you try a realistic decision from each path you’re weighing, notice how it felt, and choose your next step with evidence. The preview on our home page is free.

Try a free decision

Weighing two or three paths seriously? See our packages, each prepared and reviewed by a person.

Related guides