jim farley has put a blunt spotlight on Ford Motor Company’s internal software and IT limits as the automaker pushes deeper into electric vehicle development. In a public admission tied to Ford’s next-generation EV effort, Farley said the company’s legacy systems were not built for the speed and complexity of modern electric vehicle work. The shift has already helped drive a Skunkworks team that bypassed those older systems and moved with modern tools.
Ford’s internal reset is now part of the EV race
The core issue is not a lack of ambition or engineering talent. It is that Ford’s digital backbone was built over decades for a different era of carmaking, when development cycles were slower and software had a smaller role.
That old structure became a problem as EVs turned vehicles into rolling computers with millions of lines of code. In that setting, engineers need systems that can simulate, iterate, and adapt quickly. Ford’s older setup could not keep pace, which led the company to create a dedicated Skunkworks team outside the usual internal stack.
That team was allowed to work with modern external tools instead of relying on the legacy environment. The result, as framed inside the company, was a faster and less tangled development process that could move with more flexibility than traditional automaking allows.
jim farley and the Skunkworks blueprint
jim farley’s admission has become more than a one-off acknowledgment. It now appears to be shaping Ford’s wider thinking about how the company builds vehicles and manages development work.
The Skunkworks effort, launched around Ford’s Universal Electric Vehicle platform, has been presented as a proof point for a broader internal modernization push. One specific element mentioned in the context is that the team used Dassault software for design, a tool Ford had not previously used. Those solutions then began moving into Ford’s core business, including a parts release system that had been in place for about 40 years.
That is a significant signal because the company is not treating the experiment as isolated. Instead, it is studying the Skunkworks method as a possible blueprint for larger change across the organization. For Ford, that means rethinking how software, design, and engineering tools fit together in EV development.
Why the timing matters now
The stakes go beyond internal efficiency. The context around Ford’s modernization push includes intensifying competition from fast-moving EV manufacturers, particularly those based in China. That pressure makes development speed, software integration, and tooling flexibility more than back-office concerns.
In that environment, legacy systems can become a bottleneck. Modernization of IT and development processes is being treated as a strategic priority alongside battery technology, manufacturing efficiency, and market access. For Ford, the question is whether the company can turn a skunkworks-style exception into a repeatable operating model.
Farley’s candor matters because it puts the challenge in plain view. Ford is not being asked to abandon its history, but to retool it for a different kind of vehicle business. If the company can carry the lessons of jim farley and the Skunkworks team into its main divisions, the next phase of its EV push may move faster, with less friction, and with systems that finally match the moment.
