The three most important questions in product management
Photo by airfocus on Unsplash

Product pods (engineering, design, product) are the central engine at any eCommerce or SaaS company. They are responsible for defining and measuring success, prioritizing the most necessary work to be done, and building what your users need. There is so much work that could be done, and about a dozen teams competing for engineering attention at any given time.

This is why Product Management is so critical to a successful product pod — we hedge against chaos. We sit at the front lines and handle intake for each idea, shift in strategy, bug, and nice-to-have enhancement. At times, it feels like there aren’t enough hours in the day to give every idea the attention and vetting it needs.

The fastest way to burn out as a PM is to treat all incoming work with the same high priority and throw yourself at it indiscriminately. I have fallen victim to this myself, and when I’m overwhelmed by intake, I’m not able to do my job well. To ground myself, I always ask three core questions when considering new work.

1. Is this a problem?

One of the most important tenets of Product Management is that users do not seek products, they seek solutions. Some of the biggest failures in the business world occur because the company did not solve an actual user problem. Ask yourself, “Will this feature solve a real user’s problem?” or “Is there something that is broken?”

If you answered yes, then you have successfully identified a problem. If you answered no, but you still feel like you have a problem, then you’re probably also hearing one of two things:

Our competitor has this feature, which means we must build it too! [Stakeholder/leadership] is really pushing for this feature, so we have to do it!

These are not good reasons alone to build something. A competitor’s feature is only worth replicating if you share the same user base with the same problems. Even in this case, it probably makes more sense for your product to implement a different solution that leverages your product’s core competencies rather than copying what a competitor built.

The second scenario is the more difficult situation to work through. The most difficult conversations in my career have come from pushing back against the popular opinion within my organization. The reality is, if the product, stakeholder, and leadership teams are all in alignment with why users use the product and what success means, you shouldn’t have this problem. These conflicts occur when there is internal politics beyond your control or there is misalignment within the broader organization regarding what success means. You will need to work with the relevant leaders to resolve this issue before you can competently prioritize work.

2. Is this a problem that needs to be solved?

Anyone can identify a problem, but it takes an adept Product Manager to decide if it’s a problem worth solving. If you spend engineering hours solving a low-severity problem, you face the opportunity cost of not solving more severe or important problems. All the while, your customers may leave you for a competitor who can provide solutions to the problems that really matter to them.

To determine if you have a problem worth solving, consider the following:

For feature work: Will this feature open us up to a new market or customer base? Is this a feature that a significant portion of our existing user base will use? Will this feature improve our north star metric or other success metrics? For bugs: Is this a high impact or high severity bug? For tech debt: Will this improve our ability to scale? Is there a legal or security threat? Will this significantly improve performance?

3. What is the best solution to this problem?

Once you’ve identified a pertinent problem, it’s time to brainstorm! Even when there is an obvious or popular solution within your organization, I still encourage you to consider every possible solution, including the solutions that a different team would work on. Publicize your problem across the organization and encourage suggestions from anyone. Once, I set up in my company’s cafeteria during lunch with a sign that said “Help us fix our clunky enrollment process!” and asked my colleagues to test the experience and give me their feedback and ideas.

Keep in mind that there might be short-term and long-term solutions, or a simple MVP with a series of enhancements. List out every solution from the least amount of effort (or MVP) to the most amount of effort. Use your best product judgement to nail down one to three good solutions by yourself. Then, speak to engineering and stakeholders for their feedback. I usually default to the lowest effort, medium/high-impact solution to the problem in the interest of speed, but sometimes a more elegant solution is required depending on the size and severity of the problem.

Let’s walk through an example:

The problem: A decreased bottom of funnel conversion rate last quarter has led to lower revenue per session.

Is this a problem that needs to be solved? Yes, this decreased revenue per session has led to a major financial loss for the company. Increasing it by even 5% would lead to an increase of $3M next quarter.

What are all of the possible solutions to this problem?

Fix a bug that sometimes prevents users from entering their shipping address Test removing distractions, like upgrades and recommendation carousels Change our credentials policies to never sign-out users from the website so they don’t have to worry about logging in when they reach the cart Integrate PayPal or Visa Checkout into the cart page to reduce friction Invest in performance upgrades to improve cart page load times on the mobile app Test removing the $50 minimum for free shipping

The solution you ultimately decide to go with will depend on feedback from engineers, designers, stakeholders, and leadership. While a test removing the $50 minimum for free shipping may seem like a quick solution, this would likely require sign-off from a whole host of strategy and leadership teams because the $50 minimum is a cost-saving incentive so the company doesn’t lose money on shipping low-value packages. Similarly, integrations with PayPal or Visa Checkout could take months of legal review and site integration, which won’t be a speedy solution to your current revenue per sessions problem. This is why, in my experience, it is best to start with the smaller work efforts your team can implement quickly while you, the product manager, work on securing some of the larger solutions with wider groups.

Conclusion

This whole process requires some finesse and judgement calls. For instance, your colleague may think a decrease in enrollments by 7% is a problem that needs to be solved, but you disagree because you’ve made the enrollment process more tailored to a specific customer segment. Or, you may want to start with the low-effort, medium impact solution but leadership would rather you start with the high-effort, big swing solution. There are no ‘right’ answers here, just well-informed and well-vetted ones. Use these three questions as a guide to help you prioritize the right solutions to your most important user problems.
['Olivia Belitsky']
['Prioritization', 'Solutions', 'Problem Solving', 'Product Management', 'Kpi']