Operational Design Domain

An Operational Design Domain (ODD) is the fence a company draws around its self-driving car, saying "within these conditions, I can drive myself." That fence might include specific roads in a specific city, a set speed range, and clear weather only. It's similar to how fish can only survive safely within a certain water temperature range in an aquarium — once the temperature goes outside that range, the fish is in danger. In the same way, a self-driving car may not be able to make good decisions on roads or in weather that fall outside its ODD.

That's why self-driving car companies don't try to make their cars drive on every road in the world from day one. Instead, they narrow the scope down to a specific city, specific hours, and speeds below a certain limit, and only launch service within that narrow band. This is why news stories often mention that a robotaxi "only operates in certain areas" or "suspends service in severe weather" — it all comes down to this defined domain.

Expanding that domain becomes the company's next goal. A service might start out running only in a small neighborhood, then gradually widen to more roads, more weather conditions, and higher speeds as testing and data accumulate.

In articles, you'll often see phrasing like "this robotaxi's Operational Design Domain is limited to low-speed urban roads," describing a service's specific area or conditions. A common misunderstanding is that having a defined ODD means the car is an "unfinished product that can't go just anywhere." In fact, it should be read the opposite way — it's a sign that the company has clearly drawn the boundary within which it can guarantee safety.

Try asking a chatbot: "Based on this description of a self-driving car, summarize what roads, speeds, weather, and regional conditions it claims to be able to drive safely in: [paste article text]" — this helps you pinpoint exactly where the company has drawn its "safety boundary" in the article.