Have you ever started a project that didn’t have a precise, unambiguous definition? If so, you’ve probably experienced scope creep.
Things like…
Agreeing to do the dishes, not realizing there were two greasy roasting pans hiding in the oven.
Allowing a small, unexpected revision to your design after agreeing on a project cost. And then watching its ramifications balloon during the build phase. (Thinking of architecture – physical or software.)
Saying you’ll “build a shed this summer.” (Does that include the foundation? What about windows? Did you build in time for permits? Do you mean during July and August or by September 20th?)
If your business sells products rather than services, it’s less likely to happen. But not impossible. Consider the unplanned expense of unreasonable post-purchase support demands (or refund/exchange requests).
But if what you deliver is less tangible/physical, it can be harder to set (and stick to) clear boundaries.
And it’s not just an annoyance. Scope creep can drain the life (i.e., the profitability and/or the enjoyment) out of your business.
The best way to avoid it is to be crystal clear up-front. State – in a bi-laterally referenceable document – exactly what you’re going to do. AND exactly what you’re going to do if (when) something unexpected comes up.
Get comfortable bringing up and revisiting the original agreement. Do it any and every time something someone wants to add something new.
You float like a feather,
James
P.S. On my mind, because I unintentionally scope crept our good and friendly plumber today.
What started with a stripped thread at 9 am (and seemed like a half-hour fix)…
|
|
…had turned into much, much more, by 7 pm.
|
|
Recent Comments