Reposted from my original post Medium

Deciding What To Build NEXT? – HelloMeets – Medium

Product Managers are an interesting lot. Talk to any PM about their product and they would have a hundreds of different ideas about features they want to add to their product.

With hundreds of ideas and feature requests from users inundating a PM’s ideabook, the question that often bothers a PM is deciding what to build next?

Add to it the fact that over-complicating and adding too many features to the app not only adds to the complexity of the app but also impacts the User Experience.

The most essential rule for Product Management is to let the user find what he is looking for in the shortest amount of time. Any obstacle in the process only leads to dropoffs.

We talked to some of the seasoned Product Managers from HelloMeets Community and this is the number one rule they live by — ”Build to solve the pain points of your users”

We asked them, how they found the pain points of their users.

User Interviews

Feedback from your users is the best way to identify the pain points in your app.

Gagan Mahajan, PM at Sheroes says he lives by user interviews. He calls his new users within a week of their registration and asks them if they found what they were looking for! We think, that’s a pretty effective way to solicit feedback. But, most often, there will be many people who sign up for your services and apps passively without any ideas of what they are looking for. So, in order to get the most valuable feedback from your users, your User Interviews should be structured.

Sahil Pruthi, Product Manager at Traveltriangle who has brought massive growth in the android & iOS apps in the last 2 years has the following advice:

1. **Fixed group discussions: He **brings 4–5 of his past travellers together and gets them to talk. Through this he gets amazing insights on the various problems a user faces, and the priority because he see people relating to each others problems.

2. Face to Face interview: Typically 45 min — 1 hour interview with the user to understand the pain points. Build an empathy map and buyer persona.

Some good sources to know more about this are :

The Practical Guide to Empathy Maps Creating a 10 Minute User Persona

How to run an empathy User Journey Mapping workshop

3.** Be a User Yourself:** Eat your own dog food. In his case, he booked a trip and kept taking note of the problems he faced.

4. If you’re a tech company selling some product, make it a practice to stay with folks that sell the product. This way you’ll be better able to understand a lot of problems that a consumer faces. He says, In my case, I make it a regular practice to spend time with the operations people/travel agents.

Focus on the outcomes, not the industry

This point is oft-repeated in the industry but gets quite lost during the product development. Product Managers mostly look at the products of their competitors or the industry as a whole. Thus, their product roadmap gets filled with features some of which are not even relevant to the users.

The most important thing you have to remember as a Product Manager is that you create solutions to the problems faced by your users.

When you’re building or managing a new product, you have to believe you can create a better solution that people will want to use because it delivers a better outcome for them.

A strong understanding of the outcome customers want, and how they currently get it, is essential for you to succeed in product management.

Focusing on outcome, rather than category, industry, or product type, lets you understand your real competitors. The second a company focuses on “the industry it’s in” rather than the “outcome it delivers”, it loses touch, and shortly after, loses customers.

• Think of the outcomes that your app is trying to achieve and find how those outcomes are currently being met by your users.
• Research what solutions they’re using, and breakdown the steps required to achieve those same outcomes by using your app.

For example: Some people want to stay informed about latest news without actually reading the whole 500 word article. Now they have inshorts.

Arranging a taxi in a city used to involve calling many numbers until you found a company with availability, followed by a lengthy dialogue about your location, destination and required arrival time. Now, you can call a cab with the press of a button via Uber and Olacabs

It doesn’t have to be as revolutionary as the ones mentioned, but there are hundreds of different things that your users are currently doing in their day-to-day life. Your job as a Product Manager is to figure out how you can help your customers get the same outcome or albeit a better one in the shortest amount of time possible.

Jeff Bezos is famous for saying “focus on the things that don’t change”.

The problems that people and businesses encounter don’t change often. The ways they can be solved changes almost yearly.

So it stands to reason that making things people want should start with the “what people want” bit, and not the more tempting “things we can make”.

Prioritization

Prioritization of the features is extremely important. You have to build products based on how impactful the feature will be on a customer’s life. The second axis is based on a customer’s expectations.

If you build features that are expected from your app, it can fall in 2 categories:

Must-Have: These are features that are essential for your app and they have the most impact in the user’s life.

Who-Cares: These are features that are nice to have but doesn’t really create significant impact.

And, if you decide to go above and beyond and decide to build something extraordinary, it can either delight your users so much that they react with “WOW!” or doesn’t create significant impact but they still love it and call it a “Neat” move.

For example, when Whatsapp launched “Stories” in their app, it didn’t really create any significant impact in their user’s life, instead it backfired though some users still called it a neat move.

As startups, it is important for you to always aim for the “WOW” reaction from your users. But this should not be at the cost of “Must-Have” features.

For a more in depth explanation of various techniques for prioritization, take a look here. via ProductPlan & Jim Semick

Deriving meaning from Metrics

**Product Managers live by Metrics and KPIs (Key Performance Indicators). **But, with multiple metrics and analytics to look at, it becomes important to prioritize what metrics are important for you and your company. A business in general can has any of the following goals:

1. Increase the DAU
   Daily Active Users, as the name suggests gives you an estimate of the no. of users who are using your app everyday. Of all the different metrics, DAU is one of the most important factor for the success of your app. Some app developers can get a huge boost in the number of downloads of their app pretty quickly by having a large marketing budget and spending money on incentivized app downloads. But, it is commonly known, across all industries, 80% of all app users churn within 90 days.

To know more about what’s a Good Retention Rate, look here.

2. Increase the time spent by the user in the app

3. Increasing Retention

The graph below showcases the average retention rate by industry after 30, 60, and 90 days respectively. As you can see, the average retention rate varies by industry.

Currently, Media & Entertainment apps retain the most users on average, with a 24% retention rate post 90 days.

Source: Localytics

So the question becomes, how do we improve the retention?
With the advent of various in-app engagement solutions, real-time push notifications and improvement in the location-based marketing capabilities, there are myriad of ways you can take advantage of them to improve user engagement.

4. Increase Conversion in case of m-commerce app

Once again Gagan and Sahil agree that you should be clear about what you want the user to accomplish in your platform. Break it down into multiple steps, track how many users are reaching each step and see where they are dropping off more than usual.

For example: Check where you have the most no. of drop-offs in your sales funnel i.e from the time your user conducts a search to the point where your user completes the payment.

High number of searches, low number of product view means that you need to work on search results relevance.

It is important to break the user into product funnels → a visitor to lead to activated to conversion. There are various tools to understand and leverage these analytics.

Use Heatmaps / Live user action videos, funnel analytics to understand the drop offs in the various stages of the funnel.

But, it’s very easy to get lost in optimizing your site or app by picking up the wrong metrics. Therefore Sahil points out that it is very important for you to have a structure in mind of the various stages the user is in. And then bucket the problems.

Complexity Cost Of Your Features

In a recent article, by First Round, Kris Gale, VP Engineering at Yammer talks about out how features can create complexity cost in an engineering organization.

“Complexity cost is the debt you accrue by complicating features or technology in order to solve problems. An application that does twenty things is more difficult to refactor than an application that does one thing, so changes to its code will take longer. Sometimes complexity is a necessary cost, but only organizations that fully internalize the concept can hope to prevent runaway spending in this area.”

He goes further and talks about how often Product Managers use the phrases, “how hard would it be…” and “can’t you just…” during their conversation with engineers. These phrases reflect very poorly on the product managers. What might take two weeks right now adds a marginal cost to every engineering project we’ll take on in this product in the future. In fact, I’d argue that the initial time spent implementing a feature is one of the least interesting data points to consider when weighing the cost and benefit of a feature.

Therefore, as a Product Manager, you should also carefully discuss the engineering complexity of the feature and the codebase that needs to be changed in order to support the feature. And of course, don’t forget to do a cost benefit analysis of the time your developers would need to spend developing the feature with the time they could have spent working on some other low hanging fruits.

Some of our upcoming meetups:

Measuring Design Success — 20th May — Bengaluru

Startup Hiring Event — 28th May- Delhi

Also thanks to Sahil Pruthi and Gagan Mahajan for sharing their insights with HelloMeets Community.