WhatsApp · Execution · Entry · 45 to 60 minutes

WhatsApp launch call after a restore bug

WhatsApp is a messaging app that lets people send messages, photos, videos, and make calls with end to end encryption. Answer this product management case and get it graded line by line against a weighted rubric.

Prioritisation
User empathy
Risk assessment
Execution planning
Metric design

The situation

You are the APM supporting Android onboarding at WhatsApp. Your group PM asks for a recommendation by 6 PM today on whether to ship tomorrow's planned rollout of a redesigned chat backup restore flow for Android, which is meant to reduce setup drop off when people move to a new phone. Late in final QA, a bug was found: on some restores from Google Drive, users complete setup, see their chats, and only later discover that media sent in the last 24 hours did not restore and cannot be recovered from the local cache. Assume the following numbers are illustrative: the new flow is expected to improve restore completion by 3 percent, about 0.4 percent of restore attempts on Android 12 devices with less than 2 GB free storage hit the bug, and roughly 35 percent of affected users would lose photos or videos they care about. Engineering believes a full fix will take 5 to 7 days. Marketing, support, and app store timing are already locked for tomorrow, and the team can still hold the rollout or gate it with a remote flag. The hard part is balancing a small affected share against severe trust and data loss risk.

What to produce

A 1 to 2 page launch decision memo.

Your answer must

State a clear recommendation for tomorrow, full launch, delayed launch, or a limited rollout, and defend it with the given facts.
Estimate the user impact using the scenario numbers, including which segment is affected and why the harm is serious.
Lay out a 24 to 48 hour action plan with concrete steps, owners or functions involved, and decision timing.
Include a user communication and support plan for the chosen path, including what users would be told and through which channels.
Define 3 to 5 monitoring metrics and explicit thresholds that would trigger continue, pause, or rollback decisions.

Constraints

You have less than one working day to make the call, and engineering does not have time to fully fix and retest before the scheduled launch.
The mobile build has already been submitted, but the rollout can still be held or gated with a remote flag.
Because of privacy commitments and end to end encryption, you cannot add logging that captures message or media content.
You cannot rely on email outreach to warn affected users, because many WhatsApp users do not provide an email address.

Format

Use short sections such as recommendation, user impact, options considered, next 48 hours, and monitoring. Keep it practical and focused on tomorrow's decision.