I think this is why you need a very senior engineer overseeing your MVP.
Before MVPs were championed, companies would create a full-fledged project management suite with 50 database models and release it to crickets.
An MBA and a junior engineer define an MVP as “You can log in, and add todo lists and check them off.”
A senior engineer defines that same MVP as “You can log in, add todo lists, check them off, delete your account, and if the server crashes or we’re hacked, we have backups for 30 days.”
Or in other words with an MVP you still need to complete the 80% of the iceberg the MBA and junior engineer can’t see, but you don’t build the whole iceberg at once.
Before MVPs were championed, companies would create a full-fledged project management suite with 50 database models and release it to crickets.
An MBA and a junior engineer define an MVP as “You can log in, and add todo lists and check them off.”
A senior engineer defines that same MVP as “You can log in, add todo lists, check them off, delete your account, and if the server crashes or we’re hacked, we have backups for 30 days.”
Or in other words with an MVP you still need to complete the 80% of the iceberg the MBA and junior engineer can’t see, but you don’t build the whole iceberg at once.