Tim Reynolds

Software & Startups


Minimum Valuable Product

When building a new product the concept of Minimum Viable Product is a powerful one, ensuring you're not about to lead a team or company down the garden path on delivering software or services that provide little value to your current or potential future customers.

Generally, you won't be building on a hunch. You'll have customer or sales feedback that a pain point exists valuable enough to solve. Hopefully something painful enough they'd be willing to pay you for the solution.

However, too often I've been part of or seen teams water down the initial "MVP" to the point it no longer represents value to the intended customer. Inevitably this leads to the abandonment of the software or service due to poor feedback, poor market fit or lower than expected metric gains.

While finding a definitive answer to this problem has alluded me I'd like to challenge teams to spend more time with their customers before attempting an MVP. Listen, witness and understand where the value is for your users and then verify it resonates with a large enough addressable market to attempt solving.

So rather than asking what's the minimum viable product we can deliver to understand an ideas value, why not spend more time to understand your customers and answer what the minimum valuable product they'd accept before attempting to build your solution.