Setting Ranked Goals and Success Metrics for a Meta-Built Headphones Product

Quick Overview

A Meta product manager prompt that asks you to set goals for a Meta-branded headphones product and choose the metrics that track each one. It tests tying a hardware product to Meta's AI and wearables strategy, ranking user and company goals, defining a north-star metric, and adding guardrails for privacy, reliability and returns.

Setting Ranked Goals and Success Metrics for a Meta-Built Headphones Product

Company: Meta

Role: Product Manager

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Other

You are a product manager at Meta responsible for Meta Headphones, a pair of Meta-branded headphones. Set the goals for this product: what it should achieve for the people who wear it and for Meta, how you would rank those goals against each other, and which metrics would show that each goal is being met. ```hint Why would Meta make headphones? Meta earns its money through its apps and already sells glasses and VR headsets. Work out what headphones add to that strategy before you list any metric; that reasoning decides which goal comes first. ``` ### Clarifying Questions - Is Meta Headphones already on sale, or are we setting goals for its first launch? - What does the product include beyond audio and calling: a voice assistant, sensors, or pairing with Meta's glasses and Quest headsets? - Is the hardware expected to be profitable on its own, or may it run at a thin margin to grow use of Meta's apps and AI assistant? ### What a Strong Answer Covers - A clear reason Meta makes headphones, tied to its mission and its wearables and AI strategy, used to rank the goals instead of listing them side by side - Distinct user goals (sound and call quality, comfort, battery, hands-free help) and company goals (assistant and app usage, ecosystem pull, a viable hardware business) - A north-star metric plus precisely defined supporting metrics for each goal, with guardrails such as return rate, accidental voice activations and privacy complaints - How the goals and their weight shift between a launch and a mature product - Tensions between goals, such as assistant features against battery life, or a low price for adoption against margin ### Follow-up Questions - Six months after launch, sales beat the plan but weekly assistant use through the headphones is flat. Which goal is failing, and what would you investigate first? - How would you measure whether owning the headphones increases time in Meta's apps, given that buyers are already heavier users? - If the headphones had to make money on hardware alone, how would your goals change?

Overview: A Meta product manager prompt that asks you to set goals for a Meta-branded headphones product and choose the metrics that track each one. It tests tying a hardware product to Meta's AI and wearables strategy, ranking user and company goals, defining a north-star metric, and adding guardrails for privacy, reliability and returns.

Meta logo
Meta
Jul 28, 2026
mediumProduct ManagerOtherAnalytics & Experimentation
0
0

You are a product manager at Meta responsible for Meta Headphones, a pair of Meta-branded headphones. Set the goals for this product: what it should achieve for the people who wear it and for Meta, how you would rank those goals against each other, and which metrics would show that each goal is being met.

Clarifying Questions Guidance

  • Is Meta Headphones already on sale, or are we setting goals for its first launch?
  • What does the product include beyond audio and calling: a voice assistant, sensors, or pairing with Meta's glasses and Quest headsets?
  • Is the hardware expected to be profitable on its own, or may it run at a thin margin to grow use of Meta's apps and AI assistant?

What a Strong Answer Covers Guidance

  • A clear reason Meta makes headphones, tied to its mission and its wearables and AI strategy, used to rank the goals instead of listing them side by side
  • Distinct user goals (sound and call quality, comfort, battery, hands-free help) and company goals (assistant and app usage, ecosystem pull, a viable hardware business)
  • A north-star metric plus precisely defined supporting metrics for each goal, with guardrails such as return rate, accidental voice activations and privacy complaints
  • How the goals and their weight shift between a launch and a mature product
  • Tensions between goals, such as assistant features against battery life, or a low price for adoption against margin

Follow-up Questions Guidance

  • Six months after launch, sales beat the plan but weekly assistant use through the headphones is flat. Which goal is failing, and what would you investigate first?
  • How would you measure whether owning the headphones increases time in Meta's apps, given that buyers are already heavier users?
  • If the headphones had to make money on hardware alone, how would your goals change?