The Four Sides of Scope Creep

In my experience, I’ve seen four ways scope grows.

Breadth creep: More stuff is added than originally described. More files, more deliverables, more releases. The project got wider.

Depth creep: More detail or precision is needed than agreed. The project didn’t get wider, it got deeper. Each item now takes longer than planned.

Missed expectation: The client expected something that was never discussed. They assumed it was included. You assumed it wasn’t.

Missed estimate: The work was in scope, but it’s broader or deeper than you thought. This isn’t creep at all. It’s an estimation problem.

Depending on how the scope grows, I approach the client differently. If they add breadth, I point back to the agreed scope and decide together what fits. If they want more depth, I name the shift and show what it costs. If there’s a missed expectation, I get curious about what they were picturing. And if I underestimated, I negotiate a path forward.

Try this

Next time a project feels like it’s growing, ask: which kind is this?

• Is there more stuff than we agreed to? → Breadth
• Is each item more involved than expected? → Depth
• Does the client expect something never discussed? → Missed expectation
• Does the scope look right, but it’s just more than you expected? → Missed estimate

Then respond to suit the kind of scope creep it is.

Example

A consultant was frustrated that her client kept “adding things.” When she looked closer, she realized two requests were breadth (new deliverables), one was depth (more detail on an existing deliverable), and one was a missed expectation (the client assumed something was included). She handled each differently, and the conversations went better than when she treated them all as the same problem.

From PMEZ’s FINISH LINE approach