If you ever work with a client on a project, scope creep is one of the things that is bound to happen sooner or later, the client asked if we can add another feature onto the website, another bullet in the list of deliverables, another idea that the client came up with that might make you spend the whole weekend researching on how to fit it in the current project.

I’ve been in that situation before, and as a fellow people pleaser who doesn’t want to say no, I always say yes to those requests only to resent myself while working on it, and just between you and me, I also secretly love the challenge as well as the enjoyment of solving problems but deep down I know that this isn’t sustainable and something has to change, I cannot just say “yes” to scope-creep because the following things will start to happens:

• What is this “thing”? We will lose sight of the project, and the initial purpose of why the project was created in the first place.
• “So… when will we launch?”: the project will take longer to design, develop, and test. To postpone the launch date could affect both your and your client’s finances and plans.
• When will it end? everything will keep snowballing if you accept every request and demand from the client, the moment when you start to say “no” will cause a “crack” in the relationship with your client.

How do you get ahead of scope creep? Is it the client’s fault that you have to spend extra hours in front of your computer working?
I would say that it’s hardly the client’s fault since it’s very common to have an idea, a lightbulb moment during the project that they think can have a positive impact on the business with you saying yes they either think that: this must be easy enough to change or you’re a pushover who will agree to everything they say. Either of those is hardly true (well, maybe the latter is sometimes true). The way I deal with scope creep now is to have a system, the difference between the pros and amateur is the pro has a system:

• List out the detailed timeline and deliverables (scope of work): having things written down in an agreement and contract is a great first step for both you and a client to get on the same page, understanding what’s the project about, when and how it will be delivered
• Set expectations and boundaries before work: let the client know that you are a professional who is focused and works with a system, not a tool that the client can use and push around, you have spent years and resources to get where you are now, the client should respect your craft as you should too.
• Invite the client into the process, and work them through on how and why you make a decision -> this will eliminate impulsive, unthoughtful decisions from the clients.
• Always reflect and compare the project progress in each milestone with the agreed-upon scope of work and the project’s goals.
• If there’s a much-needed scope change, take a deep breath, stand firm, and let them know there will be budget and/or timeline implications or this will be a different project after this current project is finished and achieved its goals.