Scope creep gets blamed on clients a lot. And sure, sometimes it’s deserved. But in my experience, the more interesting cases happen when nobody really knew what was being built in the first place.
This is one of those.
The Setup
I joined a project already in motion. A client had signed on for a full website build and, to their credit, they trusted us. They didn’t push back on the scope because they didn’t fully understand what was in it. That’s not uncommon. Clients sign proposals all the time without a clear picture of what the deliverable actually looks like. That’s partly on us as the people writing those proposals.
What the client actually needed was a tool. Their customers (think arena operators, airport terminals, anyone buying massive multi-panel LED displays) needed a way to figure out what panels to order before picking up the phone. Their competition had these slick configurator tools and calculators, and this client wanted in on that. Totally reasonable ask.
The problem was the original plan had turned that ask into an entire website, with all the overhead that comes with it. By the time I got involved, the team was stressed, production was midway through, and the client was starting to realize what they were getting wasn’t quite what they had in mind.
What I Did
First thing I did was sit with the internal team and actually listen. Not to fix anything yet, just to understand how we got here and where things stood. Stressed teams don’t need someone walking in with a clipboard and a plan. They need to feel heard first.
Then I met with the client.
We got specific. Instead of asking “what else do you want,” which is how scope creep spirals, I asked “what does success actually look like for your customers?” That single reframe changed the conversation. They didn’t need a website. They needed a lead magnet. Something a potential customer could use in five minutes to get an estimate and feel good about reaching out.
So we did a mini re-discovery. No big reset, no blown timeline. We looked at what was already built, identified what was salvageable, and drew a tighter box around the actual goal.
The Solution
The website became a single page. Optimized for conversion rather than content.
The centerpiece was a form (what we used to call a wizard, thanks Windows ’95). Step by step, approachable, fun to use. It walked customers through their display needs, gave them something useful at the end, and handed them off as a warm lead. We also used it to surface the client’s other offerings along the way, so it was doing double duty as a marketing tool.
To move quickly and stay within the remaining budget and timeline, I brought in additional contractors. Scoped tightly, handed off clearly, kept things moving.
The result shipped on time, hit a marketing campaign deadline the client had been quietly stressing about, and converted.
What I Actually Learned
The scope didn’t creep because the client was difficult. It crept because the original plan was solving the wrong problem. A vague proposal plus a trusting client plus a team that didn’t slow down to ask “wait, what are we actually building?” is a recipe for exactly this situation.
The fix wasn’t adding more. It was getting honest about what was left and making it count.
I use that reframe a lot now: instead of asking what else needs to be added, ask what the customer actually needs to do. Usually the answer is simpler than the plan you’ve already built.