There are two kinds of people in this world: those who do, and those who just say.
Our project manager? He was a weird third type. He didn’t say much, didn’t do anything, and when he did say something... it usually made no sense.
The first red flag? He raised his hand one week after joining. Literally. He said he needed help understanding the project. Ok, fine. Everyone needs onboarding. But then... that was it. No involvement. No deep questions. No decisions. Just floating around. A ghost in every meeting. A name in every thread. Nothing more.
Then he disappeared for real.
No dailies. No standups. No Slack replies.
Nada.
Weeks became months.
The devs took over. The client started trusting us more than him. And to be honest... we were doing fine without him.
But guess what? Out of nowhere, he comes back.
Suddenly active. Suddenly asking for updates.
Suddenly demanding things.
Turns out he smelled something in the air.
Something that sounded like: “Hey, we’re reviewing headcounts.”
And now he wanted to appear valuable.
But here’s the thing: if you only show up when you feel your job is at risk, you’ve already lost it.
The company finally made the right call.
It took them a year and a half, but the guy’s out.
Here’s a simple truth I’ve learned in projects:
👉 A PM who doesn't show up when things are calm is the same PM who will fail you when things go wrong.
Let this be a warning.
If you’re running a Salesforce B2C Commerce project and your PM is nowhere to be found…
...you might already be leading the project without knowing it.
And maybe that’s not a bad thing.
