Root-Cause Triage for User Reports of Slow Connectivity at Google

You have just joined Google as a product manager. On your first day, word reaches you that users are complaining their internet is slow. What do you do? ```hint Confirm before you fix Before proposing any fix, find out what "slow" means here, whether the data backs the complaints up, and which product, network or group of users the problem is concentrated in. ``` ### Clarifying Questions - Which product am I responsible for: a service where Google provides the connection itself, or software such as Search, Chrome or YouTube that users experience as "the internet"? - Where are the complaints showing up (support tickets, app store reviews, social media, an internal alert), and roughly how many have come in compared with normal? - Did the complaints start suddenly, for example right after a release or an outage, or have they built up gradually? - Is there already an incident open for this, and who is leading it? ### What a Strong Answer Covers - Turning a vague complaint into a defined problem: which product, which experience, and which measure of speed - Validating and sizing the complaints against telemetry rather than reacting to anecdotes - Segmenting by region, network, device, app version and time to locate where the slowness is concentrated - A structured set of root-cause hypotheses, Google-side and external, checked in a sensible order - Immediate mitigation and user communication, then a lasting fix with metrics that show the problem is resolved ### Follow-up Questions - Your dashboards show latency is flat, yet complaints keep rising. What could explain that, and what would you do? - If the cause is a network operator Google does not control, what can you still do for affected users? - As a new PM with no relationships yet, how would you get engineering and support to prioritize this alongside their existing work?