Minimum Viable Product - Letting Software Customers Help YOU Profit

Healthy Developer

24-06-2017 • 30 minuti

Whether producing a software product for a new market in a startup, or introducing a major change in an enterprise - planning a minimum viable product is a good idea.

When building a minimum viable product (MVP), you should select a feature that shows users your core value proposition, as well as two features that "delight".

The core value proposition is a part of the Business Model Canvas, a visual tool created by Alex Osterwalder that you can use to determine which aspect of the business is being effected by a change.

The "delighting" features provide something sexy for users that attracts potential customers due to it's sleekness, innovation, or ease of use.

When planning what goes into an MVP, don't budget for only the MVP. Budget for enough to build software for 6-12 months that will adapt to feedback.

Spend a small portion of the total budget to release the MVP, and use the majority of the remaining budget to adapt so you can deliver exactly what customers want - and in the way they want to buy it. These other "ways" than the product's features itself are the other aspects of the business model canvas.

If you only budget enough for the MVP, you won't have money left over to adapt. Adaptation is the difference between a product that "meets needs" and one that "exceeds expectations". It is this latter category of products that cause companies to be leaders in their market and cause substantial growth.

When selecting technologies for the MVP, don't box yourself into feeling you need to use technologies already familiar to the development resources you might have. Hiring a specialist in a technology that is faster to build prototypes and minimal products in can save substantial money.

Should the market lead you to find that what you've built is successful, you can always change the technology used down the road to meet scaling challenges, if the original technology can't handle the volume.

This is a GOOD problem to have, and means you've found a large user base - but until this happens, don't spend the time and money planning for it! You need as much budget as possible to simply ADAPT at first, and so your money is better spent with excess funds for adaptation than building out an infrastructure or technology stack that assumes a size of user base you don't yet have.

You can also watch this episode on YouTube.

Join my Patreon:
https://thrivingtechnologist.com/patreon

Learn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coaching

TechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techroles

The Thriving Technologist career guide:
https://thrivingtechnologist.com/guide

Visit me at thrivingtechnologist.com

Potrebbe piacerti

CRASH – La chiave per il digitale
CRASH – La chiave per il digitale
Andrea Daniele Signorelli & VOIS
Bitcoin Italia Podcast
Bitcoin Italia Podcast
Rikki & Guybrush
Pillole di Bit
Pillole di Bit
Francesco Tucci
Digitalia
Digitalia
Franco Solerio
Tutto Connesso
Tutto Connesso
Politecnico di Milano
Geniale
Geniale
Il Post - Matteo Bordone
Uno Nessuno e Centomil AI
Uno Nessuno e Centomil AI
Federico Vitiello, Giovanni Tommasini e Sofi.a.
The Future Of
The Future Of
Andrea Ferrante
EasyApple
EasyApple
EasyPodcast
Pensieri in codice
Pensieri in codice
Valerio Galano
Archeologia Informatica
Archeologia Informatica
Carlo Santagostino