Tesla Renames 'Full Self-Driving' to 'Assisted Driving' in Europe

What happened

Tesla has renamed its "Full Self-Driving" feature to "Assisted Driving" for customers in Europe, according to reporting from Wired and TechCrunch. The change follows sustained criticism that the original name overstated the system's actual capabilities, potentially leading drivers to believe the car could operate with less supervision than it actually requires.

The rebrand applies specifically to Tesla's European market, where regulators and safety advocates have been more vocal about the gap between marketing language and the technology's real-world performance. The underlying software and its capabilities are not reported to have changed — only the name and, by extension, the framing presented to drivers.

Why it matters

Names are not neutral. How a company labels a product shapes the mental model customers build around it — what they expect it to do, how much trust they place in it, and how carefully they supervise it. "Full Self-Driving" implied a level of autonomy the system does not deliver, and that mismatch between promise and performance sits at the centre of long-running safety concerns and regulatory scrutiny across multiple markets.

For leaders in experience and product design, this is a live case study in how naming conventions function as a behavioral lever, not just a marketing choice. A label can either calibrate a user's attention and caution appropriately, or it can quietly erode the safety margin built into a product by encouraging overconfidence. Regulatory pressure in Europe appears to have forced a correction that marketing alone had not delivered.

The Renascence take

This is less a story about autonomous vehicles than about the words companies choose to describe imperfect automation — and who ultimately decides when those words are misleading enough to warrant change.

Most organisations treat product naming as a branding decision rather than a safety or trust decision, and that is the real lesson here. A feature name sets the customer's expectation of how much vigilance they need to exercise, and when the name promises more than the system delivers, the gap gets filled by customer assumption — rarely in the company's favour. Any operator shipping automation, AI-assisted features or anything that reduces visible human control should stress-test the name itself, not just the interface, against the question: what will a reasonable customer assume this does, and is that assumption safe? Waiting for a regulator to force the correction, as appears to have happened here, is the expensive way to learn that lesson.