The (Difficult) Trade-off between ‘Time to Market’ and ‘Readiness’

Product Management

The (Difficult) Trade-off between ‘Time to Market’ and ‘Readiness’

Several of our portfolio company founders and I have recently been debating whether to launch a new product/company quickly (and sometimes prematurely) or instead take more time to launch with a ‘fully baked’ product. The most compelling reason FOR launching early is to expose the product to real customers and begin the cycle of learning (and sometimes also to establish a first-mover advantage if relevant and important).  The principal reasons AGAINST launching early are that you deliver a half-baked or imperfect user experience and worse, you risk failing to meet basic user expectations.

Through discussions with other CEOs it became clear to me that many entrepreneurs struggle with different variations of the same question.  For example, while we’ve been debating this trade-off in the context of when we should launch a new company and how ‘perfect’ the product should be, other entrepreneurs whose companies are already in market wonder whether they should begin to scale-up aggressively or first invest in their infrastructure (provided they have validated product-market fit).athlete_at_starting_block

Clearly there is no generic answer to this question as many factors play a role – the nature of the business, competitive dynamics, user expectations, regulatory requirements etc.  For example, Indian Energy Exchange (IEX), a Lightspeed portfolio company, operates a national, electronic market for power.  The company’s platform is used by state utilities and industrial buyers to buy and sell power as well as ensure payment integrity and schedule power delivery.  Given the company’s mission critical role in the power market, it is essential to launch with a pressure-tested product that works flawlessly at scale.  However for many consumer internet or mobile companies that do not serve such mission critical use-cases, there is a strong argument to launch early with a minimum viable product and begin the learning cycle as soon as possible.  The key question we’ve been debating is how early?

My current thinking is that entrepreneurs must focus on getting to market quickly with a lean or light-weight version of the product (note that this is different from an incomplete or half-baked product), PROVIDED that:

  • The product supports the core customer use case,
  • The company has a level of technical and organizational readiness that will enable them to iterate, innovate and improve the product post-launch rather than engage in months of fire-fighting because the product or service was launched prematurely and fails to meet basic customer expectations, and
  • The company is ready to track user behavior, engagement, funnel metrics, cohorts etc so that iteration and improvement can be done in a data-driven manner – and the insight gained from an early launch can be actioned.

Note that this does not require the product to be perfect or ‘complete’ but it does require that the limited set of features and functionality work well and support the core use case. For example, an online retail company need not have full product selection, support every payment method or offer a full feature-set on day 1, but it should offer a frictionless user experience and be able to accurately ship an order to a customer within a reasonable time frame.  If the company has made appropriate investments in its organizational and technical infrastructure, it will be able to layer on additional products, functionality etc on a continuous basis post-launch and will be in a position to accelerate growth going forward.  Flipkart is a great example of a company that did this the right way – by focusing on getting the user experience right and establishing product-market fit before aggressively investing in marketing to scale rapidly.

Conversely, a company that launches prematurely, simply to get to market quickly, runs the risk of demonstrating early success, only to have to pull back later in order to fix a long list of ‘bugs’.  This can lead to unsatisfied customers, demotivated employees and a compromised competitive position.  Worse, this type of company wont be in a position to run experiments, learn from its customers and make rapid product improvements.

Companies with purely ‘virtual’ business models such as social gaming or music streaming can launch even more quickly with very lightweight minimum viable products to help establish product-market fit.  Once they see positive signs around traction, usage and engagement, they must prepare to handle scale prior to ramping usage.  After all, what would have happened to a company like Instagram if the system buckled under the tremendous growth?

[About the author: Bejul Somaiya is MD at Lightspeed Venture Partners. The article has been reproduced from Bejul’s blog post.]

Image source: tableatn

Leave your thought here


Recent Courses

Blockchain Course for Managers