Project Context
Google Meet is preparing a 10-week launch of a new AI-generated meeting notes feature for Google Workspace Enterprise customers. The work spans 11 people across engineering, UX, legal, QA, and go-to-market, and the launch is tied to a public roadmap commitment for the next Workspace release train. Midway through planning, you notice the tech lead is struggling: design reviews are slipping, decisions are getting deferred, and cross-functional partners are no longer getting clear answers.
Key Stakeholders
The Director of Product wants the feature included in the quarterly Workspace announcement and is pushing to hold scope. Legal and Privacy want additional review because notes may contain sensitive customer data. Sales wants an early customer preview for 5 strategic accounts. Engineering management is concerned about team health and does not want the lead burned out or publicly undermined.
Constraints
- Launch deadline: 10 weeks from today
- Remaining budget: $120,000 for vendor QA, legal review, and customer pilot support
- Team: 6 engineers, 1 UX designer, 1 QA lead, 1 PM, 1 legal partner, 1 GTM lead
- Dependency: Gemini summarization service API must be production-ready by Week 5
- Reliability target: 99.9% feature availability at launch
- No additional headcount approved
Complications
- The struggling tech lead owns the most critical integration with the Gemini summarization service and has not documented key decisions.
- Two senior engineers are already committed 30% to a separate Google Calendar reliability effort.
- Sales has told 5 strategic customers they may get access in Week 8, before full privacy sign-off is complete.
Your Task
- Create a 10-week execution plan that keeps the launch on track while addressing the struggling team member constructively.
- Explain how you would rebalance ownership, communication, and decision-making without damaging morale.
- Define what scope, if any, you would cut or phase to protect the launch date.
- Identify the top risks, trigger points, and mitigations.
- Specify launch success metrics and a rollback/readiness plan.
