We like to dress up our failures in fancy words. We talk about "complex IT architecture" or "lack of digital maturity."
Let us be brutally honest. Most strategic failures are not due to technology or bad luck. They are due to intellectual laziness.
We are biologically coded for the path of least resistance. We expect a vendor to step up, solve the problem, and carry the risk. As long as we get to stay in the driver's seat and cash the bonus.
After 19 years at the intersection of machine code and human architecture, I see the pattern clearly. Technical obstacles account for 14% of the friction. The remaining 86% is pure human friction. Leadership gaps. Strategic cowardice. And the fear of actually getting one's hands dirty in the details.
When laziness leads to prison Do you want to see what this laziness costs in reality? Look at The British Post Office Horizon Scandal.
For twenty years, over 700 subpostmasters were wrongly convicted of theft. Lives were shattered. People went to prison. Some took their own lives. The cause on paper? Bugs in the Horizon IT system.
But the catastrophe was not due to the code. It was due to the monumental abdication of leadership.
They delegated their understanding: Management refused to understand how the system actually worked. It was "more comfortable" to trust Fujitsu than to listen to their own staff.
They chose prestige over truth: Admitting the error required mental labor. Blaming "thieving" employees was the lazy way out.
They rented their future and abdicated their responsibility as architects.
The Graveyard of Arrogance Do not think this is just a public sector problem. The corporate graveyard is full of giants who rented their brains and paid the ultimate price.
Lidl's €500 Million Delete Button: The grocery giant spent seven years trying to build a new inventory system with SAP. The leadership refused to adapt their "unique" processes to the standard software. They insisted on customizing everything rather than understanding the architecture. The result? After burning half a billion Euros, they deleted the entire project. Zero value. 100% waste.
The Hershey’s Halloween Nightmare: In 1999, Hershey’s rushed a massive ERP implementation before its busiest season. Leadership ignored the engineers' on-the-ground red flags. The system crashed during Halloween. They couldn't ship $100 million worth of candy. The stock dropped 8% in a single day.
These were not "technical glitches." They were failures of executive curiosity.
Shadow IT: The proof of your absence We see the same pattern in your organization. Just on a smaller scale. We call it "Shadow IT."
When you see your employees bypassing your official systems or using their own ChatGPT solutions in secret, it is not "innovation." It is Survival Mode.
They have given up on you solving the problem. They are building their own lifeboats because you are not steering the ship.
If you, as a leader, respond with bans rather than fixing the foundation, you are just a passenger hoping the ship does not sink on your watch.
3 steps to stop being a passenger Do you feel like you are nodding a little too much now? Here is how you take back the pen.
1. Apply the 10% Rule (Stop renting your brain) Never outsource the first 10% of thinking. If you cannot explain the architecture behind a decision on a napkin, you are too lazy to lead it.
"If the consultants draw your map they own your destination."
2. Conduct a "Friction Audit" Where do you see Shadow IT? Instead of punishing those who go their own way, buy them lunch. Ask: "What hole is this shortcut filling for you?" Their "illegal" solutions are the best map of where your system is broken.
3. Kill the phrase "I am not technical" In a digital world saying "I am not technical" is the same as saying "I am not good with numbers" as a CFO. It is not a charming flaw. It is irresponsible. Set aside time to understand the foundation of what you are building. It is boring. It is hard. But it is your job.
The Dividend of Ownership What happens when a leader actually takes the pen? Look at Domino's Pizza.
In 2010, their stock was worth $3. The pizza tasted like cardboard. But CEO Patrick Doyle did not hire a consultant to "fix IT." He declared that Domino's was a tech company that sold pizza.
He and his leadership team took ownership of the digital architecture. They did not outsource the platform. They built it. They removed every barrier between a hungry customer and an order.
The result? By taking ownership of its architecture, Domino's outperformed Google, Amazon, and Apple in stock growth over the next decade.
Ownership pays. Laziness costs.
Conclusion Architecture is not built by algorithms. It is built by leaders who refuse to choose the lazy path.
To "slow down to speed up" is about daring to look into the engine room before it catches fire. Stop expecting someone else to solve your future for you.
Take the pen. Start drawing. Before someone else does it for you.
If you believe a fellow leader needs this data before their next board meeting, forward this briefing. You might just save them from being the next headline.