Presentation objective:
By definition, an MVP must have the "core" functionality of your product so you can get a "quick win". This implies having a clear picture of what you are solving to a very specific type of user.
Statistically as your customer base grows, their needs grows and you need more ways of solving those needs, which implies having to develop additional features to keep your value proposition relevant and innovative.
Think big but start small.
Understand what your solving
* Focus on:
Neil has created and evergreen pre-recorded webinar where he explained the benefits of using his methodology to achieve high performance on speed reading.
* What he did:
Pay close attention to what isn't being served by others and understand the value it will provide to your users.
Listen to your potential customer
* Focus on:
Daniel wants to do a portfolio management tool but instead of start building his product, he decides to collect user feedback through surveys.
* What he did:
Pay close through active listening of your audience in order to deliver what actually meet your customer's needs.
Rome was not build in a day
* Focus on:
Less is more
* Focus on:
Tom builds a nutrition advice progressive web application with what he considered the minimum features and later he decides to tell his friends and asks them to test his app.
* What he did:
It's much more useful to listen to beta testers to gather early customer feedback and avoid confusion and waste.
Establish clear communication between business and technical teams
* To optimize the workflow:
Laura (marketing manager) sits down with a client to present him the new workflow to prevent work in progress and client's budget waste.
* What she did:
By removing ambiguity, you can confidently predict a more realistic outcome and prevent waste.
¿What's worth doing?
¿For whom are we doing it?
¿What's the real value of it?
* Must know:
* Focus on what can be done by first having all written down and then spending time on what's really worth doing.