I've been really appreciating your videos because you emphasize thinking through the problem and why it makes sense, rather than memorizing a bunch of frameworks with fancy acronyms
Great video. Some comments: I would prefer to keep revenue/profit metrics out of scope since they're not product success metrics - you mentioned # of completed rides as NSM, that's a good enough proxy for revenue imo. I would track Driver/Rider ratio at Uber level instead of at the driver-level.
Wouldn't this have been easier to do thinking about company goals (engagement and retention > monetization> adoption > acquisition), followed by evaluating the drivers and riders' top 3 pain points and defining success that helps us track our performance on a few prioritized painpoints.
What is the reasoning behind giving the average number of rides requested/week/rider (P2) a lower priority as compared to the number of cancelation/total number of ride (P1)?