You have conflicting stakeholder requests for Threads. How do you decide what ships first

Problem Statement Description

Product context: Meta is a social technology company; its products include Facebook, Instagram, WhatsApp, Messenger, Threads, Quest, creator tools, and ads.

Threads is evolving within Meta’s broader social and immersive ecosystem, and multiple stakeholders are asking for different work to ship first. For example, requests may come from growth teams focused on user acquisition, creator teams focused on engagement and monetization, ads teams focused on revenue readiness, integrity teams focused on safety, or immersive/VR teams interested in serving VR enthusiasts and communities.

Your task is to describe how you would make an execution decision when these requests conflict. The focus is not on picking a single “correct” feature, but on showing how you would create a clear prioritization process, align stakeholders, manage dependencies, and decide what ships now versus later.

Assume Threads operates in a competitive social environment where speed matters, but Meta also has high expectations for reliability, user trust, safety at scale, network effects, and long-term platform quality. You should account for both near-term launch execution and the downstream consequences of prioritization choices.

The execution plan should consider:

- How you would clarify each stakeholder request, including the user problem, business objective, urgency, and expected impact

- How you would compare requests across common criteria such as user value, strategic alignment, effort, risk, dependencies, and reversibility

- How you would identify owners, required teams, technical dependencies, policy or safety reviews, and launch-readiness requirements

- How you would handle trade-offs between growth, engagement, monetization, creator value, VR enthusiast use cases, and platform integrity

- How you would define sequencing, milestones, decision checkpoints, and go/no-go criteria

- How you would communicate the decision to stakeholders who may disagree with the prioritization

- How you would monitor launch risk, prepare rollback or mitigation plans, and adjust the roadmap based on early signals

The goal is to demonstrate how you would operate as a PM in a fast-moving Meta product environment: bringing structure to ambiguity, making transparent trade-offs, aligning cross-functional teams, and ensuring the highest-priority work ships with clear accountability and measurable outcomes.