Diagnose a 20 percent drop in activation for Energy at global scale

Problem Statement Description

Product context: Tesla is an electric vehicle, energy, and software company; its products include EVs, charging, vehicle software, Autopilot/FSD features, energy storage, and solar products.

Tesla has observed a 20% drop in activation for its Energy experience at global scale, specifically among EV buyers who are expected to discover, configure, connect, or start using Tesla Energy-related products or services through the Tesla ecosystem. The activation journey may span touchpoints such as vehicle purchase, Tesla app onboarding, home charging setup, solar or Powerwall interest, installation readiness, utility integration, and first successful use.

Your task is to diagnose the drop as a product RCA problem. Treat this as a high-severity global anomaly where the business needs to understand whether the decline is real, where it is concentrated, what changed, and what actions should be taken to stabilize the funnel without prematurely jumping to a solution.

You should consider Tesla’s hardware-software integration, regional operational complexity, energy product dependencies, app and backend instrumentation, installation or utility constraints, and differences between EV buyer segments across markets.

The experience should consider:

- The exact activation definition, denominator, time window, and expected baseline for Tesla Energy activation.

- Whether the 20% drop is global or concentrated by region, vehicle model, app version, acquisition channel, energy product, installer flow, or customer cohort.

- Instrumentation checks, including event schema changes, delayed reporting, duplicated users, backend outages, consent changes, or attribution issues.

- Funnel segmentation from EV purchase through Energy discovery, eligibility, configuration, order, install scheduling, device connection, and first successful usage.

- Potential product, operational, supply, pricing, policy, utility, or competitive factors that could explain the decline.

- Evidence needed to prioritize hypotheses, including logs, funnel analytics, customer support contacts, installation data, payment failures, app telemetry, and regional market signals.

- Immediate mitigations, customer communication needs, escalation paths, and safeguards if the issue affects safety, billing, installation, or device control.

- Prevention mechanisms such as monitoring, alerting, ownership, experiment controls, release gates, and post-incident learning.

The goal is to demonstrate a structured RCA approach that separates measurement issues from real user or operational problems, narrows the anomaly through segmentation and evidence, identifies the most likely root causes, and recommends a responsible path to mitigation and long-term prevention.