DIY

It ain't what you do; it's the way you do it

Yet again, support pro Jeff Dray finds that he needs to fix the customer as well as the technology to completely resolve an issue.

The main purpose of my weekly ramblings, apart from the ability to vent my frustrations about life in general, is to allow me to challenge preconceptions and try to take a different look at the way in which people work.

-------------------------------------------------------------------------------------------------------------------

Most support issues aren’t about the technology; we know what that does and what causes it to malfunction. It gets interesting only when people get involved, and thankfully for the weekly blog writer, whenever you think you have seen or heard it all, the wonderful body of people that is the user community will surprise you with a new outlook on a well-known problem.

It has been said before that equipment is fairly easy to deal with; sometimes the customer is harder to fix. Some equipment failures can lead to a loss of confidence, which, although illogical, is quite understandable.

I was on site looking at one of our production machines recently; it was showing real signs of excessive wear and tear. I was surprised, because they have two identical systems that are designed to share the load. The other machine was in perfect working order, but the customer seemed reluctant to shift the work onto it in order to free up the worn machine for some overdue TLC.

This seemed a bit strange, so I asked the operator why this was. It turned out that there had been some previous problems with the machine, and the operators had lost confidence in it, preferring to stick to the one that had always worked well. We had sorted out the problems, and the machine was fine -- it was the customer who needed fixing. I asked if there was any more work to run, just so that I could stress-test the machines.

As luck would have it, they had a mountain of work to process, so I set up both machines and ran them together. After an hour’s solid run, the pile of work was substantially smaller and I was able to show that the untrusted machine worked as well as, if not better than, the favorite. It took a couple more visits to convince them that both machines were sound and ready for use, since which time things have calmed down with that customer.

I can see when a motor or a belt is worn out and needs to be replaced. It is sometimes harder to recognize when the problem has its roots in the human side of the equation. It is very satisfying to identify such cases and get all the issues resolved, not just the technological ones.

Do you sometimes feel that you have to be part technologist and part psychologist while on the job?

4 comments
davidt
davidt

For some reason, a couple of higher-ups have it in their head that Patch Tuesday is a killer (I suspect a coincidental problem in their past, before I got here). I mean, it's not like I don't test the updates before rolling them out. So, I have to sneak around to those people and do the updates without their knowledge or consent.....

susanai-22169053899661078984272886566109
susanai-22169053899661078984272886566109

Living in Australia I have already had my 'patch Tuesday'. Everything went fine and fast. I think it's only 'mac' people who fret and spread misinformation about these downloads.

howard48906
howard48906

As An IT support person I understand. What they don't know can hurt you. Most users will only learn what they absolutly must to do thier job. The rest is rumor, superstition and ask IT for help.

HAL 9000
HAL 9000

While M$ has got considerably better over the years they still introduce problems along the way. For instance IE8 let the system Auto Update when IE7 is installed and see what happens. :D In the not so far past it wasn't uncommon for the Auto Update to run and then things would stop working. A month ago I got a WGA warning that my copy of Office 2003 was not Genuine. This is a Volume License Product installed on 15 systems on a Volume License copy of Windows XP Pro. On 3 Systems there isn't an issue and on the rest it is Not Genuine. Same Software Same Patch Level and 3 work while the rest don't. Then try ringing M$ for a solution and when they hear that it is installed on 15 machines they immediately scream Piracy even though you told them that it's a Volume License Product. They have selective listening abilities. The only answer that I have got is that I have an Old Copy of XP Pro and it's a Volume License Product. Well I never would have guessed and I do not see any reason to replace every install in the place because M$ would like some more money out of me. Individually both products work fine but add them together and most times you'll get a Error Message demanding that you buy something more from M$ to use one or the other. But there are no problems with M$ Hot Fixes are there? That is only the past couple of months and look at the problems that have been brought about there. :^0 Col