MVP insights, articles and news

In software development, one of the most common traps organisations fall into is trying to build everything at once. The result is often a long, expensive project that takes months (or years) to deliver, and when it finally arrives, it’s bloated with features nobody actually uses.

Utilising an MDV (Minimum Deliverable Value) approach has a host of benefits that can ensure that development and assumption validation is as effective and beneficial as it can be.

A Minimum Deliverable Value (MDV) is a lightweight, functional outcome that tests a core assumption or delivers operational insight without the bloat of a full MVP. This is ideal for validating a specific assumption, exploring a technical opportunity, or demonstrating early value before investing in a larger, traditional MVP or product build.

We’re often engaged by our clients to develop Minimum Viable Products (MVPs) of a given product or system. More often than not we see a common and recurring problem with the original brief – the “MVP” is packed full of features of varying shapes and sizes.

At The Curve, we build products for our clients. These could be business systems that are used by internal stakeholders that we develop using a product mindset, or B2C products our clients then use with their own customers.