Case study of flawed conception due to abusing MVP Pattern (slide 2 of 2) Are there still short comings in the ‘Enlightened MVP’ Case example?
Thinking regarding how best to fulfill customer needs is often prematurely constrained to existing platform/team capabilities which leads to coercing adoption onto customer.  
Minimal Viable Product is often mis-used as a vehicle to rush to cheap creation, rather than using MVP as vehicle for exploration and discovery of what is actually needed.
Pursuing opportunities without qualification is not sustainable; therefore, we need understanding of: what the solution might cost; and, can the market pay for it.
The commitment to seeking a real solution seems tentative (i.e. research); the commitment to spend money on development is very real
Getting the opportunity to create appears to be the Team’s measure for success. Conception Discussion – Enlightened MVP Case Study. The “misused MVP” pattern implies that it is better to rush to narrowly focused creation rather than using the MVP to research what solution is actually needed.
Conception is a creative activity that should be shared with the customer-base in order to facilitate adoption!. ©2018 iiSM.ORG, All Rights Reserved. Cooperatively. Click slide to see in context of slide deck
Click to enter the site

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.

We require that our copyright notices are left in place.