i’ve been at deloitte for four years and i’m at that weird inflection point where i’m good enough at consulting that i’m getting staffed on interesting work, but i’m also starting to wonder if i’m just getting better at something i don’t actually want to do for another five years. everyone tells me to ‘know when to leave,’ but nobody actually defines what that threshold is.
here’s what’s making me question the move now: i’m getting pulled into strategy work with clients that feels kind of like PM—thinking about long-term direction, understanding constraints, building business cases. but i also know that consulting strategy is different from actually owning a product. the consulting version is about analysis and recommendation. the PM version is about living with the consequences of your decisions and having to ship incrementally.
the pay jump to tech PM is real but takes a hit initially. the work-life balance is supposedly better, but i’ve heard horror stories about PM on-call culture at certain companies. and the weirdest part: i’ve built a substantial network at mckinsey, and moving to tech feels like torching that advantage.
what i’m trying to figure out is whether the itch i’m feeling right now is ‘this role has run its course’ or ‘i’m just bored right now and need a project.’ the people who made this transition have told me the hardest part isn’t learning PM—it’s actually committing to losing consultant status and starting over as a junior.
how do you actually know you’re ready? what were the signals for you that made you go ‘okay, this is the right time’ instead of ‘i’m just running away’?
real answer? you know you’re ready when staying sounds worse than losing your network. the network anxiety is normal—i had it too. here’s the thing: you think mckinsey status matters outside mckinsey. it doesn’t. what matters is shipping. if you’re already bored after four years, you’ll be bored at year six. the itch doesn’t go away; it just gets louder and more expensive.
don’t overthink this. the ‘junior again’ thing is brutal for about two months, then you realize you never actually lost anything—you just stopped performing a role. the pay hit is real though. calculate whether you can actually afford it before you decide. financial regret is worse than ego regret.
this is honestly what im trying to figure out rn too. the part about consultant status is what’s weird for me—like do ppl actually care about that outside the industry? or is that just a mental block we’re all creating?
the ‘am i bored or am i done’ question is hitting hard. how do u even test which one it is without just jumping?
so should you just try talking to ppl at tech companies first to see if the work actually interests u? like info interviews or smth?
Your self-awareness about the distinction between role fatigue and genuine misalignment is exactly the right starting point. Here’s a structured way to evaluate readiness: first, identify whether your interest in PM is driven by specific product challenges you want to solve or primarily by ‘getting out of consulting.’ These motivations matter—the first sustains you through difficult transitions; the second often leads to regret. Second, run a controlled experiment over the next quarter. Take on one internal project where you own a decision from problem definition through to outcomes measurement. This simulates PM accountability at lower risk. If you find that process intellectually fulfilling rather than anxiety-producing, that’s a signal worth listening to.
Regarding your network concern: the consulting relationships you’ve built have real value, but they’re portable in ways you might not realize. The ones worth keeping are relationships with people, not with institutions. What matters post-transition is whether you maintain authentic connections. Most of my best consulting colleagues stayed in my professional circle even after I moved to tech. The ones who didn’t were relationships I didn’t actually value. By that measure, you’re probably overestimating what you’d lose. Focus on moving toward something compelling, not away from something comfortable.
One final thought on timing: readiness isn’t just psychological—it’s structural. When are you next facing a major staffing cycle or assignment point at your current firm? The worst time to leave is mid-engagement when you owe commitments to clients. The best time is when you have some control over the transition. If you’re genuinely ready, you’ll also want to have done enough interview preparation that you’re competing for strong PM roles, not just moving laterally into any tech job. Readiness means you’re moving toward something better, not just away from something.
i was in exactly this position three years ago—four years at accenture, getting bored, wondering if i was overthinking it or actually done. the signal that pushed me over the edge was when i started declining interesting projects because i knew they’d keep me in consulting longer. that’s when i realized it wasn’t about the work being bad; it was that my energy just wasn’t there anymore. i took a week off, thought about what actually excited me, and realized it was the product thinking, not the problem-solving—the two actually aren’t the same thing. that clarity helped.
the network thing is real but not the barrier you think. i kept about 70% of my actual friendships from consulting, and the relationships that mattered stayed strong. the ones that were transactional? didn’t miss them. what surprised me was how many consulting partners actually wanted to stay close after i moved to tech—they saw the network as bidirectional. don’t let fear of losing status keep you somewhere you’re not excited to be.
my honest take: do one trial run. pick a tech company, interview seriously, get an offer. then sit with it for a week. if the excitement holds and you stop making excuses about why you shouldn’t take it, you’re ready. if you start rationalizing why you should stay, you’re not there yet. that clarity came for me only after i actually had to choose.
A practical framework: spend the next two weeks documenting what excites you about PM work versus what you’re running from at consulting. If excitement reasons outnumber escape reasons 2:1, readiness is likely sufficient. Also worth noting: your four years of consulting experience actually places you at optimal career stage for senior PM track at mid-market tech companies, where transition friction is lowest. Larger companies screen harder for tech PM experience; smaller ones are more forgiving. Knowing your target company profile helps confirm timing.
On the network concern: research on consultant-to-tech transitions shows professional network value is largely portable through maintaining 8-12 key relationships from your previous firm. Most successful transitions reported minimal network loss. The real value of your consulting network is the skill of relationship-building you’ve developed, which transfers perfectly to tech. By that measure, you’re not losing an asset; you’re bringing a core competency to a new context.