The real cost of ignoring scoping an MVP

It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Nobody bills you for neglecting scoping an MVP. The cost shows up somewhere else.

The projects that go badly are rarely the ones with the hardest technical problems. If it only works because one person remembers to do something, it does not work yet.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• Minimum means uncomfortable, viable means it works
• Rework, once the problem is finally visible

Cut features, not quality. In practice this is a scheduling problem more than a technical one. Budget a little time for it every quarter and it never becomes a project of its own.

A reasonable first step

The point is to learn something specific. This is the sort of thing that compounds, quietly, in both directions. Write the reasoning down alongside the decision, because the reasoning is what changes first.

How to tell if yours is fine

Clear scope protects the client at least as much as it protects the agency. Three things worth confirming about scoping an MVP before you move on:

• Someone can say what the current setup is without going to look
• Minimum means uncomfortable, viable means it works — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.