MVP: Minimum Viable Product
In product development there is a concept known as MVP, or minimum viable product. Simply put, this means getting the product out into the market with the least amount of features, in order to get customer feedback and to just get something out there!
This concept can be applied in multiple ways in the data management arena, but two obvious ones come to mind:
- Rolling out a new system. Too often, we decide that ALL functionality in ALL areas must be working "just right" before we go-live. And the result is that go-live takes months and months (sometimes years!) longer than it should.
- Rolling out new functionality within an existing AMS. Again, too often new functionality is not rolled out quickly because of the mistaken belief that the new functionality must work perfectly before it can be launched.
"Perfect" never happens, so that shouldn't be our benchmark in any case. But too often "it's not quite ready" is an excuse not to launch an otherwise useful new product or service.
MVP is a really good framework to help you avoid waiting and waiting and waiting until something is "just right."
Wes's Wednesday Wisdom Archives
Eyes wide open and affirmative decision-making
Eyes wide open and affirmative decision-making When I work with my clients on any type […]
Honoring an industry legend
Honoring an industry legend I’m taking a break from my usual data management tips to […]
Never burn a bridge
Never burn a bridge My children have reached the age where they have, or are, […]
You CAN compete with the big guys…
You CAN compete with the big guys… In my experience, associations often undersell their actual […]
Join (or start) your users group!
Join (or start) your users group! Today’s message is simple: If the AMS you’re using […]
They don’t care, until they care.
They don’t care, until they care. One of the more common questions I get from […]
Longfellow and data management
Longfellow and data management “We judge ourselves by what we feel capable of doing while […]
Do you really need all that historical data?
Do you really need all that historical data? A question I’ll often get from my […]
AI actually requires thinking
AI actually requires thinking “I don’t think AI introduces a new kind of thinking. It […]
It’s not the mistakes, but how you respond
It’s not the mistakes, but how you respond Recently a client was complaining about a bug that […]