Say What We Won't Build First

Blog ZH

TanBlue Studio

Quiet notes from a small studio.

Blog Post

Say What We Won't Build First

How project scope gets pinned down

  • Project management
  • Requirements
  • Working together
Show contents
  1. 1. The usual story
  2. 2. The “not doing” list
  3. 3. Not “never”
  4. 4. In short

After a few projects, we noticed that what goes wrong is rarely the technology. It's the scope.

The usual story

The project starts as "online booking". Halfway through, the client wants loyalty points. Just before launch, a mini-program shop. Each request makes sense on its own. Together, the project never ends.

The "not doing" list

Before we quote, we now write two lists with the client:

  • In scope: down to specific pages and features;
  • Out of scope: just as specific — "no payments", "no data migration", "no native Android app".

The second list is often the more useful one. The client knows exactly what they're paying for, and we can focus on what actually has to ship.

Not "never"

Anything left out gets written down and revisited once version one has been in real use for a while. Often, after a month, the client decides they don't need it after all.

In short

Clear scope gets a project launched on time. Once it's launched, there's a next step.