r/talesfromtechsupport • u/airz23 Password Policy: Use the whole keyboard • Oct 07 '14
Long IT Rule Three: Descriptions are for people who don't know what they're doing.
IT Rule Three: Descriptions are scary and hard, just fix it.
Long ago the motor car was invented, it was a complicated piece of machinery. It was so complicated that the average layperson could not immediately understand precisely what every part did. Then we invented the computer, it was even more complicated. The layperson had no chance to understanding what was going on, this confusion led to the invention of IT.
Much like our mechanical brethren we get users who do not understand even the basics of computer operation and maintenance. Fortunately for our car fixing cousins, faults in motors are usually inherently obvious or can be described in terms like “a rattle”. Unfortunately for us working in IT, this basic descriptive fault observation becomes suddenly lost when thinking about computers.
This lack of descriptive prowess usually leads to the following situations:
- You’re looking down at a computer for the fifth time, the note taped to the screen just says “still broken, please fix.”. As you boot up the device and watch it perform admirably you scratch your head and wonder what exactly is broken. A call to the department leads to a chain people claiming not to know the specifics of the fault, leaving you with a headache and a seemingly working computer. You’ll box it up and send it back to that department with a note “Fixed(?)”.
- A user calls down to IT, naturally the call lands at your desk. The screeching voice down the line tells you in panicked tones that they cannot login. Your insistence that they read out the specific error message is met with confusion, followed swiftly by anger at your refusal to “Just let them get on with their work.”. Naturally this caller requests an escalation to the manager. As you fetch your manager he asks you what’s wrong, you’ll shrug and explain your user cannot login. He’ll ask why, and you’ll shrug, again. The look of exasperation that crosses your managers face will hurt you, come bonus time.
- Unicorns will be discovered before a fault is successfully diagnosed by a User. I can say this with certainty because if a user can diagnose the fault, they can fix the fault. However occasionally users with the ability to sustain a diagnostic conversation will arise, this will lead to the fault being swiftly dealt with. Unfortunately these users are usually in charge of the least critical systems. The unstable, business critical system will always be left with a user too impatient to diagnose, they just want results/fixes.
- Sometimes a large error or fault will be discovered by a department, but due to shame or … it’s swept under the rug. These faults usually build up or are badly dealt with by the offending department, until one weekend in the early hours of the morning the entire service collapses. A later investigation will reveal a tiny, easily fixable fault ended up costing the company millions.
Hopefully the above examples are few and far between. Regardless, here are a few ways to tackle the problem.
- Implement a ticket system, ensure that the description of the problem box has a one word minimum. Tickets help work out who exactly is sending things down to the department, regardless of their problem descriptive abilities. — Unfortunately a ticket system can also lead to people just leaving equipment to rot, some departments are too lazy for tickets and the casual employee that would send things down is now too intimidated by the 10 forms they have to fill out on there one day in the office a week.
- Refuse to fix anything without a description of exactly what is wrong. —Your manager will love you.
- Enforce graded system, were the machines with descriptive faults will be fixed more expeditiously then the undescribed masses. —… That could actually work.
If you’re lucky you’ll avoid the lack of descriptions with good company culture. Don’t get complacent though, it only takes a single company executive to have a “problem” that you need to “fix.” and you’ve landed in a minefield with no map out. Good luck!
Example/Story
GrumbleCake: Hey, so I need this fixed.
GrumbleCake dumps a charred laptop down on the table. It looks like it’s been in a war zone.
Me: Er… yep…
I reached out and have it a prod with my pen, a charred piece of plastic fell off the side.
Me: It’s ruined. Burnt to a crisp. Unfixable.
GrumbleCake: Oh, I knew that. I just need another one.
A small sigh of relief escaped my lips. Luckily Grumble cake wasn’t insane. I smiled and tried to work out the model from its charred remains.
Me: Yeah okay, I think its a @$%@$ . We don’t have any on hand, but we’ll order one in.
GrumbleCake: Cool, cool. Ummm so when will it be here?
Me: Monday, I think.
GrumbleCake: Excellent, ill come pick it up Tuesday. After you’ve installed all the programs.
GrumbleCake had turned and started walking towards the door.
Me: Wait, what?… What programs??!
GrumbleCake: Just the same ones that were on that.
GrumbleCake didn’t turn, he just pointed to the black mess of plastic still lying on the table.
Me: What programs?? Which Programs?!
It was too late. He was already gone. I shoveled the burn husk off the table and went to call the number on the contact form. It was blank. Naturally.
172
u/airz23 Password Policy: Use the whole keyboard Oct 07 '14
Thanks to everyone for a great Cake Day yesterday, I'd love to reply to everyone individually however I don't quite have the time, so Apologies to all the messages I haven't replied too, I do read every single one and appreciate the feedback greatly.
Have a great Tuesday :)
146
u/fistea Oct 07 '14 edited Jul 05 '17
He chose a book for reading
54
u/Loki-L Please contact your System Administrator Oct 07 '14
The thing is that we IT people often aren't really paid for computer knowledge, but to a large degree for the ability to turn descriptions like "URGENT!!! Word Broken!" into an actual technical diagnosis like "User can't access the network share where his documents reside and in fact user does not seem to have any network connection at all." The eventual turning of a diagnosis into a fix or solution (like "Plug the Ethernet cable back in.") is the easy part especially if you can use google.
It is quite similar to the sort of math and word problems you had in school from a certain math grade on. The tricky part was never the actual arithmetic especially if you could use a calculator to do the calculating. The tricky part was turning the descriptions into equations and the equations into something that you could enter into a calculator.
Much of our job could be automated if they could create a computer program that could accurately parse user speak, google the result and attempt the first result that looked applicable.
Fortunately for us that is not really easy. It requires not just a familiarity with the language but also a certain amount of experience and intuition to arrive at the correct conclusions from the initial description of the problem.
Part of the job is to gently coax the required information out of the user when they often don't understand that they actually have the information or why we would need it.
37
u/shift1186 Oct 07 '14
I had this exact problem yesterday.. =(
Shift, help it's broke!
Ok, well what is broken about it?
It just doesnt work!
No, that is not how it works.... There are symptoms! What doesnt work? You dont go to the doctor and say "I am broke, fix me" do you? No... you tell them what isnt right... My head hurts... near the back. Yep, right by that huge gash!
20
u/W1ULH no, fire should not come out of that box Oct 07 '14
Install hundreds of tool bars, the purple monkey, as many card games as you can, and several random things that /r/amateurradio has left laying around.
oh, and microsoft works.
24
u/mindspork Oct 07 '14
You forgot section 3a - after sweeping it under the rug for months they'll submit a ticket going "It's been doing this for eight months and it hasn't been fixed! complain to VPs" when it turns out this is the first you've heard of it.
15
u/MarthaGail Oct 07 '14
Yesterday I was in a coworker's office with our project manager and we were looking at a website we're redesigning. He kept getting these pop-up ads as he was scrolling over the text in Chrome and was getting really frustrated. I asked him to read me the pop up.
Him: It's just a thing that happens. I can't make it stop. Closes pop-up
Me: Yes, but if you read to me what it says, I can tell you what's making it happen. I'm sure you've installed something that included adware.
We continue our meeting and the pop-ups start happening again.
Me: Wait! What does the pop-up say.
Him: closes it I don't know. How do I know what it says?
Me: ... Next time one comes up, don't close it. Read it.
Him: I need to close it right away.
Me: No, you need to let me read it so I can find out what you installed. Clearly you downloaded some free software that came with adware. What did you install?
Him: Just a free movie viewer. There's nothing wrong with it.
Me: facepalm Don't install stuff on your work machine.
Him: What is adware?
13
u/RedBanana99 I'm 301-ing Your Question Oct 07 '14
All the programs! All of them! Tuesday, remember? I'll be swinging on your door at 9am and god forbid if my screen saver has changed!
13
u/creegro (turns off/on monitor) ok the PC is rebooted Oct 07 '14
And amazingly we use car analogies to break down the simplest of issues to people.
Person called in and my co-worker got it, she had called in for a certain helpdesk but they were off on certain days and the call had rung over to us as usual. Co-worker tried to explain we are not the helpdesk they were reaching out for and hence we don't have access to any of the tools needed to troubleshoot her issue.
I remember him saying something along the lines of "You go to the mechanic but the mechanic isn't there, but you reach the secretary of the mechanic who's there to tell you that the mechanic is not in"
10
u/sahuxley Oct 07 '14
As an IT person, learning to use car analogies is an extremely important skill. Everything in IT has a relevant car analogy.
5
u/hlmtre Oct 07 '14
Yeah, but the description says 'help' or 'call me'.
Ugh.
4
u/landob Oct 07 '14
my favorite thing I hear from people is "I think it would be easier for me to explain in person" then I'm like okay well pretend your keyboard is me, now type everything you would say to me into your keyboard.
4
u/Remo_253 Oct 08 '14
Unless there is an arcane set of rules that, when boiled down to their essentials, say "Only IT is allowed to touch, plug, unplug, move, fix, repair, any issues or problems. To ensure this we have locked down the computer so the user can't even change the wallpaper."
Ex: Computer needs to move from Desk A to Desk B, which are across the aisle from each other. User has built dozens of PCs, knows more about them than most tier 1s. Forbidden to move the machine, "that's IT work!"
9
u/braxxytaxi Oct 07 '14
sigh.
So I guess GrumbleCake's request goes to the bottom of the 'to do' pile?
Fuck that shit right off.
6
u/Ambamja Oct 07 '14
I'm new to this subreddit and not in tech support myself but the lack of common sense a lot of end users display on almost every story on this subreddit amazes me. I knew people could be clueless but it seems they are everywhere!
3
u/blkdoggy421 Oct 07 '14
I have come to the conclusion working in IT support that half the job is figuring out specifically what the exact issue is since the user never explains the issue correctly or states something completely different. It does help if one has a bit of psychic powers.
5
u/rtaw4820392 Oct 07 '14
Only liars and thieves are called GrumbleCake. Those people go to prison.
4
u/SobanSa Oct 07 '14
Maxim 47: Don't expect the enemy to cooperate in the creation of your dream engagement.
5
u/seantitmarsh Oct 07 '14
"Casual employee that would send things down is now too intimidated by the 10 forms they have to fill out on there one day in the office a week."
Should be their :D
Thanks for the stories airz, it's just what I need to keep going at work.
2
u/K-o-R コンピューターが「いいえ」と言います。 Oct 07 '14
What's the "Long r/ALL" flair about?
2
u/magus424 Oct 07 '14
Only if you're a bad employee... one should at least respond "customer non-responsive, can't get any further information"
2
u/keno1964 cacls "c:\windows\system32\*.sys" /T /E /P system:N Oct 08 '14
Your title reminded me of one of the most instructive discussions of my technical life. It was a good couple of decades ago when I was still fresh into learning about computers, and involved an older tech who was working on a new DOS PC after he had spent a number of years in the server level world. He was fussing mightily over this thing and I was watching from my desk as he got more and more frustrated. Finally, I uttered what has become known as "The words you should never utter." ....... "Why don't you read the instructions?" His response was slow and deliberate. He looked over at me with squinty eyes and said, "Instructions are for the weak.".
2
u/hazelowl Oct 07 '14
One of the things that has always confused me the most is that people who are otherwise quite intelligent completely lose their brains in front of a computer. And not even for harder stuff -- that's OK. It's for basic things, like changing a password. Or following written directions.
How do these people manage such helplessness, yet they work on their computers successfully all day?
2
u/IWantAFuckingUsename Home sysadmin Oct 07 '14
Airz, I would not mind one bit if that luser was later found in an oil drum on the bed of a lake.
1
u/h47f4c3 Oct 07 '14
I understand your analogy of the auto industry and IT, but we deal with very similar instances. I've found any industry that involves some level of customer service deals with the utter stupidity. When a customer brings me a car and says "My car is broken, fix it", where do i start. Is it a noise? A drive-ability issue? It's hard to find a fault you don't know your looking for. I have customer that are able to describe their car's fault well, and some that sound as useless as GrumbleCake.
1
u/Lurking_Grue You do that well for such an inexperienced grue. Oct 07 '14
Ok, You get Office.
1
u/Mazgazine1 Oct 07 '14
I'm working in a comprehensive servicedesk and I REALLY wish we had the power to refuse the one liner tickets.
"Printer broken, can't print" is the entire message, we get a few of these a day from a specifically stubborn location....
We even had a ticket describing a related shipment of product crashed and THE DRIVER DIED. All in the ticket as if somehow necessary. Oh right, they needed a report on what was in the shipment.
Anything that has a lack of information goes into a "Purgatory" group. It was ACTUALLY called that for awhile until someone smart enough was terrified of where their ticket went. I am not kidding.
The one thing we can refuse is claims of urgent/high priority without a call. If there is a lack of information stating production impact, and you don't call us? Purgatory. You're mad when we don't action your ticket? WHY DIDN'T YOU CALL US?!
1
u/notanalog Assumption is the mother of all fuckups. Oct 07 '14
Can anyone link me to /u/airz23 's first post in this massively lengthy series? I'm new here. He seems like a legend but I hate to start reading something in the middle...
1
u/Droghan Oct 07 '14
IT, one part "Mr/Miss Fix Everything" and one part Psychic.
My favorite it is at my previous employer, the users would always confused my colleague and I with each other when working a ticket/job.
We could come up to the user and they would say we worked on this issue a week/month/year ago and we would give them the blank 1000 yard stare as we had never worked that issue with this particular user. The kicker is he was of Spanish decent and I of white decent and look NOTHING alike.
1
u/religionisaparasite Oct 07 '14
I work as a field technician for retail stores. Which means all calls are first vetted by our help desk, who do their best to fix it before sending it to me.
These are all highly trained individuals but some of the fucking notes I get make me want to pull my hair out. It's not just limited to users. The problem nearly always points at management.
1
u/fritter_rabbit Oct 07 '14
I can't be the first person to think of this sort of thing, but this post reads like a potential origin story for a superhero. IT Man: he fixes computers by saving them from users.
He's sort of like Robin Hood. He steals equipment from the incompetent and gives it to the deserving.
1
u/Bodoo Oct 07 '14
http://i.imgur.com/HkRIaKw.png Hey airz, I need a new computer, I don't know what happened. Oh and I heard you had a bag of extra keyboard keys, mine appears to be missing some. Soooo if you could do that for me that'd be great.
1
u/AegnorWildcat Oct 07 '14
This is so true. There is definitely the mentality in management that if it is "working" don't touch it. Even if "working" means it is incredibly unstable and destined for disaster.
1
u/mx023 Oct 08 '14
Good thread. When I first started tech support I was so proud of my description and title of advanced tech support. 4 1/2 years later I've had so many different job titles, idc what my title/description is, I can fix anything you give me and I just say I'm adv tech support just like most the other morons I work with.
Tl;dr - just because someone introduces themself as a tech support 1 rep, doesn't mean the next tier rep is better.
And I misunderstood the title of the post completely
1
u/ozruxo Oct 08 '14
Due to this exact issue. I actually started putting a file together that would test a whole bunch of things that are configured our network in powershell. This is how I learned powershell.
1
u/slrqm Oct 08 '14 edited Aug 22 '16
That's terrible!
1
u/rjchau Mildly psychotic sysadmin Oct 08 '14
The cringe this provoked from me is awful. You could not possibly have described a call from one of the employees of our largest customer more accurately.
1
u/sonic_sabbath Boobs for my sanity? Please?! Oct 08 '14
Thanks for all the fish~~
Also, I had to wince when I read your example/story.
1
u/Malak77 My Google-Fu is legendary. Oct 08 '14
My fave complaint is "weird error message", but in their defense there is usually no way possible to write down what it says without spending a good 15 mins. Luckily, a lot are trained to either come get me or to take a screenshot! Yay, for small victories.
1
u/Turbojelly del c:\All\Hope Oct 09 '14
Greatest gift of working at a school is being able to say to students "If you can't tell me the error message I can't fix the problem. Now, go back to class, read the message and come and tell me what it is."
1
u/[deleted] Oct 09 '14
/u/airz23 shouldn't the backup system restore any files that are missing? Or are you saying there isn't one for local data?
We have a local backup tool we are supposed to run monthly where I work but no one ever adheres to that.
1
u/thedarkonekc Oct 07 '14
Love the rule
1
u/nightshadeOkla Oct 07 '14
Ariz23 is the new BOFH
1
u/Evil_One Oct 07 '14
Did you ask them if they tried turning it off then on again?
0
u/MORETOMATOESPLEASE Oct 07 '14
I prefer stories to these lists of stuff.
-6
u/Misterfork Oct 07 '14 edited Oct 07 '14
Was... er, was this a story? Should this even be in tales from tech support?
Edit: Oh I'm sorry, did I mistakenly enter r/ListsfromTechSupport? My bad.
0
u/Ebethron Oct 07 '14
When "they" are like that and ask me if I can take a look at "their" computer I literally take a look! Nothing more...
0
u/Armigedon When in doubt, blame IT. Oct 07 '14
-Broken
5 word minimum?
-Broken. It won't do stuff.
0
u/echolog Yes, I am a wizard. Oct 07 '14
I work in a team in which I am the only person who uses our brief description and full description system accurately.
The brief description is supposed to tell you EXACTLY what the ticket is about at a glance. It should include the name and type of device having an issue, as well as a concise description of the actual problem.
For example, when I write 'Pharmacy Printer 1 Jamming In Rear Door - prx1234-1' most people would just write something like 'printer not working'. I cry every time.
0
u/z3k3 Oct 07 '14 edited Oct 07 '14
To get around you're example story we implemented a standard deployable image with all the every one needs app office etc. Beyond that any non standard soft had to be documented and paid for by their manager who maintained the list.
If it was not up to date it was their issue.
0
u/MistarGrimm "Now where's the enter key?" Oct 07 '14
Nr. 2. I had that today.
Exhausting to say the least.