If you were to create a new startup that put the legacy taxi experience on a mobile app, most entrepreneurs would take the traditional functionality and implement it directly in version one. Expected features would include:

  • Requesting a car
  • Inputting the destination address
  • Watching the car’s location on a map
  • Paying the fee for mileage and time
  • Providing a tip based on service and experience
  • Bonus: rating the driver

Only now, after being in business for eight years and raising $8.8 billion (source), Uber has rolled out tipping — You can now tip your Uber driver in the app.

This isn’t a critique on whether or not tipping is the right thing to include. Rather, Uber waiting eight years to add a feature that most entrepreneurs view as standard to the product teaches us an important lesson: the offline experience shouldn’t be recreated verbatim in an app. Rather, prioritize the product functionality that delivers the best experience to the user, and that often is a subset of the traditional functionality combined with new functionality that is only possible due to new technology.

Entrepreneurs would do well to prioritize product functionality based on value to the user, not on legacy features.

What else? What are some more thoughts on Uber adding tipping after eight years and what that teaches us about product functionality?

Source: https://davidcummings.org/2017/07/06/what-ubers-tipping-feature-teaches-us-about-product-functionality/