Every growing business eventually hits the same wall: the systems that got you here won’t get you there. Add enough new tools, new teams, and new customer demands to an org chart built for an earlier stage, and you end up with the corporate equivalent of a house with seven additions and no master plan — a maze of workarounds where nobody remembers why the hallway bends the way it does.
The auto industry is living through its own version of this problem right now, and its solution holds a useful lesson for any leader eyeing a restructure.
For decades, a car’s electronics were built the way a lot of companies build their org charts: one function, one box. A separate computer for the brakes, another for the windows, another for the infotainment system — dozens of isolated units bolted on over time, each with its own wiring, its own software, its own blind spots. It worked, until it didn’t. As vehicles took on more intelligence, that fragmented structure became the bottleneck. Adding one new feature meant touching a dozen disconnected systems, and no single component had visibility into the whole vehicle.
The fix wasn’t more boxes. It was fewer, smarter ones. Automakers are consolidating those scattered functions into centralized “zones” built on a single AI vehicle software platform, giving far fewer systems much broader visibility into the vehicle as a whole. The result is a vehicle that can actually reason about itself as one system, not a committee of parts that never talk to each other.
That’s the part worth stealing for your own org chart.
Redundancy hides in the seams, not the departments
When companies audit for inefficiency, they usually look inside departments — is marketing overstaffed, is engineering too slow. But the real waste often lives in the seams between departments: the handoffs, the duplicate tools, the three different project trackers nobody agreed to consolidate. Just like a car with a dozen disconnected control units, a company with a dozen disconnected functions pays a tax on every interaction between them, whether or not any single team is inefficient on its own.
Rebuilding from the architecture up means asking a different question from “which team needs to shrink.” It means asking which functions should never have been separated in the first place — and which central layer, if you built one, would let the rest of the organization move faster without adding headcount.
Centralize the boring stuff so the interesting stuff can move fast
The industry didn’t centralize vehicle architecture because centralization is elegant. It did it because a unified layer underneath makes it dramatically cheaper and faster to ship anything on top. The same is true in a business. Consolidating the unglamorous, repeatable functions — reporting, procurement, onboarding, compliance checks — into one well-run core frees your best people to spend their time on the parts of the business that actually differentiate you.
The mistake most companies make is treating consolidation as a cost-cutting exercise instead of a speed exercise. The point isn’t to run leaner for its own sake. It’s that a clean, centralized foundation is what lets you add new capabilities in weeks instead of quarters, because you’re no longer routing every change through a dozen systems that were never designed to talk to each other.
Architecture is a leadership decision, not an IT decision
Perhaps the biggest lesson from the shift underway in vehicle design is this: nobody assigned this restructuring to a single department and hoped it would sort itself out. It required leadership to decide, deliberately, what the new foundation should look like before building anything new on top of it.
Growing companies rarely get the luxury of a clean slate, but they do get to choose when to stop patching and start rebuilding. The businesses that make that call early — before the workarounds calcify into “how we’ve always done it” — are the ones that end up able to move fast later, precisely because they slowed down long enough to fix the foundation first.
