Gemini engagement dropped 20% in two weeks among enterprise admins. Diagnose the issue

Problem Statement Description

Product context: Google is a consumer technology, ads, AI, and cloud company; its products include Search, YouTube, Android, Maps, Gmail, Chrome, Google Play, Workspace, and Google Cloud.

Google has observed a 20% drop over two weeks in Gemini engagement among enterprise admins. This segment includes administrators responsible for configuring Gemini access, managing licenses, setting security and compliance controls, monitoring usage, and supporting rollout across their organizations.

Your task is to diagnose the decline as an RCA problem. You should clarify what “engagement” means for enterprise admins, determine whether the drop is real or measurement-related, identify where in the admin workflow the decline is concentrated, and develop a structured set of hypotheses that could explain the change.

This is a hard RCA scenario because Gemini sits across enterprise workflows, admin tooling, user permissions, billing/licensing, compliance expectations, and broader AI adoption dynamics. The diagnosis should account for product, data, customer, operational, and market factors without jumping directly to a fix.

The experience should consider:

- How to define the engagement metric, including numerator, denominator, frequency window, and expected admin behaviors

- Whether the 20% decline is statistically meaningful versus seasonality, customer mix, reporting lag, or instrumentation changes

- Segmentation by enterprise size, geography, industry, Workspace plan, Gemini SKU, tenure, rollout stage, and admin role type

- Funnel or workflow cuts across login, dashboard visits, policy configuration, license assignment, usage-report viewing, and support actions

- Instrumentation checks for event logging, identity mapping, permission changes, dashboard tracking, and data pipeline reliability

- Hypotheses across product changes, UI discoverability, latency/errors, billing or licensing friction, policy restrictions, customer trust concerns, and competitor/market shifts

- Evidence needed to confirm or reject each hypothesis, including logs, admin feedback, support tickets, release timelines, cohort trends, and customer success signals

- Mitigation and prevention considerations, including monitoring, alerting, ownership, communications, and safeguards for future launches

The goal is to present a clear diagnostic plan that would help Google determine why Gemini engagement declined among enterprise admins, quantify the affected scope, prioritize the most likely causes, and guide the organization toward an evidence-based response.