Project Background
Meta planned to launch a new Threads creator onboarding and cross-posting flow that lets eligible Instagram creators set up Threads profiles faster and automatically share selected posts across both surfaces. The project is owned by a cross-functional team of 15 people across Product, Engineering, Design, Data Science, Legal, and Marketing. It was originally scoped as a 12-week launch tied to a major creator event, but the project is now in trouble at week 7.
The launch matters because leadership expects the feature to improve creator activation on Threads and increase weekly cross-posted content by the end of the quarter. However, engineering estimates the team is 3 weeks behind due to API reliability issues between Instagram and Threads, and Legal has raised new concerns about consent language for cross-posting defaults.
Key Stakeholders
- Director of Product, Threads wants the feature live before the creator event in 5 weeks.
- Engineering Manager, Instagram Integrations wants to cut scope to protect reliability and avoid on-call risk.
- Legal Counsel will not approve launch without updated consent and data retention language.
- Creator Partnerships Lead has already communicated the feature to 20 top creators and wants a visible launch.
- Marketing Lead needs a locked scope 2 weeks before launch to finalize assets.
Constraints
- Timeline: 5 weeks until the creator event; no date change allowed without VP approval
- Budget: $180,000 remaining for vendor QA, creator support, and launch ops
- Team: 8 engineers, 2 designers, 1 data scientist, 1 PM, 1 UXR, 1 legal partner, 1 marketing manager; no additional headcount
- Dependencies: Instagram account linking API, Threads publishing service, Legal approval, localized copy in 8 languages
- Launch target: US, UK, Brazil, India in phase 1
Complications
- The Instagram linking API is failing in 6% of test sessions, above the 1% launch threshold.
- One senior backend engineer is rotating to a P0 integrity incident for 2 weeks.
- Creator Partnerships is pushing for auto-enabled cross-posting by default, while Legal requires explicit user consent.
Your Task
- Build a recovery plan for the next 5 weeks, including scope decisions and milestones.
- Recommend what to ship for the creator event versus what to defer.
- Define stakeholder communication and escalation paths for the conflicting launch expectations.
- Propose launch readiness criteria, rollback triggers, and post-launch monitoring.
- Identify the top execution risks and how you would mitigate them.
