[YS Learn] Indiagold Co-founder and ex-Paytm exec Deepak Abbot on the importance of product thinking for startups
In a conversation with YourStory, Deepak Abbot, Co-founder of indiagold, and former Senior VP-Products at Paytm, brings an understanding of why product thinking matters and why product is central to our industry.
Deepak Abbot is rather well-known in the startup world of product and growth hacking. The co-founder of
, Deepak has been the Senior VP - Products at Paytm, COO of Getsmart, and Zapak’s CPO.Having built several web-based products from scratch, Deepak is known to have taken several core products to scale.
In a conversation with YourStory, Deepak explains the importance of product thinking and why is it the focus word in our industry. He shares his experiences and lessons of building products to scale.
Editec excerpts from the interview:
YourStory (YS): Why is product thinking key for any startup, whether in the early or the later stages?
Deepak Abbot (DA): The way we define startups is that they are either trying to disrupt an existing model or creating something new. Most of it is four or five-year plan and these things are vague, and that is true even for a unicorn like Paytm that is thinking four to five years ahead.
The only way is to keep experimenting. To achieve that, you hire smart people who know what they’re doing, understand the target audience, understand the market, and take baby steps. These steps create something like a piece of code, a service, an app, a website – which build towards your goal. It is the product person who is going to transform the vision of the business person, techie, or the founder to something that the end-user can use.
Thus, nothing works without a product in the startup world. Now, in the digital world, the definition of a product is different from a manufacturing company or a services company.
In the startup world, the product is defined as the platform that we create for the end consumer to experience something that they may not have, or they may not have experienced in the same fashion.
With companies like Beardo, which are technically like traditional FMCG companies when we look at the product, their approach to consumer acquisition, branding, and distribution mediums were all different. They created an experience layer between the product and at the consumer. Thus, their definition of the product would be the experience they are creating for the consumer.
YS: How do you work on building the MVP for products that will keep transforming and changing? How do you approach them?
DA: While the definition of an MVP is a Minimum Viable Product, it depends on which segment you’re building it for and what’s your competition. If I am building a CRM, Helpdesk software, or an analytics tool, then I can’t simply just build an MVP because there are 10 established companies which can build great products and my MVP won’t have a chance, and the end customer now has certain expectations. They want things that are already available in the market, so you need to build better than that.
YS: While you are building a product with a larger vision to be fulfilled in a few years, how do you account for user feedback?
DA: Take the gold loan example: you generally go to a store with your gold, the store managers take the gold and check it for quality and purity, and they transfer the money. And when you repay, you take the gold back. If I have to change this behaviour – then I need to ask if I can go to the consumer's house, do the exchange in front of them and if they like the price, they get the money in five minutes.
There are many steps involved. How will I know how users will react to the whole procedure? Some people just call to check the value of the gold. Instead of building the entire tech experience on the app where they can order the person to come in and go the extra mile, can I have a simple form in my app asking if they want their gold valued by our experts? And then, we send someone in.
Building an extensive app doesn't always work. Can it be done one-on-one to understand their needs – do they want more money, lesser interest rate, lesser tenure? What are they thinking? For that, you don’t need tech. You need people who attend to real consumer needs.
Start with a basic service, understand their psyche and then hire and work on the complex steps of building the product.
YS: What mistakes do product people make?
DA: One of the biggest mistakes we make is believing that what a customer is saying is what they actually want. You need to understand that the customer is telling a problem and while they may say they want something, the solution will not come from them.
A customer, for example, will tell you that they want a juicer that can make pineapple juice without peeling it. You will create some complex mixer that does that but it is pointless. What the customer is actually asking for is a hassle-free and fast way to drink pineapple juice. They actually are telling you – I don’t want too many hassles when I want a pineapple juice made freshly at home. So the idea is to simplify the problem statement and look at the solutions.
Listen to the first 10 customers, understand the core problem and then see the simplest way of solving that. The product must be an extendable solution to a few other things they may do.
Cut the problem into multiple chunks and that’s the easiest way to solve. Maximise the coverage area you can get with a product and keep building on that. There is no single product that can cater to every single need of every person.
Even something like WhatsApp has 96 percent retention, there still are 4 percent people who don’t find its use.
YS: How do you build products that are completely ubiquitous and have high retention?
DA: All products with a cult status have two things that work for them – network effects and word of mouth. Products like WhatsApp and Facebook created a network effect where people started talking about the ease of use through friends and word of mouth.
Any product that gets these two things right will have a cult status. Even if one is missing they won’t have the standing.
For example, while Ola and Uber have word of mouth, they still aren’t used by 96 percent market share. It doesn’t have a network effect. If I am travelling on an Uber or Ola, it doesn’t mean my friends also will do so, unlike WhatsApp.
Today, with hindsight vision, we may say WhatsApp is easy to use. But if you think back, the network effects were strong. Your friends had it so you had it, and you were on it so you got your parents and siblings on it. And of course, the product was simple that reachd people within two taps.
YS: How do you bring in network effects and word of mouth for your product?
DA: When I am building a product, I need to think of three things – will it help me? By using this product, can I also help people around me? And by telling people about this product, will I look ‘cool’? All the Silicon Valley products work on this model where they make you feel ‘cool’ about using the product and you start doing word of mouth. You look like an early user and a cool person.
For example, the reason Shareit became popular was that people were sharing illegal videos and music on it. People realised how easy it was to share videos without going to clunky sites with malware. So when a young person tells their friends, your coolness factor increases. And it also has a usefulness factor.
Then the word of mouth kicks in, where the initial person gets rewarded. For example, Dropbox said if you get your friend, you get 2GB extra space and the more friends means more space for free.
You also can create scarcity like how Facebook and Gmail did with the invite-only option. It creates excitement.
For Indian products, I think we still have a strong belief that western products are cooler and better. You think you look cooler when you use a product that is made in the US; that is why Americans get more love in India.
Also, anyone in India who has built great engineering products caters to consumers outside India. They end up building globally-focused products.
YS: What advice would you like to give product developers?
DA: The only quality a product manager should have is the ability to ask a lot of questions and just be curious. You will learn a lot when you’re curious and apply that learning in a way, which translates into something that is easy to use.
Edited by Kanishk Singh