• Home
  • About
  • Archives
  • Authors
  • Contact
  • Polls
  • Small Biz Interviews
 

Posts Tagged ‘OnStartups’

Does it Matter if your Product is Minimally Viable or Maximally Buyable?

Wednesday, June 30th, 2010

I was reading this article by Dharmesh Shah on the OnStartups blog where he indicates that a Minimally Viable Product (MVP) is “a product that has the minimum set of features needed to learn what the market wants” and conversely he defines that Maximally Buyable Product (MBP) as “the set of features needed to capture the maximum potential opportunity in a market.”  Dharmesh then goes on to give 5 features of the Maximally Buyable Product.

I think the interesting point that is made in this article is not with the MBP but instead the Minimally Viable Product (MVP).  How does a company know when they have completed building their MVP?  When is an MVP “finished” enough in order to increase online sales and not result in abandoned carts of potential customers at checkout?  I know that when we were putting our finishing touches on our MVP one year ago for our KikScore trust seal product that it was very difficult for us to know when it was more important to get the product to market and when to add that one last feature that our customers would love.

My point here is that I think that building the MVP is not the most difficult thing most of the time.  Usually the entrepreneurial spirit inside of the people that are involved with MVPs is such that dreaming up and building the MVP is not the difficult part.  The difficult part may sometimes lie in the area of limiting the scope and defining the lines of exactly what the first iteration of the ultimate product is going to look like.  Initially, the MVP may be just a shell of what the founders of the company initially dreamed up but the team needs to decide as a whole when it is close enough to “learn what the market wants.”

How did your company define your MVP and how is your MVP different from your MBP?

Post to Twitter Tweet This Post

  • Share/Bookmark
 
 

Posts Tagged ‘OnStartups’

Should Start-Up Companies and Small Businesses Release Their New Software Early or Wait Until it is Perfected?

Wednesday, February 3rd, 2010
This question has long been debated by people in the software industry and has come under increased scrutiny since the dot-com era when every man, woman, and child with an HTML reference manual and a website domain registration started creating their own e-commerce sites.  Should start-up companies and small businesses release their first version of software as soon as possible in order to take advantage of being the first one to the marketplace or should they wait and carefully hone their product until it is more mature? 
 
I recently came across a post by Jason Cohen on the OnStartups blog where he makes a good argument for companies to take their time when releasing new products to the general public.  One argument that Jason makes in this post that I thought was very interesting is that the best products are not built by consensus and that some of the best products in recent history (like the iPod from Apple) actually went against conventional wisdom when they were initially released and thus early customer feedback can be an overrated benefit.  He mentions how the iPod has a battery that can’t be replaced, does not have an FM transmitter, and has a confusing wheel-based user-interface but still managed to revolutionize the way we listen to and purchase music.  While this is a great point, I would argue that these are a few major faults in the product that Apple was able to overcome because of the real game-changing feature that they introduced with the iPod: purchasing individual songs on iTunes and allowing them to be easily downloaded to the iPod. 
 
On this topic I would argue that going against public sentiment is generally a bad idea for start-up companies and that most software products will greatly benefit from early customer feedback. The iPod had the benefit of being developed by a multi-billion dollar company like Apple so it could take risks on certain features, but smaller companies don’t always have that luxury.  Getting a product in the hands of it’s target users early so that they can play with it a little and provide invaluable input can be a huge benefit to companies that decide to release their products and software before they are 100% complete.
 
Another argument that Jason makes in his post is that releasing too early can ruin a company’s reputation because the first customers to use the software may tell their peers that your software is buggy or doesn’t work the way it is advertised to work.  I would have to agree with this argument and I think that this is one of the biggest concerns for a small company releasing software early.  I think that a company has to set expectations with their early customers, but also has to take the time to find and fix any major bugs that would cause a negative customer experience before the initial release of their software.  There is a definitely a fine line here that small businesses and start-up companies must strattle in order to get their product early but not have it be buggy or lacking in functionality.  I think that this is definitely a hard call for a fledgling company to make early on but an important one that must be made amongst all the major stakeholders in the company.
 
So what is the answer to this age old question of releasing early or later?  I think in the end the answer is different for every company’s unique situation so in my final analysis I will say “It depends…”  What do you think?

Post to Twitter Tweet This Post

  • Share/Bookmark