Sometimes it makes sense to create only what is essential as a first step.
Creating an MVP can enable you to launch quicker, or simply just create quicker in order to get to an investment milestone.
There are options in terms of how this phase is conducted from a wireframe and prototyping perspective, but ultimately we need to create what we need to create.
We need to build the functionality you require for your MVP.
And make good decisions on hosting and support.
Whilst many in MVP mode are striving for lower budget and maximum speed, it is important to note that using research and gaining insights means we can find out what features your customers value most – so we can prioritise and reduce needless development costs.
We don’t see an MVP as a way to make mistakes and learn from them, as for most companies its success is crucial to the existence of a phase two.
You can talk about about a good idea but there is no substitute for showing it.
Building an MVP helps people to actually see how the product works and provides confidence to your internal stakeholders or new, would-be investors.
Once you start de-scoping the non-essential, there is a tendency to start slicing off everything apart from the core, required functionality.
But often, when you are creating an MVP you are launching and building a brand as well. It is important the brand and the reason you exist is also considered.
For example, if your brand is all about providing choice, you need to provide that even if this is classified as non-essential from a functionality perspective.
Stop assuming. Start understanding your customer needs.