Why Minimal Viable Experience ?
Many of us are familiar with Minimal Viable Product (MVP) but not necessarily of Minimal Viable Experience (MVE) and its significance within Product Management or Software Development.
Why MVP?
MVP refers to the version of the product, where a set of identified core functions with importance is delivered to facilitate an early feedback loop.
The success criteria for MVP is measured with the value delivered by the core functions to the user.
Why MVE?
MVE refers to how users feel when they interact with the product and how they feel about the overall User Experience.
The success criteria for MVE is not about what the user achieves with the product, instead it is the overall User Experience (UX) of the user whilst using the product.
Measuring Minimal Viable Experience (MVE)
MVE is a phase that remains live throughout the lifecycle of a product, until its maintenance and discontinuation. Whereas MVP is a phase preceding towards a milestone or a release and mostly considered to be internal-facing.
Therefore it is crucial to ensure that more significance is given to defining MVE and continuously refining it to with each milestone or release to reflect and adjust to customer feedback, instead of assumptions, presumptions, hypothesis or biasness.
While there are many frameworks to measure MVE, we used the HEART Framework by Google to measure, compare, and track the experience of our users to ensure product and design decisions are made and evaluated in relation to feedback instead of opinions and assumptions.
Components:
- Design & Layout
- Product Packaging
- Onboarding
- Help Resources
- Customer Support
The objective of the deliverables must always remain to only satisfy and meet customer requirements.
References: