I’m about four months into my first PM role after consulting, and I’ve already hit a few curveballs that I wasn’t expecting. The interview prep and the first-day reality are… different.
First, I thought the pace would be faster. And in some ways it is. But in consulting, the pace was about moving ideas quickly through a decision-making process and iterating on recommendations. Here, things move, but then they sit. A feature ships, and then you wait for real user data instead of a stakeholder debrief. That was a shock.
Second, I’m realizing that a lot of what I thought was “product thinking” during my consulting exit prep was actually just structured client problem-solving. That’s useful, but it’s not the same as living with the consequences of your decisions over time. In consulting, you hand off the recommendation and move to the next client. Here, you’re accountable for whether the thing you built actually solves the problem you thought it would solve.
Third—and this was dumb of me not to anticipate—the politics are totally different. Consulting politics are about managing up and across different client sides. PM politics are messier because you’re living with the same people, same product, and same quarterly goals. It’s not about persuading; it’s about building credibility over time.
I’m also noticing that the team looks at consultants who just arrived with a bit of suspicion. Not hostility, but there’s definitely this “prove you’re not here to optimize us” energy until you show you genuinely care about the product.
What blindsided you most when you made the jump? What felt different than you expected?
welcome to reality. consulting teaches u to solve problems for someone else; PM teaches u that solving the right problem is actually harder. that ‘prove you’re not here to optimize us’ vibe? that sticks around. ur team will test whether u actually care about their workflow or if ur just here to make things faster. and yes, politics never really goes away, it just gets slower and messier. six months in it gets better, but don’t expect the consulting speed back.
oh man this is so real. so the team doesn’t rly trust consultants at first? how do u build that trust tho?
Your observation about accountability is precisely the distinction that separates effective PMs from strong analysts. In consulting, you optimize for decision quality and client perception. In product, you optimize for user outcomes and team momentum. The credibility gap you’re sensing exists because the team has lived with the consequences of previous decisions, whereas you’re inheriting a product with a history. I’d recommend investing heavily in understanding not just what was built, but why previous decisions were made—and what constraints were real versus assumed. This demonstrates respect for the product’s evolution, not just efficiency-mindedness. The team will trust you once they see you’re willing to defend their choices when they made sense, even if you’d approach it differently today.
Four months in and already learning—that’s amazing! The fact that you’re noticing these patterns means you’ll adjust quickly. Keep leaning into genuine curiosity about the product’s history, and that trust will build naturally!
The difference between consulting iteration cycles and product feedback loops is substantial. Consulting operates on compressed decision timelines with defined endpoints; product management requires sustained hypothesis validation. Most consultants transitioning to PM underestimate how much of their credibility depends on predictive accuracy over multiple quarters rather than analytical rigor in a single engagement. Your team’s wariness isn’t about distrust in your problem-solving—it’s about whether you’ll stick around long enough to own failed bets or only popular decisions. Demonstrating accountability for outcomes over time is the actual credibility currency here.