All Episodes
Scope Creep: How Small Changes Destroy Projects And How to Stop It

Scope Creep: How Small Changes Destroy Projects And How to Stop It

0:00|0:00

Michael explains how small requests become scope creep and shares practical ways to define scope, control changes, and protect budgets.

https://myprojectlessons.com/scope-creep/


Chapter 1

Imported Transcript

Michael

G'day everyone! Welcome back to My Project Management Lessons. I'm Michael, and if you're a project manager, there's one phrase that should make you sit up straighter every time you hear it: It'll just be a small change. It sounds harmless enough, doesn't it? But mate, that phrase's a red flag wrapped up in good intentions. Welcome to the world of scope creep. Think of a new project like a cute, fuzzy little pet you've brought home from an antique store. It's perfectly manageable, provided you follow a few simple rules. But what happens? Someone decides to bend the rules just once. It's a tiny exception, maybe accidentally spilling something extra into the mix, or feeding a harmless little requirement into the schedule way too late in the day. Before you know it, that one small addition's popped and multiplied into a whole horde of chaotic, destructive little nightmares tearing your project apart! That's exactly how scope creep works. It rarely arrives as an email titled Let's Triple the Workload. Instead, it's a bunch of small, seemingly reasonable requests. Could we just extend the kerb a few metres? Or, since we're already digging the trench, can we run this extra pipe? Each change on its own feels pretty negligible. But stack 'em up, and they'll quietly undermine your project like a wombat digging under your foundations. You've suddenly got a fundamentally different beast than the one you'd scoped, priced, and resourced. Your team's stretched too thin, your budget's blowing out, and you're left dealing with absolute mayhem!

Michael

So, how're we gonna stop these little terrors from taking over the town? Well, you've gotta draw the line early, clearly, and defend it. First up, spend real time upfront defining the project scope and write it down. Use a detailed scope statement and a Work Breakdown Structure so there's absolutely no doubt about what's in and what's out. Be precise! Don't just say, replace the culvert. Say, replace the 1200 millimetre culvert at chainage 540 with like-for-like material. If it isn't in writing, it doesn't exist. You've also gotta capture your assumptions and exclusions. If your project assumes you've got site access Monday to Friday, you've gotta write that down. Next, implement a rock-solid change control process. This's your safety net. Every proposed change's gotta be assessed for its impact on cost, schedule, and resources, and then logged into a variation register. When stakeholders throw creepy language at you, like, while you're there, it shouldn't take long, you've gotta use your authority to push back. You aren't being difficult; you're protecting the project. You're the one who's gotta expose these sneaky additions to a harsh light before they multiply and cause havoc. I always say, that's a good idea, but it's out of scope, would you like me to price that as a variation? Project managers aren't yes-men, mate. We're value protectors. You've gotta educate your clients and sponsors that even small changes mean more time and more money.

Michael

The big lesson I've learned here's that scope isn't a suggestion; it's the promise you make to your sponsor. Break that promise, and your credibility suffers. As project managers, we've gotta be the gatekeepers. It's always easier to say, let's follow the process, than it is to explain blown budgets when the project's in crisis. Sure, you'll always face requests for changes, and sometimes they're genuinely necessary, like unexpected site conditions or a newly discovered asset. But they've gotta be formal, priced, and deliberate, not quick side-of-the-road favours. You've gotta deliver what was agreed, not just what people suddenly decide they want after the fact. Be friendly, but be firm. So here's your practical action step for today. Review your current projects right now and assess whether your scope changes're being managed through a formal change control process. If they aren't, you need to implement a structured approach to evaluate and document all modifications, ensuring they align with your project's constraints. Lock those rules in, and don't let anyone break 'em, no matter how much they beg! If you're keen to dig deeper into keeping your projects on track, check out some of my related posts like Document Changes to the Scope Brief, Document Changes in Scope, and Know the Scope of Your Project. You'll find all the details at My Project Lessons dot com. Thanks for tuning in, folks. Keep your scope in sight, don't let the little surprises multiply, and I'll catch ya next time!