
Why Every Project Needs One Decision Maker
Learn how unclear client communication can trigger scope creep, unpaid work, and schedule overruns in project management. The episode explains how to set a single decision maker, enforce approval guardrails, and keep everyone aligned with simple progress updates and documented communication plans.
Show Notes
Why You Need A Single Decision Maker In Client Communication - My Project Management Lessons: https://myprojectlessons.com/single-decision-maker/
Chapter 1
Single Decision Maker Stopping Client Communication Chaos
Michael
Picture this. You're out on site, trying to run a smooth operation, and suddenly it feels like a total drop ship malfunction. Conflicting orders flying over the squad radios, total chaos on the line, and nobody knows who's actually running the show. I, I, I see it all the time in project management. The client will give instructions, clarifications, or information to individual project team members without the project manager being aware of this. And mate, that is where the real nightmare begins.
Michael
What happens next? Well, your team, bless 'em, they jump straight on it. They start tweaking designs or changing scope because they reckon they're just being helpful. But here's the kicker, most clients require formal written approval before they'll pay a single extra dollar for fee changes or extra scope. So if your squad does work without that formal green light, guess what? You've just done free labor, your schedule's blown out, and you're not getting paid for it. Game over, man, game over!
Michael
So, what's the fix? How do we stop the scope creep madness? It's simple, really. You need a single decision maker as the main point of contact on both sides of the fence. One authorised legend from your team, usually the project manager, and one designated key contact from the client side. That's it. You get that locked down, named by title or person right in the contract, or at least in the written communication plan.
Michael
Now, does that mean your team can't ever speak to the client? No, of course not! Fair dinkum, you don't want to be a bottleneck for routine stuff. If your design lead needs standard drawings, or site guys need permission for site access, that's totally fine. But, you've got to educate your team on the guardrails. Anything, and I mean anything, that touches scope, schedule, or cost has to route straight through the authorised project manager.
Michael
If a rogue request comes in over the phone or email from someone else at the client organisation, your team needs to forward a copy of that direction straight to the official client PM for authorization before anyone touches a tool. And to keep everyone on the same page, run a strict no surprises policy. Send out regular progress updates. Even a super simple weekly email with dot points showing schedule progress, scope completed, costs so far, and pending variations works absolute wonders.
Michael
Using solid project management communication systems helps heaps too. Tools like Monday, Teamwork, Nifty, or Blue let you keep task chat and approvals neatly recorded with time stamps. So here's your practical action step for today, right after this podcast. Go and audit your active project contracts and communication plans right now. Make sure your single decision makers are explicitly documented in writing for both sides.
Michael
If you want more tips on specifying deliverable due dates, tracking career achievements, or managing change requests, head on over to MyProjectLessons.com. Thanks for listening, legends. Catch ya next time!