Product Manager Speak: Deconstructing Ratings in India and the U.S.

This article has been authored by Kriti Mehra from UpGrad and Andrew Kaufteil from Cooper and was originally published on Cooper. You can read it here.

India and the United States have a lot in common.

Both countries are characterized by growing and diverse economies, and inhabited by passionate and entrepreneurial citizens.

In FY16, the US was the world’s largest economy, and India was the world’s fastest growing major economy, at a 7.6% GDP growth rate. In particular, the design and tech sectors of both countries are growing, as are our partnerships with one another. For example, India is the largest market for Uber outside the United States.

Walking around Bangalore or Hyderabad, you see logos of Facebook, Apple, AirBnB sewn onto backpacks, making you feel like you’ve been transported to Silicon Valley. Given our growing convergence, it’s important to understand our similarities as well as differences. One aspect of our cultures that are a bit different are ratings.

(Also Read: Top 3 Capabilities of Facebook Ad Targeting You Didn’t Know)


Image source: BBC

Rating Inflation

On a recent trip to India, Andrew Kaufteil, Senior Director of Growth & Partnerships for Cooper, ordered an Uber and noticed the assigned driver partner had a rating of 4.2. He had never seen an Uber rating so low. This scared him and he immediately canceled the request. He asked himself: what kind of a maniac could have a 4.2, and why was this person not fired?

Just a few months ago, he had looked at his Uber passenger rating (how he had been rated by drivers), and had been disappointed to see a 4.81. How could Uber keep a driver partner with a 4.2?!

He re-ordered, and his next driver partner had a 4.31. He needed to get to his destination, so even though the rating was low, he pursued the ride. He was surprised that his driver was courteous and competent, and the car was clean; a clear “5” in his estimation. In the following weeks, he identified lower overall ratings than he was used to in the States.

(Also Read: How Uber Uses Data Analytics for Supply Positioning & Segmentation)

Two approaches to ratings seem prevalent in India. One is an empathetic approach in which the consumer views delays in pick-up or speaking on the phone as minor annoyances and gives a 5 rating so that the driver is not penalized. The other is more value-based, where a 4 rating is associated with meeting expectations and a 5 is associated with exceeding expectations.

In the US, if service is competent and nothing goes wrong, a perfect rating — a 5 in the Uber example — is assumed. In India, consumers have a greater expectation of value. A perfect rating demands extravagant service.


Image source: Uber

This reality has broad implications for business. For example, many companies use Net Promoter Scores (NPS) to measure customer engagement with a product or service. However, given the cultural considerations explained above, companies with more Indian customers will likely yield a lower NPS than companies with American customers.

This is problematic for benchmarking customer loyalty to Indian versus American companies, or American companies catering to large groups of Indian customers, or vice-versa. In order for the score to be relevant, it must be normalized.

Moving forward, understanding your customer’s relationship with your product or service will require comprehensive design research to unlock customer goals, behaviors, and motivations, coupled with sophisticated data science modeling, taking into account where the rater is located, or their cultural background.

(Also Read: Product Manager’s Focus: Habit-Forming Products that Improve Lives)

Additionally, India uses ratings in different ways than the United States. Take for instance, Andrew presenting at Agile India 2017. When he looked at his profile leading up to the conference, he observed a rating of 210. He was jarred by the rawness of the rating, and embarrassed when he saw that another speaker at the conference, Evan Leybourn had 998 points. From the ConfEngine website, here is an explanation of the “points system” for the conference:

  • You earn 30 bonus points on your first activity in every new conference.
  • You earn 1 point when others like your proposal.
  • You spend 1 point when you like others’ proposal.
  • You spend 10 points when you propose a session.
  • You earn 100 points when your proposal is selected.

According to Kriti Mehra, raw points systems are widely used in India to create a sense of transparency and competitiveness that prompt individuals and companies to increase their engagement with web platforms.

Many US-based sites reward increased engagement differently; they hide their methodology or relate points to levels, labels, and/or titles to increase engagement with web platforms. For example, hyper-engaged users of Yelp are labelled “Yelp Elite,” though criteria and points for inclusion in Yelp Elite are shrouded and seemingly subjective. On TripAdvisor, a user’s points corresponds with different “levels” (1-6). 


Image source: TripAdvisor

The nuances of American and Indian approaches to rating are a reflection of different cultural contexts. It will be interesting to see how these systems evolve over time.

Will Indian sites soon have winners and losers?

Or will US-based sites adopt raw numerical scores?

Uncovering these differences will allow companies to design products and services for diverse customer bases, and to learn new approaches to engagement driven by design thinking and big data.

The following two tabs change content below.
Andrew Kaufteil

Andrew Kaufteil

Andrew is the Senior Director, Growth and Partnerships for Cooper. He identifies, manages and leads engagement campaigns across multiple channels to a wide set of audiences. Before joining Cooper, Andrew had designed engagement programs for a number of organizations, including UCSF, UC Berkeley, The George Washington University, National Defense University, Gratz College, and the Jack Kent Cooke Foundation.
Andrew Kaufteil

Latest posts by Andrew Kaufteil (see all)