Minimal Supportable Product
A minimal viable product (MVP) is a version of a product, project, or concept with just enough features to satisfy early customers. It‘s a way of testing an assumption before committing to building a fully-featured product. The concept was popularized by the author and consultant Eric Ries.
But during my work in the innovation team at the Süddeutsche Zeitung I found the MVP-framework lacking in a couple of ways. As with most concepts out of the startup-to-consultancy-pipeline, it lacks a way of interfacing with the structure of the organization and its dark matter.
As a result, MVPs build by an innovation team are in danger of being created in a vacuum. They might fit the users‘ needs but aren‘t sustainable inside the organization because of lacking resources, knowledge, man-power, or a miss-fit with strategy or business goals. Such teams might end up with a perfectly fine new product, but without a way to sustain it further.
Products and projects need the political will, the people (developers, designers, etc.), the tools, and the technical infrastructure to build and maintain it. Building this infrastructure is often an implicit part of innovation, but for complex organizations, it has to be explicit to be successful.
Which in turn means, that innovation has to work on different levels inside these organizations. It might be more useful to influence the strategy, hiring, or processes to build a solid infrastructure that can then support the new product, then building the product itself.
My suggestion would be something like a minimal supportable product or (MSP). An MVP that is embedded from the start in the organization and can not only be iterated along with the users‘ needs but also the organization‘s capabilities, while also transforming both product and organization.