How to Build a Product Marketplace with Yelp Product Manager
Ever wondered what it’s like to work as a Product Manager? We held an AMA event a while ago with the Head of Product at Yelp to give the audience a chance to ask every question they’ve ever had about Product Management. Here are the most interesting bits of that session.
Head of Product at Yelp
Natarajan “Raj” Subbiah is a results-driven Product Management professional, formerly of Microsoft and currently has been at Yelp for 3,5 years, with a track record of launching successful products. He holds a Bachelor’s Degree in Computational Mathematics and Statistics, an MBA and a Master’s Degree in Computer Science.
What do demand and supply mean?
Raj discussed how to build a product marketplace, and what the demand and supply mean. He also gave the inside scoop on the day-to-day work in Product Management, the challenges of the job and personal insight from Raj’s experience at working at different companies.
- What was the metrics you chose to focus on with the products you’ve worked on and how did you choose it?
- Challenge: Can we use existing demand at Yelp to solve the marketplace problem?
- Building a marketplace: demand and supply.
- What kind of experiments did you run to move the needle to increase for example the delivery at Yelp?
- How are you satisfied with the experiment results?
- Users & features; When to build when users want something and how to choose what to build?
- How do you know how many features to add so that it doesn’t take the focus off the app?
- How important is it for a startup for a product manager to keep both sides, demand, and supply, in the same team?
- How do products like Fitbit make sure that they’re still the market leader with the competition?
- How to change the product’s direction but not the product?
- How to set up the team for long-term bets?
- Does Yelp use A.I. or ML?
- How do you prioritize features?
There is no direct answer to any of these questions as it always depends on the company, product and situation. When it comes to prioritizing and building new features sometimes you just have to build it, ship it and see how it goes. If it goes well, good, if it doesn’t, you learn from it.