Project scoping: a practical guide

The gap between knowing this and actually doing it is where most teams lose ground. This guide covers what project scoping actually involves, where it usually goes wrong, and how to tell whether yours is in reasonable shape.

Clear scope protects the client at least as much as it protects the agency. Nothing below assumes a large team or a large budget — most of it is a decision somebody has to make and then write down.

Why it matters

Vague scope is the root of most budget disputes. Getting it slightly wrong is survivable. Ignoring it entirely is not. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

For most businesses the question is not whether this matters but how much of it is worth doing right now. That depends on what you are trying to achieve in the next few months, not on best practice in the abstract. In practice this is a scheduling problem more than a technical one.

Where to start

Write down what is explicitly out of scope. The teams that handle this well are rarely the ones with the biggest budgets. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

Strategy work is mostly deciding what not to do, and writing it down so it stays decided. The version that works in practice is usually less elaborate than the version described in the guides.

Assumptions should be recorded, not held in someone's head. Getting it slightly wrong is survivable. Ignoring it entirely is not. Assume whoever inherits this will have half your context and none of your patience.

A working checklist

If you want a quick read on where you stand, work through this. Anything you cannot answer confidently is where to start.

• Vague scope is the root of most budget disputes
• Write down what is explicitly out of scope
• Assumptions should be recorded, not held in someone's head
• Someone is named as the owner, not just assumed to be
• There is a date in the calendar to review it again
• The decision and the reasoning behind it are written down somewhere findable
• You could explain the current setup to a new hire in five minutes

Common failure modes

The most common failure is not doing this badly. It is doing it once, during a launch, and never revisiting it. Circumstances move, the setup does not, and the gap widens quietly until something breaks or somebody notices the numbers.

• It was configured during a launch and has not been touched since
• Different people in the business believe different things are true about it
• There is no way to tell whether the last change helped or hurt
• The only person who understands it has left, or is about to

The projects that go badly are rarely the ones with the hardest technical problems. None of that requires a large budget, only a decision and someone to own it.

How we approach it

On our projects this gets handled during the build rather than added afterwards, because retrofitting it costs several times more than including it. We write down what was decided and why, so the next person to touch it is not guessing.

If you are working with someone else, the questions worth asking are simple: who owns this, how will we know it is working, and what happens when it needs to change?

Making it stick

Pick the single item from the checklist above that would cause the most trouble if it turned out to be wrong. Fix that one, confirm it worked, then move on. Most of the value here comes from doing the first two things, not all of them.