Signs it is time to revisit scoping an MVP

There is no clever trick in this one, just a handful of decisions worth making deliberately. A few signals that scoping an MVP is due some attention.

Strategy work is mostly deciding what not to do, and writing it down so it stays decided. Budget a little time for it every quarter and it never becomes a project of its own.

The signals

• Nobody can say when it was last reviewed
• The answer depends on who you ask
• Minimum means uncomfortable, viable means it works
• Cut features, not quality

How we handle it

The point is to learn something specific. This is the sort of thing that compounds, quietly, in both directions. If two people in the business would answer this differently, that gap is the actual problem.

In practice

The projects that go badly are rarely the ones with the hardest technical problems. 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

Most of the value here comes from doing the first two things, not all of them.