Set Operating Cadence for Reels Team

Project Context

Meta is scaling a Reels creation and publishing team responsible for creator-facing improvements across Facebook Reels and Instagram Reels. You are the Engineering Manager for a 10-engineer team that recently absorbed two adjacent workstreams, and leadership wants a clearer operating cadence because delivery has become unpredictable over the last two quarters.

The team must support three parallel goals over the next 12 weeks: ship a new draft recovery feature, reduce P1/P2 production incidents, and improve roadmap predictability for cross-functional partners. The challenge is not defining the product strategy; it is designing how the team runs: planning, reviews, execution check-ins, escalation paths, and launch readiness.

Key Stakeholders

Key stakeholders include the Reels Product Manager, Design Manager, Infra partner team, Data Science partner, and Director of Engineering. The PM wants faster iteration and more flexibility for late-breaking creator feedback, while the Infra team wants fewer ad hoc requests and stricter dependency planning. The Director cares most about predictable execution and sustainable team health.

Constraints

• 12-week planning horizon
• Team of 10 engineers, 1 EM, 1 PM, 1 designer, shared DS support at 25%
• No additional headcount approved this half
• 20% of engineering capacity is reserved for on-call, bug fixes, and production support
• One senior engineer will be out for 3 weeks during Weeks 5-7
• Draft recovery launch is committed for end of Week 10 in internal planning docs

Complications

1. The team currently runs multiple overlapping meetings, and engineers report losing 6-8 hours per week to coordination overhead.
2. A partner Infra team has missed two recent dependency dates, making weekly status reporting look green until late in the cycle.
3. The PM wants to keep accepting scope changes up to launch, while the Engineering Director wants a firmer execution model.

Deliverables

1. Propose an operating cadence for the team across planning, execution, risk review, and launch preparation.
2. Define how you would allocate capacity across roadmap work, interrupts, and technical health.
3. Specify the decision points for scope changes, dependency escalation, and launch go/no-go.
4. Identify the top execution risks and mitigation plan.
5. Define the metrics you would use to know whether the cadence is working after one quarter.