You're reading ODAM v1 (2023), kept as published. See ODAM v2 →
ODAMFrameworkODAM Overview (PDF)

The Data-Driven Product Development Process Part III

From MVP to Iteration

An MVP (minimum viable product) is a product that has the minimum set of features and functionality needed to satisfy end users, and to provide a basis for learning and future development.

I like to use the MVP concept to describe what the end user should expect out of the gate. It is tempting to think that every KPI and visualization a user could want is on their dashboard out of the box but as we all know, there is some assembly required.

If we’ve already created an IT Service Blueprint for one of the organization’s services, we can begin to ask our personas questions about what KPIs are going to be most meaningful and important off the bat. This could be a measurement of capacity or speed. The bare bones of a dashboard are assembled to create the MVP for this persona and over the next months or quarters, it will be up to the ACE to solicit and collect feedback from the end user community.

Planning for Ask Me Anything sessions or Office Hours can be a good way to make the ACE a welcoming place.

As end users come to these office hours and talk to one another as well as the ACE, they can begin to share their lessons learned and experiences with one another. This helps build and foster community and trust which ultimately creates culture.

Let’s summarize some typical steps when launching an MVP:

The goal of launching an MVP is to quickly and efficiently test and validate a product concept, and to gather insights and feedback that can inform future development.