The main barrier to delivering software-defined vehicles is not hardware performance or algorithms, but structural, cultural, and organizational challenges. The automotive industry is not lacking ambition. OEMs, Tier 1 suppliers, and software providers broadly agree on the desired outcome: centralized zonal computing, cloud-native vehicle architectures, decoupled hardware and software life cycles, continuous over-the-air (OTA) updates, and, ultimately, edge-cloud-AI-driven mobility.
Conway's Law, formulated by computer scientist Melvin Conway, states that organizations which design systems are constrained to produce designs that are copies of the communication structures of these organizations. In automotive engineering, Conway’s Law operates with unforgiving precision.
80% of the most essential SDV enablers have not yet been deployed by OEMs and/or their supply chain, according to Omdia’s 2026 SDV Survey. The data also indicates that major software restructuring and organizational changes are extending beyond 2030, while concerns about legacy architecture and increasing software complexity are rising year-over-year.
For over a century, traditional automotive manufacturers organized engineering teams by physical domains such as powertrain, chassis, body, thermal management, and infotainment. Each division operated independently, with separate budgets, procurement processes, safety protocols, and Tier 1 vendor relationships.
This organizational structure led to the traditional distributed electronic control unit (ECU) architecture, with 80 to 120 dedicated microcontrollers running proprietary firmware and connected by hard-wired CAN and LIN buses. The software-defined vehicle requires reversing this approach. Modern vehicles need centralized, high-performance computing clusters, standardized abstraction layers, unified data buses, and microservices to manage cross-domain functions.
