The Computer Isn’t the Problem

Technology is supposed to make life easier. Yet anyone who has stared at a frozen screen, fought with an automated customer-service system, or wondered why two pieces of software refuse to communicate knows how quickly technology can become the problem instead of the solution.

That tension was at the center of my conversation with IT consultant Tim Maile, who has spent more than two decades working with technology in both corporate environments and small businesses. Tim describes his job rather simply: he is the person who stops you from throwing your computer out the window.

But the more we talked, the clearer it became that his work has surprisingly little to do with computers alone.

Tim estimates that roughly 80 percent of what he does involves understanding people: how they work, what they need, what they understand, and sometimes what they refuse to admit they do not understand. The remaining 20 percent is the technical work of configuring systems, fixing problems, improving workflows, and keeping businesses running.

One story illustrated the point especially well. Tim was once hired for what was supposed to be a one-week contract helping transfer data for a company that had gone into administration and was being acquired. He was assured that the company’s system was completely secure.

Within about twenty minutes, using only the access he had been given, Tim was able to produce a complete list of the company’s clients.

That one-week job ultimately lasted nine months.

The deeper he looked, the more problems he found. Information stored by different departments did not match. Addresses were wrong. Names were misspelled. Processes that were supposed to move information from one department to another simply were not happening. The technology was part of the problem, but the larger failure was organizational.

That creates another challenge for anyone working in IT: telling people that the system they are proud of may not work nearly as well as they think it does.

Tim emphasized the importance of tact. Business owners and employees naturally become attached to the processes they have built, particularly when family dynamics, hierarchy, or professional pride are involved. Walking into a company and announcing that everything is wrong is rarely productive. The better approach is to understand the people first and then determine how to communicate what needs to change.

We also discussed automation and the temptation to believe that once a system is automated, people can simply walk away from it. Tim’s experience suggests otherwise. Automation still requires oversight, quality control, and human judgment. Technology can eliminate repetitive work, but it cannot eliminate responsibility.

Perhaps the most useful principle from the conversation was also the simplest: technology should work for you, not the other way around.

Good IT is not about having the newest software or the most complicated system. It is about choosing tools that fit the people using them, reducing unnecessary work, preventing problems before they happen, and making the business easier to operate.

In other words, behind every computer problem there is usually a human being trying to get something done. Understanding that person may be the most important piece of technology expertise of all.