SUNDAY REWIND: Deciding what to build after achieving product/market fit by Yuhki Yamashita

Yuhki provides some practical tips that product managers can use to decide what to build after they’ve achieved product/market fit.

When working at Uber, Yuhki found it took seven steps for a driver or rider to send feedback via the app, so a lot of feedback wasn’t shared. Yuhki and his team found that by conducting user interviews via driver lunches and ride-alongs, they could discover that many users shared similar problems.

By paying attention to the product hacks that users come up with, product people can find out which features should be prioritised.

Work backwards from the feature request to understand the problem so that you can come up with the best solution

Business insights and macro environment insights can be valuable sources of feedback.

Yuhki recalls how the ops team at Uber used SQL queries and emails to build the product, recruit drivers and expand the user base.

Your users can create plug-ins and applications that extend the functionality of the product. This has happened at Figma.

Competition makes everyone better

When users ask for a new feature, product managers can let them know why it isn’t a priority by sharing some of the other priorities and frameworks they’re working on instead.

Watch the original talk: Deciding what to build after achieving product/market fit by Yuhki Yamashita