MVPs don't work anymore

MVPs don't work anymore

When Piktochart was at its infancy, we used to say "MVP" all the time. It was the philosophy behind everything we did from thinking about the user interface to adding new features. Here's a brief process of what we did in selecting a new feature and building it:

  1. Write down all the ideas about what could work
  2. Pick the one that would have the greatest impact with the least amount of work
  3. Start working towards it and launch it
  4. Measure its effectiveness
  5. Scrap/Improve or Re-build

The time that was taken from #1 to #2 might have been 20 minutes, #3 about 1 day. We will then push the code to production and hope that everything works! Quotes like these were famous in 2011, "If it doesn't break, you're not moving fast enough."

Today at Piktochart, a similar process would have taken more than 1 day and 22 minutes. A friend, Thomas Yip from Radica Software quoted that the current concept of "Minimum viable product" seems to have a large emphasis on Minimum instead of viable. In 2015, you won't see any beta product on ProductHunt that breaks. The analogy is that it will be like a book that has not been read beyond prologue and tossed in a corner to gather dust. 

In the wake of throwing away "Minimum viable product", we have picked up a new methodology which unfortunately, without my technical background makes it sound a little dodgy.

  1. Collect data from users
  2. Sketch on paper (Wireframe) & Research apps out there
  3. Discuss
  4. Sleep on it
  5. Decide
  6. Build it
  7. Measure

With the new process, the shortest it has taken us to get through #1 to 5 is 2 weeks. Step 4 is actually really important. After discussions, it's usual to either have everyone completely persuaded by one charismatic leader of the discussion or to have no one agreeing on the concept. Sleeping on it is therefore a crucial and inexcusable component of the 7 steps. Comparing this new methodology with "Build, Measure, Learn" doesn't even make sense. We still care about measuring te results but the point is that by going through this 7 step process, whatever we have built should be good enough that we're certain it's going to yield an incremental positive result.

We can no longer make mistakes with products. Users are not willing to tolerate a poorly-executed change. Many products in the past 5 years have won hearts of users over reliability, simplicity and focus on delivering 1 positive user experience really well. I feel extremely blessed to have been forgiven of the mistakes that we made at Piktochart when we first started out.

I have to remind myself that it is okay to take a longer time to ponder upon, deliberate and be sure that we're out there to build the best and most excellent version of our product.

Do you agree? Or are you still in for MVPs? :) 

 

Prince Hasn

Engineer +10y crypto space, +20y product R&D

4y

It is amazing to see this vision was 3 years ago. Indeed, today it is clear design and development are merging into one process especially in digital products.

Like
Reply
Rajakumar Somasundaram

Exceptional SAP FI/CO Solution Architect With Multi-module Experience In SD, MM, PP and PS

7y

Hi Ai Ching, Learned about your site from the Star newspaper today and i must say your team and you have built a great wonder product! This is an amazing idea presented in the best possible way. I love you guys and wish you all a great success in the global arena!

Like
Reply
Philip Yong

Sustainable Commerce Advocate

7y

For me, I believe the 'human' factor plays a big role here. I would like to believe we all think differently, work differently and have different risk appetite. So it all really depends on an individual or a group to decide which method they would prefer as both has its pro and cons. Working on any products or businesses, I always like to go back to the fundamental aspect, the people building these products/businesses. Because it always boils down to the people working on it. Apologies if you think this is irrelevant to your topic!

Like
Reply
Keat Wei Yoong

Product Manager at Weavary

8y

I came across to misinterpret M(minimum)VP in the beginning on planning and deciding what to build. Minimum - we decided the minimum things we can build. Yet, the more we look into our proposed solution, it is buildable but not sellable. Then we know that we were wrong. In my understand/point of view, MVP is something that you can build and validate(fast) your idea in the early stage - to avoid building something people do not want (in the minimum cost), it can be ppt, video, website or etc. then constantly getting feedback and iterate to a sellable product which added value (the secret sauce). I'm working on a B2B product, ya.. theres no tolerant on a buggy or an incomplete product. Alpha and Beta test will be ours to test it out. MVP is more applicable on early stage or building a new product that has no proven market and test it out or as others comment said - situational. Anyway, the concept of MVP really change the approach on how people used to be building things (build and find customer)

Like
Reply

To view or add a comment, sign in

Insights from the community

Explore topics