You are the engineering lead for a Google Meet feature launch: a new AI-generated meeting notes summary in Google Workspace. The feature was released to 5% of Workspace domains after 10 weeks of development by a 9-person team (5 software engineers, 1 TPM, 1 PM, 1 UX designer, 1 SRE). Within 48 hours, customer support tickets increased 32% because summaries were being attached to the wrong meetings for some shared-device and delegated-calendar workflows.
The issue was traced to an identity-mapping assumption in the launch plan that you approved. No data breach has been confirmed, but Legal and Privacy require immediate containment. The VP wants the feature back on track for a broader launch before the next Google Workspace admin event in 6 weeks because Sales has already briefed several enterprise customers.
Engineering wants to fix the root cause without creating more production risk. Legal and Privacy want the rollout paused until they review the remediation. Sales wants a customer-safe timeline they can communicate. SRE wants clear rollback criteria and reduced on-call load.
You have 6 weeks until the event, a remaining budget of $120,000 for vendor QA and temporary support coverage, and no additional full-time headcount. Two engineers are already committed 30% to unrelated Google Meet reliability work. Privacy review requires 5 business days after a remediation design is submitted. Any relaunch must begin with a domain-admin opt-in pilot capped at 50 customers.