Detroit has always been a city of systems.
Long before people talked about “platforms” or “digital transformation,” Detroit was solving a harder problem: how to coordinate thousands of moving parts with precision. Assembly lines, supplier networks, logistics routes—these weren’t just operations. They were carefully designed systems, built to be reliable under pressure.
If one part failed, everything felt it.
That’s the thing about infrastructure. You don’t notice it when it works. You only notice it when it breaks.
When Tools Quietly Become Foundations
For most of the last century, Detroit’s infrastructure was physical: steel, rubber, glass, and concrete. You could see it, touch it, and walk through it. And because of that, companies treated it with the seriousness it deserved. You didn’t “launch” a factory and move on. You maintained it. You improved it. You designed it to last.
Somewhere along the way, software entered the picture. At first, it looked like a tool. Something to support the real work. A layer on top of the business, not the foundation beneath it.
So companies treated it accordingly. They scoped projects. Built systems. Shipped them. Then turned their attention elsewhere. But software doesn’t stay in the background for long.
It spreads.
It starts by solving a small problem. Then another. Then another. Over time, more people depend on it. More workflows rely on it. More decisions are made because of it. What began as a tool quietly becomes the system everything else runs on.
And yet, the mindset often doesn’t change. We continue to treat infrastructure like a project.
This is where the tension begins. Because infrastructure behaves differently.
It accumulates complexity. It demands maintenance. It shapes what an organization can and cannot do. When it’s thoughtfully designed, it creates leverage. When it isn’t, it creates friction.
The Domino’s Lesson
One of the clearest examples of this shift didn’t come from a technology company. It came from Domino’s Pizza.
At some point, Domino’s faced a question that most companies eventually encounter: What business are we really in?
The obvious answer was pizza. The more accurate answer was systems.
Domino’s didn’t win by making better pizza alone. It won by rethinking how the entire operation worked. Ordering, routing, delivery, store coordination—these weren’t separate functions. They were parts of a system that could be redesigned.
So Domino’s made a different kind of investment. They invested in software. Not as a feature. Not as a side project. As infrastructure.
They built systems that allowed customers to order seamlessly, stores to operate efficiently, and drivers to move with precision. They connected the front-end experience to the back-end operation in real time. Over time, the [majority of their orders became digital](https://www.businessinsider.com/dominos-is-a-tech-company-2016-9)—not because customers were told to change, but because the system made it easier.
The pizza didn’t change dramatically. The system did.
And when the system improved, everything around it improved.
Detroit’s Quiet Shift
This is the quiet shift happening across Detroit right now.
The industries that built the city—automotive, manufacturing, healthcare, logistics—are being reshaped by software. Not replaced by it. Reconfigured by it. Vehicles are becoming software-defined. Factories are becoming data-driven. Care delivery is becoming digitally coordinated.
The work is still physical. But the infrastructure that enables it is increasingly digital.
Detroit doesn’t need to become something new to understand this shift. It already has the mindset. It knows what it means to build systems that matter.
The question now is whether we’re willing to treat software with the same level of seriousness we once reserved for steel and concrete. That’s because the organizations that do will have something others don’t: not just better technology, but better infrastructure.
And infrastructure, more than almost anything else, determines what’s possible.