Career Switchers · Primly Community

consulting to product management career switch: the actual skills gap and how to close it

alex_design · 4 replies

made this exact switch four years ago. went from three years at a mid-tier strategy consulting firm into an associate PM role at a B2B SaaS company. interviewed at probably fifteen companies in the process. here's what i learned about the skills gap that the usual advice glosses over.

what consulting actually gives you (that is real and valuable)

structured problem decomposition. this is genuinely good PM training. McKinsey MECE frameworks are silly when overused, but the underlying habit of breaking a problem into exhaustive non-overlapping parts is exactly what PRDs and discovery work require.

stakeholder management across a hierarchy. consultants present to C-suite regularly and manage up constantly. PM work requires this constantly, especially at companies with complex org charts.

client-facing communication under pressure. used to walking into a room where people are skeptical of you. that's most product reviews.

the real gaps

technical intuition. not 'can you code' but 'do you understand what is hard vs easy for engineers, what a migration costs, why this API change is a month of work.' consulting-to-PM switchers often underestimate how much this matters. you can close it by spending real time with engineers in early roles: pair on a ticket, read the code, ask why the tech debt exists.

design instinct. consultants are often not taught to think about user experience, only business outcomes. you need to develop opinions about flows, learn to read a usability problem in a prototype. this takes time and practice.

shipping instinct. consulting deliverables are decks. PM deliverables are working software. the feedback loop is completely different. consultants often struggle with 'done' meaning 'it runs in prod,' not 'it looks good in the deck.'

the interview path

associate PM and rotational APM programs are the most realistic first step. they're designed for career switchers. after 18 months in those, you can move laterally to a PM role at the level your experience actually warrants.

if you're going directly for a senior PM role from consulting with no product experience, expect to struggle. the interview will include execution questions about past prioritization decisions, and 'i managed a consulting workstream' is not the same as 'i owned a product roadmap.'

4 replies

jordan_pm

the 'done means it runs in prod' point is the thing that most consulting-to-PM people take the longest to internalize. i've worked with several and the ones who struggled most were the ones who kept optimizing for the clarity of the explanation rather than whether the thing worked. shipping mediocre software on time beats shipping a perfect spec late every time.

pm_priya

also: in consulting your reputation resets with each client. in product you have to work with the same engineering team indefinitely. the political cost of being wrong or making promises engineering can't keep follows you. that's a big context shift.

ux_uma

the design instinct gap is real. i've worked with a few PM switchers from consulting who were very impressive on the strategy side and genuinely couldn't look at a user flow and identify friction. that's learnable but it takes exposure. spending time with your design team before you have to make decisions is not a nice-to-have.

alex_design

agreed. the fastest way i closed this was asking to sit in on user research sessions before i had any product responsibilities. just watching real users interact with a product is a fast education.