Anyone who works around technology long enough eventually learns something that surprises a lot of people.
Most technology problems are not actually technology problems. They’re people problems.
That might sound strange coming from someone who spends a large portion of his time working with complex systems – audio processing platforms, network infrastructure, cameras, automation systems, and the layers of software that tie all of it together.
On paper, those systems are complicated. Thousands of components. Endless configuration options. Enough variables to make even experienced engineers scratch their heads.
But after working around these systems for years, I’ve noticed a pattern.
When something breaks, fails, or doesn’t perform the way it should, the root cause is rarely the technology itself.
It’s almost always something upstream.
A missed detail in communication.
An assumption someone made that turned out not to be true.
A decision made without all the information.
Or sometimes simply a lack of clear ownership over who was responsible for what.
Technology is actually very logical. It does exactly what it’s told to do.
The problem is that people aren’t always as logical as the systems we build.
⸻
The System Is Doing Exactly What It Was Told
Not long ago we were working on an integration project that involved several different pieces of equipment communicating across a network.
On the surface, the problem looked like a technical failure. Devices weren’t communicating properly, data wasn’t flowing where it was supposed to go, and several parts of the system simply weren’t behaving the way the design said they should have.
At first glance, it felt like a classic engineering problem.
Maybe bad firmware.
Maybe a configuration error.
Maybe even a hardware fault.
But after digging into it, the real issue turned out to be something much simpler.
Two different people had made reasonable assumptions about how the system would be configured. The problem was – the assumptions didn’t match.
No hardware had failed.
No software had crashed.
The system was doing exactly what it had been configured to do.
The breakdown happened in the human layer.
Once the communication gap was fixed, the technology immediately began working the way it was supposed to.
⸻
Extreme Ownership
One of the principles from the book Extreme Ownership that stuck with me is this:
“There are no bad teams, only bad leaders.”
At first that statement can feel a little harsh. But the longer you lead teams or manage complex systems, the more truth you begin to see in it.
When something goes wrong, the easiest reaction is to blame the technology.
The server failed.
The network was slow.
The software had a bug.
But strong leaders learn to look deeper.
What instructions were given?
What assumptions were made?
Was the mission clearly understood by everyone involved?
Another line from the book puts it even more directly:
“The leader must own everything in his or her world.”
That principle applies just as much to technology as it does to combat leadership or business operations.
If a system fails because someone misunderstood the design, that’s a leadership problem.
If two people built their parts of a system based on different assumptions, that’s a leadership problem.
If no one was clearly responsible for a critical part of the implementation, that’s a leadership problem.
The technology simply reveals what was already broken in communication.
⸻
Technology Amplifies Leadership
Technology has a way of acting like a magnifying glass. It doesn’t hide weaknesses in leadership, planning, or communication.
It amplifies them.
If a team communicates clearly, plans well, and takes ownership of their responsibilities, the technology tends to run smoothly.
But when communication breaks down, when roles are unclear, or when checkpoints and accountability is missing, the technology becomes the place where those problems show up.
Servers crash.
Networks slow down.
Systems fail in ways that seem mysterious until you trace the issue back to the decisions that were made long before the first cable was ever plugged in.
As Extreme Ownership teaches:
“Simple, clear, concise orders.”
That principle is just as true in a network architecture diagram as it is on a battlefield.
Complex systems demand clarity.
⸻
Leadership First, Technology Second
One of the lessons I’ve come to believe more strongly over time is that good technology organizations aren’t built primarily on technical brilliance.
They’re built on clear leadership.
You can buy the best hardware. You can install the most advanced software. You can design a beautiful technical architecture. But if the people involved aren’t communicating well, taking ownership of their work, and paying attention to details, even the best technology will struggle.
On the other hand, when you have a team that communicates well, takes responsibility seriously, and approaches problems with humility and a deep desire to learn, even imperfect systems tend to work remarkably well.
⸻
The Principle Beyond Technology
What’s interesting is that this idea extends far beyond technology.
Many problems we encounter in life look like surface-level issues.
Financial problems.
Organizational problems.
Relationship problems.
But when you dig down far enough, the real issue is often the same thing.
Miscommunication.
Lack of clarity.
Avoidance of responsibility.
Or sometimes simply the unwillingness to address the root cause of a problem instead of treating the symptoms. You should read that line again.
Technology just happens to expose those issues faster.
⸻
Final Thought
Technology gets blamed for a lot of things.
But more often than not, the technology is doing exactly what it was designed to do.
The real question is whether the people behind it are doing the same.
As the principle of Extreme Ownership reminds us:
When something goes wrong, the first place to look is not the equipment.
It’s the mirror.
We’ll talk more soon.
~NG
