The Real Cost of Doing Nothing
Don’t buy tools. Build capabilities.
I know that sounds like something people say in strategy meetings right before showing a four-box framework, but I mean it in a much more practical, drywall-dust-on-your-shirt kind of way.
When we bought our house, it was already more than 25 years old. Great house. Not exactly designed for the modern tech era. The walls did not care about smart home panels, cameras, distributed audio, networking gear, Wi-Fi access points, or whatever other nonsense I was inevitably going to convince myself was “necessary.”
We were repainting anyway, which meant the walls were already going to get abused. So I made the decision that still sounds a little ridiculous when I say it out loud: we ran thousands of feet of cable through the house. Ethernet. Speaker wire. Coax. Yes, coax. That felt reasonable at the time, and now it sounds like I was preparing for a 2006 Best Buy showroom. But we did it because the walls were open, the mess was already happening, and it was the cheapest moment to make the house more adaptable later.
The funny part is we only used maybe 20% of it at first. Maybe less? A lot of those wires just sat there behind the walls doing absolutely nothing. No blinking lights. No cool automation. No immediate payoff. Just capped wires sitting quietly in places future-me hoped would someday matter.
And future-me was right. We just did another round of smart home upgrades. New cameras. More speakers. A few touch panels. Upgraded networking. Things we did not fully know we would want years ago. And this time, we did not have to tear the place apart. No new drywall chaos. No fishing wire through mystery wall cavities. No “well, this should have been done before we painted.” The infrastructure was already there. Past-me, despite many other questionable decisions, had apparently done one thing right.
That is exactly how I think about industrial digital infrastructure.
The Use Case Might Be the Mess You Already Have
A lot of companies want the exciting thing first. AI. Predictive maintenance. Autonomous operations. Better dashboards. Digital twins. Customer visibility. Faster decisions. I get it. Nobody wants to stand in front of the leadership team and say, “Good news, we are investing in the stuff behind the walls.”
But the stuff behind the walls decides what is possible later. If your plant data is incomplete, delayed, or not trusted, AI becomes an expensive guessing machine. If your systems cannot talk without custom work every time, every new initiative starts with integration pain. If your network was not designed for what you are now asking it to carry, you are not being innovative. You are overloading old assumptions.
This is where companies get stuck. They ask for the use case before investing in the foundation. I understand the instinct. Nobody wants to spend money based on vague potential. But sometimes the use case is not some beautiful future scenario. Sometimes the use case is the current mess. The manual reports. The duplicated data. The production number nobody fully trusts. The cybersecurity gaps that only become urgent during an audit. The pilot that worked in a controlled setting and then got mauled by the real operating environment. The “temporary” workaround that has survived longer than three org charts.
That is not background noise. That is evidence. If you are still waiting for a clear use case to justify the investment, your indecision is the use case. Not because every infrastructure investment is automatically smart. It is not. You can absolutely overbuild, overspend, and create complexity with impressive confidence. But there is a point where the lack of foundation becomes the thing actively limiting the business. When that happens, asking for a perfect use case can become a polite way to keep tolerating the same constraints.
The Cost of Doing Nothing Has a Weird Billing System
Doing nothing usually looks cheaper because the invoice is scattered. It shows up in engineering time. Operations time. IT time. Supplier delays. Rework. Meetings. Reconciliation. Custom integration. Production investigations that take too long because the data trail is bad. Leaders making decisions with numbers that everyone sort of trusts, but not enough to stop arguing about them.
That is the tricky part. Bad foundations do not always fail loudly. They just make everything take longer. They make good ideas heavier. They turn scaling into a negotiation with old decisions. This is why the quote matters: if you are not investing in your digital foundation today, you are budgeting for irrelevance tomorrow.
I do not read that as a dramatic warning. I read it as a very practical one. Companies rarely become irrelevant in one cinematic moment. They drift there through a thousand small frictions. A customer wants visibility you cannot provide. A competitor launches faster because their systems are easier to extend. A regulation exposes how patched together the environment really is. An AI initiative gets delayed because the data needs six months of cleanup before anyone can trust it.
And then someone says, “We should have handled this earlier.” Yes. That is usually how foundations work.
Back to the house. If I had evaluated those wires based only on what I used in year one, it would have looked wasteful. But that was the wrong measurement. The value was not utilization on day one. The value was optionality without future demolition. It gave me cheaper choices later. That is what industrial companies need to get better at calculating. Not fantasy value. Not “someday AI magic.” Real optionality. Faster deployment. Less rework. Fewer custom fixes. More trusted data. Lower integration pain. Less drama every time the business wants to do something new.
Apparently I have become the dad of digital transformation, and yes, I find that funnier than I probably should. But I am embracing it, because somebody has to remind everyone that the best time to run the wires is before you need the camera.
