Project Context
Meta wants to launch a new set of Instagram Teen Account safety controls before the start of the next school year. The feature bundle includes stricter default privacy settings, expanded parental supervision prompts, and new in-app safety education surfaces. You are the PM responsible for planning the project from scratch across product, engineering, legal, policy, and operations.
The core team includes 12 people: 4 backend engineers, 3 client engineers, 1 designer, 1 data scientist, 1 UXR, 1 legal/policy DRI, and you. Leadership has asked for a launch in 14 weeks because teen safety is a company priority and there is external scrutiny on youth protections across Meta products.
Key Stakeholders
- VP, Instagram Product wants an on-time launch with visible impact before the school-year PR cycle.
- Legal and Policy want conservative defaults and complete review of all teen-facing copy and flows.
- Engineering Director wants to avoid destabilizing the Instagram app ahead of another Reels performance release.
- Comms and Public Policy want a clear rollout narrative and no preventable safety incident after launch.
Constraints
- Fixed timeline: 14 weeks to initial launch
- Budget: $180,000 for vendor moderation support, research incentives, and localization QA
- Scope must cover US, UK, and Canada at launch, with 8 languages localized
- No additional headcount approved
- Dependency on the central Meta integrity review queue, which currently has a 10-business-day SLA
- Engineering can only support one major app release train every 4 weeks
Complications
- The Legal lead says parental supervision copy may require an additional review cycle if it implies age verification.
- The Reels team has already reserved the week-10 release train for a monetization launch, creating a conflict for launch timing.
- Early UXR feedback shows teens understand the privacy defaults, but parents find supervision setup confusing.
Your Task
- Build an end-to-end execution plan from kickoff through launch.
- Define scope, milestones, owners, and key dependencies.
- Explain how you would handle the release-train conflict and any scope trade-offs.
- Identify top risks, mitigation plans, and launch readiness criteria.
- Define how you would measure launch success in the first 30 days.
