Defining the Single North-Star Metric for a Travel Technology Company's Leadership
Company: Microsoft
Role: Product Manager
Category: Analytics & Experimentation
Difficulty: medium
Interview Round: Other
You are a product manager at a travel technology company. The product leadership team asks you to build one metric they can use to judge whether the product is succeeding and to steer the business. Which single metric would you build for them?
Define it precisely enough that an analyst could compute it, explain why it beats the alternatives, show how individual product teams would connect their work to it, and describe what would stop the metric from being gamed or from hiding harm.
```hint Look past the click
Most people buy travel only a few times a year, so measures of visits or app usage say little about value. Ask when a traveler has really received what they paid for and when the company has really earned its money, and what can still change between a search, a booking and the journey itself.
```
### Clarifying Questions
- What kind of travel business is this: an online agency selling flights and hotels, a lodging marketplace, a metasearch site that sends travelers to airlines and hotels, or a corporate travel booking tool?
- How does the company earn money: a commission on each booking, fees for referring travelers, advertising, or subscriptions?
- What will leadership use the metric for: setting annual goals, reviewing progress each week, or deciding where to invest across teams?
- Is there a current strategic priority, such as winning repeat travelers or improving profitability, that the metric should reflect?
### What a Strong Answer Covers
- A precise definition: the unit counted, the time window, and how cancellations, refunds and changed itineraries are treated
- A justification linking the metric to value for travelers, value for supply partners and revenue, with reasons it beats candidates such as booking value, searches or active users
- A breakdown of the metric into drivers that individual product teams own and can move
- Guardrails that expose gaming or hidden harm, such as discount-driven growth, refunds and support contacts
- Travel-specific measurement problems: the lag between booking and travel, seasonality and infrequent purchases
### Follow-up Questions
- Your metric grew this quarter, but support contacts per booking grew faster. How do you report the quarter to leadership?
- How would your metric change if the company were a metasearch site that never takes the booking itself?
- Trips often happen months after a product change. What faster signal would you give teams, and how would you check that it predicts your metric?
Overview: A product manager at a travel technology company must propose the single metric product leadership should use to steer the business. The prompt tests precise metric definition, links between traveler value and revenue, driver trees teams can own, guardrails, and travel issues such as booking lag and seasonality.