Product creators still think of features because they try to deliver a certain functionality. Instead, a product should actually be visualized as an answer to a pain point. Users don’t use products because they need certain features.
Product Management/Strategy Related Articles
Product creators still think of features because they try to deliver a certain functionality. Instead, a product should actually be visualized as an answer to a pain point. Users don’t use products because they need certain features.
Why would a user talk about your product? Often, it’s because your product is really cool and helped them do something that they would never have imagined possible. But users don’t want to be talking about your product all the time.
Finding product/market fit is an iterative process but bottom line is to establish key metrics that define product engagement and focus on those metrics relentlessly. Anything that doesn’t contribute to moving those metrics upward is not important before product/market fit.
While many of us are now laughing at the extent to which the movie has been copied, but to those who knew nothing about the original artwork (did you?), the movie still is a great piece of storytelling and proves a simple point that a well conceived products (i.e. sum) is greater than the sum of parts.
When there is a lot of uncertainty regarding the product, answering ‘why’ could (and I say, could) turn out to be a never-ending-loop. You might be looking for data that doesn’t exist, you could be looking for customers who are still asking for ‘better horses’.
Here’s a fact: if given a choice, an Indian consumer will buy a foreign brand instead of a domestic one. At its most basic level, this preference is sparked by prejudices against an Indian brand name, even though there is no valid reason to justify this bias.
Facebook focused on Harvard, Foursquare focused on New York and StackOverflow focused on programmers. In fact, StackOverflow’s growth and moving on to the cooking category from the programming category is a great case study. Apparently, programmers love to cook a lot!
When users interact with our products they experience how it works. The users will find the commitment towards the product if it fits just fine with the user expectations while they are trying to achieve their goal.
Our contention is that entrepreneurs should demonstrate product-market fit before investing in scaling up. In the Indian context, where new web services are cloned on a weekly basis, waiting to get to product-market fit can be difficult to do. Founders may feel pressured to scale prematurely, justifying this decision with reasons such as “it’s a land-grab” or “first-mover advantage”.
None of the CEO’s actually used the product. Every time they wanted data from our system, they’d just call the sales rep and ask him for information. We showed them how easy it was for them to look up the information on their cell phone, but they’d still call and “chat up” the rep, share more information about their business, their issues, etc.
