Investigate why conversion fell after a Charging Network launch 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 launched a new Charging Network experience globally, spanning discovery, availability, routing, pricing, account/payment, and session start flows across app, in-car, and possibly web surfaces. Soon after launch, a key conversion metric dropped materially. You are asked to investigate the decline as a product RCA, not to redesign the product immediately.

Assume the affected users may include Tesla drivers, non-Tesla EV drivers using compatible chargers, fleet or energy customers, and customers interacting with charging as part of the broader Tesla energy ecosystem. The workflow may involve finding a charger, confirming compatibility and availability, navigating to the site, initiating a session, paying or authenticating, and successfully charging.

This is a global-scale issue, so the investigation should account for regional launches, charger hardware differences, payment/localization requirements, vehicle compatibility, app and vehicle software versions, network reliability, pricing changes, and operational dependencies. The challenge is to separate a real user-behavior or product issue from measurement, rollout, seasonality, or traffic-mix effects.

The experience should consider:

- How to precisely frame the anomaly: which conversion step fell, when it started, how large the drop is, and whether it is statistically and commercially meaningful.

- What denominator should be used, such as eligible users, charger searchers, route planners, session starters, payment attempts, or completed charging sessions.

- How to segment the decline by geography, charger type, vehicle type, Tesla vs non-Tesla users, app version, vehicle firmware, payment method, customer type, traffic source, and launch cohort.

- How to validate instrumentation, event definitions, logging delays, duplicate events, tracking changes, and funnel continuity across app, vehicle, backend, and charger systems.

- What hypotheses could explain the drop, including compatibility issues, degraded charger availability, pricing or fee confusion, payment failures, account authentication problems, localization gaps, routing errors, latency, or supply constraints.

- What evidence would confirm or disconfirm each hypothesis, including funnel analytics, logs, customer support contacts, charger telemetry, payment processor errors, field operations reports, and user feedback.

- How to distinguish launch-related impact from external factors such as holidays, weather, regional travel patterns, competitor charging promotions, outages, energy prices, or EV demand shifts.

- What immediate mitigations, monitoring, communication, and prevention mechanisms would be appropriate once the likely root cause is isolated.

Your goal is to explain how you would structure the investigation, narrow the problem space, identify the most likely root cause, and recommend the next decision point for Tesla while protecting customer trust, charging reliability, and global launch quality.