Let me begin by stating I have no bias as to what type of computer people want to use. For me, it’s about people having the right computer to do their jobs and to not have to ask me for support.
With that said, let me share a story of the first day at a new account. A colleague wanted to use his personal Macbook instead of the clients PC. The Macbook had MS Office and could easily connect to the client’s wireless network. The problems all started when the client provided us with a dedicated printer (HP LaserJet) for our use. After downloading drivers, the PC was able to fully able to use the printer while the Mac was unable to connect. This followed with the requirement of MS Project leading to the installation of Windows XP running on the Mac in order to run the application.
What was interesting were the number of people who thought I would be happy about a Mac not being able to perform the functions of a PC. Why do we still feel this way? Unless you are a support organization, what difference does it make?
These feelings stem from corporate PC support organizations. Over 20 years ago corporations began to purchase large numbers of PCs for their employees. Then, one day, someone brought in their Mac from home and wanted to use it in the office. They said it was much more productive for them and we (those providing PC support) were living in the Stone Age. The same thing happened when we selected BlackBerry’s as the corporate standard for PDAs. Within days from the announcement of the iPhone, users were asking why they had to use an antiquated device such as a BlackBerry.
So, why can’t establish desktop/laptop/PDA computing standards that allow multiple devices to be used? Progressive firms are considering allowing employees to “Bring Your Own Technology (BYOT)” to the office. Managing an environment of mixed hardware requires standards, processes, and support training designed to treat problems more in the abstract. The diagnostic process for resolving issues on any platform is the same. The problem is support people don’t follow the process. They tend to be so busy knowing how to solve the technical issue; they lose sight of the problem.
At the same time, I get pretty upset with support personnel who ask me 20 questions in order to understand what I could explain in one sentence. They are following a process in order to deliver a consistent set of information for problem resolution. Maybe I need to be a little more tolerant and practice what I preach.