Re:Customers hate MVPs – Make it simple, loveable, and compl...
by loopz on Thursday April 23, 2020 @10:04AM
(#22956076)
You may not generate much income with initial MVP, or whatever you want to call it. The point is to learn while minimizing costs, risks and time to market. To expect greatness without work, is folly..
Your example with the restaurant is a perfect example: Have someone execute the MVP manually. Map routines that works great, optimize and document outcomes. This becomes spec for initial automations.
The alternative could be someone in a corner office applying systems thinking and predicting everything required in the system. This tend to overcomplicate system designs and make them less amenable to adapt over time.
If I'm building an MVP for a restaurant, maybe there's no code at all in that system. Maybe I'm manually taking everyone's orders and serving at most one or two dishes on a street corner. But I'm not just showing people pictures of food.
Your no-code solution still needs to be a solution, it can't just be a promise that there will be a solution at some point in the future. An MVP doesn't mean code, it means: Build the smallest possible product (whether that involves code or not) that actually solves someone's problems in the real world, and then put that product in their hands so you can see what they do with it.
A poll is not a product. No customer is going to pay you so that they can take a poll.