Recover a Mistake Before Launch

Project Context

You are a Software Engineer on the Google Workspace team, leading execution for a new Gmail feature that uses Gemini to generate thread summaries for enterprise users. The feature has been in development for 10 weeks with a cross-functional team of 9 engineers, 1 product manager, 1 UX designer, 1 privacy reviewer, and 1 SRE. The VP has committed to a limited launch to 500,000 Workspace users in 6 weeks because a major customer renewal depends on it.

Two weeks before the planned code freeze, you discover that your team made a mistake: the current implementation logs partial email content in Cloud Logging for debugging, which violates the approved privacy design and creates launch risk. Fixing it fully will likely delay launch by 2 weeks; shipping as-is is not acceptable. You need to handle the mistake, reset expectations, and still deliver the highest-value launch possible.

Key Stakeholders

The Gmail PM wants to preserve the committed launch date. The Privacy and Legal teams want zero policy violations and are willing to delay. The Engineering Director wants a credible recovery plan without burning out the team. The Sales lead for Workspace wants at least a pilot launch for the renewal customer.

Constraints

• 6 weeks until committed launch date
• 2 weeks until code freeze
• $120,000 remaining budget for contractor QA and launch support
• Team capacity: 9 engineers, but 2 are shared with a parallel Google Meet reliability project at 40% allocation
• Dependency: Privacy re-review requires 5 business days after code changes
• Rollout surface: Gmail web only; Android and iOS are explicitly out of scope

Deliverables

1. Create a recovery plan that addresses the mistake and protects user privacy.
2. Recommend whether to keep the original launch date, reduce scope, or delay.
3. Define stakeholder communication and escalation steps.
4. Propose launch criteria, rollback triggers, and post-launch monitoring.
5. Identify the top execution risks and mitigations.

Complications

1. A large Workspace customer has already been told to expect pilot access on the original date.
2. Privacy reviewers are available for only one review cycle this month.
3. The PM is pushing to keep the date by limiting the fix to new traffic only, but historical logs from the last 3 weeks must also be addressed.