The Innovation Blog
Insights for Chief Innovation Officers, Product Leaders, Innovators
MVPs and Startups - FAQs
MVPs and Startups - Why should a startup follow the MVP approach? How do you prioritize features? Answering these and other frequent questions people ask me about Minimum Viable Products - MVPs
Is this a Prototype or an MVP? Or maybe, a Proof of Concept?
When building software products or solutions, it is of critical importance to define early enough the target output — in terms of both functionality and ‘production readiness’. This is a practical guide to help you define a ‘prototype’, versus a ‘proof of concept’ and a ‘minimum viable product’ — and avoid costly misunderstandings.
Building an MVP: How to define the first instance of your product
This article provides actionable guidance on how to define a good Minimum Viable Product and how to avoid common mistakes and risks. If you are in the process of designing a product, establishing a product development function, or setting up a technology startup you will find essential information on how to approach the MVP development process.
The True Meaning of Minimum Viable Product
A popular definition for the MVP is this one “… the minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future development…”