Go or no-go call on a Zomato voice ordering integration with Alexa
Company: Nielsen
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a PM at Zomato. How would you decide whether Zomato should build an integration with Amazon Alexa?
```hint Start from the voice moment
Picture the Zomato tasks someone would actually want to do by voice, with no screen, and the ones that would be painful. That list shapes both the size of the opportunity and what a first version should do.
```
### Clarifying Questions
- Which parts of Zomato are in scope: food delivery only, or also dining out and table reservations?
- Is this Zomato's own idea, or has Amazon proposed a partnership with terms attached?
- Does the decision cover Alexa only on Echo speakers, or also Alexa on phones, TVs and in cars?
- What does a yes need to deliver: incremental orders, retention of existing customers, or a signal that Zomato is easy to order from anywhere?
### What a Strong Answer Covers
- Zomato's current goals and whether a voice channel serves or distracts from them.
- The voice use cases that fit Zomato's customers and the ones that do not, and which come first.
- A sizing of the opportunity and of the build and upkeep cost, with assumptions stated.
- Strategic risks of building on Amazon's platform: data sharing, who owns the customer, payments and dependence.
- A low-cost test, the metrics that decide, and go or no-go criteria set in advance.
### Follow-up Questions
- The pilot shows many people asking where their order is but few ordering by voice. Do you keep the integration, and what changes?
- Amazon offers featured placement in exchange for order data. How do you weigh that?
- How would your decision change if Google Assistant offered the same opportunity, or if Zomato added voice search inside its own app instead?
Overview: A product strategy question asking a Zomato PM how to decide whether the food delivery app should integrate with Amazon Alexa. It tests picking voice use cases that fit, sizing the opportunity against build cost and platform risk, weighing alternatives, and designing a pilot with go or no-go criteria.