15 Signs Your MVP Isn't Ready for Production

An MVP is supposed to be minimal. It is not supposed to be fragile. The difference shows up as a set of recurring signals that appear in almost every product we review.

Engineering signals

1. 1Every new feature breaks something unrelated.
2. 2No one can explain the whole codebase with confidence.
3. 3There are few or no automated tests.
4. 4Database changes feel dangerous and are done by hand.
5. 5Deployments are manual and only one person can do them.
6. 6There is no separate staging environment.
7. 7Secrets live in the codebase or in a chat thread.
8. 8Errors are discovered by users, not by monitoring.

Product and delivery signals

1. 1Estimates keep growing for work that used to be quick.
2. 2Bug fixes create new bugs at a steady rate.
3. 3Performance degrades noticeably as users are added.
4. 4Security has never been reviewed by anyone.
5. 5Logs do not explain why a failure happened.
6. 6Architecture decisions are inconsistent across features.
7. 7Scaling is discussed as a rewrite rather than an increment.

What to do about it

Do not stop feature work entirely. Sequence the fixes: automated tests around the riskiest paths, then a repeatable deployment pipeline, then data safety, then a security review. Each step reduces the chance that the next feature causes an incident.