Product Management mantras from the 26th Playbook Roundtable

The 26th playbook roundtable was held last week (8th March 2014) at Delhi NCR and brought together over 15 startup and product practitioners to discuss and gain insights on some of the challenging aspects of growth and monetization in product companies. This roundtable was hosted at Eko India Financial Services office in Gurgaon, and was led by Amit Ranjan, Cofounder of Slideshare, and Amit Somani, CPO of MakeMyTrip. In a span of over 5 hours, a diverse set of topics were discussed. Prominent takeaways from the roundtable were insights on approaches to pricing, virality, growth decisions, pivoting, user experience etc. The following paragraphs detail the key learning from each of these above aspects.

Pivoting in a Business

Creating a successful company is essentially a search for the repeatable and scalable business model. To succeed in this search, companies should frequently make and test predictions about what will work in their business models. Businesses, no matter, which stage they are in are always pivoting. As a business, while you do focus on your revenues, but you also need to constantly keep thinking what will drive the revenue in 3 years from now and ensure that you slowly move in that direction. Of the so many internet companies, perhaps only a handful will survive 10 years. Amit Somani mentioned how MakeMyTrip is constantly looking at the next big thing. It started from a flight booking venture for NRIs to become the largest flight booking portal for the Indian market and is already evolving to cater to hotels and holiday packages. The next challenge for the company is mobile and ensuring that the company is successful in an increasingly mobile world.

IMG_2851Amit Ranjan talked about how often ventures have to 3-4 side projects or “distractions” that help you understand what will work in a fast changing industry and ensure you evolve to address these changes.

Moving from early adopters to 10x Growth

One of the best ways to achieve 10x growth after successfully validating your product and without spending too much or no money is virality. By definition, virality is designing and engineering your product such that it markets itself. A viral product derives much of its growth from its current users recruiting new users. A user could recruit another through a simple invitation (“Check out this product, it’s cool/useful/entertaining!”), or directly through using the product (“I want to send you money on PayPal!”). Virality is not an accident. It is engineered. Virality is more about width and depth. Amit Ranjan shared interesting insights on how the homepage of Slideshare during the initial days was designed for virality (with several banners and stickers to attract audience) during the initial days and when the portal was able to achieve significant growth, the homepage was redesigned for user experience.

Prioritizing Customer Inputs in a B2B Product

If you manage a product or service in the business-to-business (B2B) market, customer requests for features will be a regular part of your work. Requests come in through the sales team, service reps, and senior management, as well as directly from customers themselves. This makes it difficult for companies to decide which feature to include in the product or not. A good thumb of rule to decide whether to include the feature or not is that if 3 customers want it or a pushy a customer wants it and you can sell it to 2 more customers, then you should go ahead and include that feature. A key issue is to how do you know multiple customers have the same request? A common way is to utilize software which allows customers to post ideas, suggestions and requests. There are idea management providers that are good for this. Or you can user customer feedback sites. These asynchronous, always-on, open-to-all sites are well-suited for capturing suggestions.

IMG_2852In addition, you may need to check other areas. Your email often contains customer suggestions. Or you have a service ticket database you can check. Relevant knowledge will be in people’s heads, those who directly work with customers.

Also, it is very important to validate this feature. This can be done by rolling out first to your employees and then to few customers. This will help validate your thoughts.

Documentation and User Training

Generating user training manuals and videos can be a tedious job, especially for ERP kind of solutions, especially when the product is frequently undergoing changes. Also, the general trend seems to be that users have stopped reading trend. Even if people did decide to read the instructions, showing too many at once increases users cognitive load. Because users cannot read the hint overlay and use the app at the same time, they are forced to memorize the instructions and then apply them. Thus, it is more effective to focus on a single interaction rather than attempting to explain every possible area of the user interface.

Rather than generating documents and videos which will very soon become redundant, a better approach will be to have built in CTAs in the product to help/guide the users. This includes things such as built in FAQs (built using services such as Zendesk), using coachmarks etc. Presenting hints one-by-one, at the right moment, makes it a lot easier for users to understand and learn instructions. This interaction pattern has the added benefit of teaching the user at which point in the workflow these interactions or functions become applicable.

Making Sense of Data

As a product usage grows, enormous amount of data gets collected and sometimes making sense of the data becomes a challenge for Product Managers. It is no wonder that big players such as LinkedIn, Facebook etc. have large teams comprising of data scientists. Data crunching from this team of scientists even help the companies to validate the probability that a particular feature will be liked by their audience.

Product Managers are knee deep in the product and data can help take an unbiased look at the product, often yielding amazing insights and learnings. Data Analytics are important for one major reason: What you don’t measure, you can’t improve. Without knowing what the state of the system is, it is very hard, if not impossible, to do much to change or affect the system. You can, of course, make changes  blind, but without analytics you will never know whether the system was changed or whether nothing happened. It allows you to see what is currently happening, make a change and see what effect the change has.

IMG_2849A good way to make sense of data is to have an hypothesis and then look for local maximas. Apart from that, product managers can apply operations such as segmentation, funnels and cohorts to make more sense of data. Over time, as the system changes and improves, the KPIs (and consequently the metrics) will change, which in turn leads changes in what needs to be measured. It is likely that new flows and metrics will be discovered that prove crucial to the system so whatever the analytics used, they will need to be continuously adapted to meet this change and keep you on top of what’s happening in your product.

Encouraging Users to Sign Up

For a consumer product, completely logged in experience versus a logout experience is a choice between distribution and engagement. Slideshare and Youtube offer a complete logout experience as users do not need to login to access the portal. Linkedin devised an interesting way to incentivize users to sign up. They show a glimpse of profile to users who then need to sign up to view the full profile. It is also imperative that the process to get users through the front door of an application and engaging with content needs to be as simple and seamless as possible if an organization wants to win and keep mindshare.

Increasingly a lot of companies are using gamification, but it is more geared towards engagement rather than acquisition.

What Makes a Good Product Manager: Lessons from Doers

For solo product entrepreneurs and product teams that are caught in a vicious cycle of build, release, build release, we bring some insights from “doers” that will help them differentiate through the demanding skills of product development. Deep Nishar, who leads product management at LinkedIn, had said sometime ago that a product manager needs brain of an engineer, heart of a designer and speech of a diplomat. Is product management an art or science is an extraneous question. It is both and more. If a product manager can understand where code sucks and how to place a nice button to entice the user, his job is well done. It’s a deft left brain right brain play.

Indian product ecosystem is evolving and many product managers are learning on the way to make their successes and don’t ask heartwrenching slips, which anyway is part of the game. These first-generation product managers are just sowing their seeds of a developing ecosystem. When we asked some accomplished product managers who are part of successful product ventures in India—Amit Somani of MakeMyTrip, Ravi Padaki of Pravi Solutions, Shivakumar Ganesan (Shivku) of Exotel, Krishna Mehra of Capillary Technologies, and Shrirang Bapat of Pubmatic—as to what makes a successful product manager, the answers were varied and thought-provoking.

Key aspects of becoming a product manager

Krishna Mehra and Shirang Bapat are unanimous in their view that a product manager should understand the pulse of the customer. Mehra adds another element to the product manager’s repertoire – execution. Ravi Padaki takes a holistic view in stating the a product manager should understand the how business works, be creative in solving problems for customers that may not translate as features in the product, and be a great communicator, not just in listening to customers but to the market as well. Amit Somani demands insane curiosity, building capability, and knowledge of how to work through influence. Shivakumar Ganesan (Shivku) of Exotel feels the product manager expects the product to sell itself and works backwards from market needs to build a suitable product. He feels product manager is a misnomer and the correct term is “market manager.” Shivku brings out the creative plus execution aspect of a product manager when he says, “he is willing to write a hack to keep the elegance.” Aesthetics are important for a product manager whereas the coder just concentrates on architecture and design.

Attributes demanded: ability to understand customer pulse, creativity, curiosity, influence without authority, capability to build what market needs

Top three priorities of a product manager

Ravi Padaki is emphatic that shipping is the first priority. Iterating and scheduling releases based on feedback and market response follows. Krishna Mehra cautions against building without validation and product discovery. In enterprise market, building for wrong requirements means loss of cost and time, while customer feedback should be gauged quickly for consumer products. Focusing on customer experience is the first priority of Shirang. Amit bets on a big vision to begin with. According to Shivku, customer support comes first.

The second priority for all the five revolves around execution. While for Amit, understanding customer requirement and translating it into a product is important, Mehra focuses on the ability to work with the engineering, design and QA team to deliver high-quality product. Shirang takes it a step ahead to focus on communication between customer, product manager, and engineering, which again emphasizes on aligning customer needs to building the product. Shivku emphasizes on product-market fit, while Ravi bets on validating the product through feedback through all stages of development.

The third priority for product managers is taking several parts of the organization together to build a successful product. For Shirang, the third priority is fitting the non-functional requirements into the product. Mehra wants the product manager to drive customer success by working with other parts of the organization. Ravi terms it triangulating and prioritizing, which means synthesizing inputs from various parts, which the product manager likes some part of it or not. Shivku calls for inventiveness in creating a product out of ideas from the junk. Amit takes shipping, iteration and metrics to the end.

Three priorities: 1. Enlisting customer requirements/support, 2. execution and continuous iteration based on feedback, and 3. taking the organization along during product development