7) Minimum Viable Product for your “Super Fan’s” Company to use

This is the logical step after you’ve gained the commitment (and the enthusiasm) from your superfan to use your product. Focus on what needs to be added so that more than one user from the company can perform the task. It’s likely to be login (and the associated authentication, authorisation issues), filtering data by user, basically multi-user functionality. There is still very unlikely to be the “need” for reporting and advanced dashboards. You can create the users manually in the database if needs be…no need to worry about “admin” or “settings” pages yet!
 

This definition is the minimum that I default to when someone says “MVP” without any further clarification. It has a real focus on the bare bones of what is needed to solve the customer’s pain point.

From this point on, the driver for expanding the functionality should be taking feedback from the users as a primary influence. You still need to stick to the vision of the product, but the minor alterations in direction are best influenced by those people that actually perform the job. It is at this point that the Product Manager / Owner role becomes so key… but that’s for another post!