u/Murky_Cow_2555

when i was maybe 3 years into pm i thought the job was basically risk management on a spreadsheet. good plan, clear raci, tight change control, and youd be fine. i was honestly a little smug about how organized i was. then i ran a project that fell apart in slow motion and it rewired how i think about this whole career.

quick version: cross department rollout, exec sponsor who was super hyped at kickoff. i did everything right. plan was clean, risk log was beautiful, status was green for months. what i didnt clock was that two of the team leads quietly hated each other and one of them had basically decided the project was a threat to his teams headcount. none of that was in my risk log because none of it shows up in a status meeting. people just nod and then go do nothing.

we hit integration and it all surfaced at once. one team had been too busy to do their part for weeks. sponsor suddenly went cold cause the politics shifted above me and the project wasnt his favorite anymore. i was standing there with a perfect plan and a dead project, getting asked by leadership why i didnt see it coming. genuinely thought i was done. updated my resume that weekend lol.

what it taught me and what i'd tell anyone earlier in their career: green status is the most dangerous color. its usually not "everythings fine", its "i havent found the problem yet". i now actively go looking for the bad news instead of waiting for it to show up on its own.

the org chart is fiction. the real map is who trusts who, who's threatened by what, who owes who a favor. i spend way more time on that now than on the gantt, and it's the thing that actually saves projects.

and the career one. you will, at some point, be blamed for something that wasnt fully in your control. how you carry yourself in that moment matters more than the outcome. i didnt panic, i didnt throw anyone under the bus, i laid out honestly what happened and what id do differently. the project still failed. but a director who watched me handle it pulled me onto a bigger thing a year later specifically because of how i acted when it went bad.

funny thing is that disaster did more for my career than any of the clean projects ever did. you just cant see it while youre living it.

anyway, whats the project that went sideways on you and did it end up helping or hurting where you are now?

I think one of the strangest parts of corporate life is how quickly being responsive becomes more important than actually doing good work. At some point your day slowly stops being about solving problems and starts becoming this constant performance of availability. Replying fast. Reacting fast. Joining calls fast. Sending updates fast. Even when none of those things are the actual work. And the weirdest part is people start rewarding visibility over outcomes without even realizing it.

The person constantly active in Slack looks productive. The person answering emails at 9PM looks committed. The person always present in meetings looks engaged. Meanwhile some of the most useful people I’ve worked with were quiet for half the day because they were actually focused on solving something.

Feels like a lot of companies accidentally built cultures where attention is fragmented all day long and then everyone wonders why nobody can think deeply anymore. I noticed this especially after moving into more project-heavy work. Entire days disappear into updates, alignment meetings, status discussions and follow-ups about follow-ups. By the end of the day you were busy for 10 hours but somehow the important thing still barely moved forward.

And honestly I think a lot of burnout now comes less from hard work itself and more from the feeling of never mentally leaving work for even one uninterrupted hour.