Best Practices for Developing MVPs
2 comments
Run - if those ‘founders’ keep insisting to revise instead of putting the current MVP in front of users. These kind of founders are useless and you should steer clear of them.
There are no best practices that are universally applicable. Some don’t even like the concept of MVP. But putting a product in front of users - however clunky the product is - is the best practice.
Get early feedback, prioritize, iterate - rinse and repeat. That is all there is to it.
There are no best practices that are universally applicable. Some don’t even like the concept of MVP. But putting a product in front of users - however clunky the product is - is the best practice.
Get early feedback, prioritize, iterate - rinse and repeat. That is all there is to it.
Totally agree! How would you communicate this to the non-technicals in an influential way?
I've been recently (2-3 months ago) affiliated with a startup at the idea stage and I'm the only developer. I developed the MVP, which is pretty much done, but the other founders are asking constantly for revising certain parts. I think we should have released the MVP within a month and iterated but I cannot seem to convince them to put this version in front of some users.
So my question is, What are some best practices for developing MVPs? How should a technical person communicate with non-technical founders pre, during and post developing the MVP? How is this different from iterating on an MVP?
I feel like I need a different process for going from 0 to 1, then iterating on an already built product with some users. What is that process?