Tesla Charging Experience
An independent strategy concept for explainable charging recommendations, driver control, and a staged MVP.
Overview
Independent PM interview case · 2 weeks · Strategy and prototype
This project explores how a charging interface could help drivers choose a station under uncertainty. I developed it independently for a Tesla China PM interview, covering the journey, recommendation logic, interface concepts, and a proposed validation plan.
The work is a concept exercise, with no Tesla affiliation or production rollout.
The Problem
A station list leaves several questions unresolved: will a charger be available on arrival, how long will the stop take, and which option best fits this trip?
I framed the opportunity around reducing the effort of comparing uncertain options while keeping the driver in control.
Key Design Decisions
Show a small set of explainable recommendations
The concept ranks two or three options by time, cost, and trip fit. Each recommendation explains its trade-off and can be dismissed.
Trade-off: fewer options simplify comparison but depend on reliable station data and a ranking the driver can inspect.
Explore two levels of detail
A concise recommendation supports a quick decision; a comparison view exposes more detail when needed. Automatic switching between these views remains a hypothesis to validate.

Extend the journey beyond station selection
Charging progress, departure reminders, and a summary of the stop connect the recommendation to its outcome. An initial MVP would use explicit rules before introducing predictive models.

Proposed Validation
These are evaluation measures, not observed results:
| Question | Measure to establish |
|---|---|
| Is choosing easier? | Decision time and comparison errors |
| Are recommendations understandable? | Comprehension of the stated reasons |
| Do drivers trust the choice appropriately? | Acceptance, overrides, and explanations for both |
| Does the stop match expectations? | Difference between expected and actual wait and charging time |
Baselines and target values would require real driver sessions and operational data. I would test recommendation clarity and user control before committing to adaptive layouts or broader network optimization.
Artifacts & Reflection
The deliverables are a strategy deck and interface prototype. The central lesson was to connect every recommendation to an explanation, an override, and a way to evaluate whether it helped.