Things that annoy you beyond reason...(Vol 5)
Discussion
carguy45 said:
People telling you how to do your job. Especially ones who have absolutely nothing to do with it.
As part of my IT role, I sometimes have to facilitate major presentations for a group of a few hundred people in our office. There was one this week. I sent out some emails about it, scheduled everything, got the equipment ready, tested, all good to go. Figure as per usual I'll head out about 20 mins beforehand and make sure I'm there in case of any issues or queries.
2hrs before it starts, Mr X walks into our office. He's a bit of a weirdo low down the food chain who walks very slowly for no good reason, looks sheepish all the time and is considered a bit creepy by many of his female colleagues. He also talks slowly so even an average conversation can take twice as long as it should. Stands looming over my desk as he always does until I actually raise my head and address him, which he must construe as permission to speak.
"Can I help you?"
"Hmmmm. Just down about the presentation."
"What about it?"
"You're normally .......... out there by now."
"No, I'm not. It doesn't start for 2hrs."
"To get set up, I mean."
"I've already set it up."
"Hmmmm. .................Does it not need tested?"
"I've already tested it."
"Hmmmm.............. No issues then?".
"No."
"Yes. Like I said. And the time is in my email also."
"Aaaah. ..............Sounds like you have it all in hand."
"I do. That's my job."
I get it all the time in my Job, I'm a self employed Handyman, clients phone up and say It will only take 10 mins or 1/2 hr or an Hour.....Really!As part of my IT role, I sometimes have to facilitate major presentations for a group of a few hundred people in our office. There was one this week. I sent out some emails about it, scheduled everything, got the equipment ready, tested, all good to go. Figure as per usual I'll head out about 20 mins beforehand and make sure I'm there in case of any issues or queries.
2hrs before it starts, Mr X walks into our office. He's a bit of a weirdo low down the food chain who walks very slowly for no good reason, looks sheepish all the time and is considered a bit creepy by many of his female colleagues. He also talks slowly so even an average conversation can take twice as long as it should. Stands looming over my desk as he always does until I actually raise my head and address him, which he must construe as permission to speak.
"Can I help you?"
"Hmmmm. Just down about the presentation."
"What about it?"
"You're normally .......... out there by now."
"No, I'm not. It doesn't start for 2hrs."
"To get set up, I mean."
"I've already set it up."
"Hmmmm. .................Does it not need tested?"
"I've already tested it."
"Hmmmm.............. No issues then?".
"No."
- pause*
"Yes. Like I said. And the time is in my email also."
"Aaaah. ..............Sounds like you have it all in hand."
"I do. That's my job."
- silence*
Well it takes me normally an hour to get to my area of work, thats without even getting the tools out the back of the Van!
If they think it only takes 10min to do the job why don't they bloody do it!
People who don't listen. I have a colleague who is a nice enough guy and pretty good at his job, but just won't accept what you tell him. He has to argue about everything. An example. We had to complete an online form where the entry boxes would only accept plain text.
Him: "Can we not put a photo in?"
Me: "No"
Him: "Are you sure?"
Me: "Yes. Only text is accepted"
Him: "Are you sure? Have you tried?"
Me: "No, because I know it's pointless"
Him: "Will you try? The original is a Word document with a photo in it. Can you not cut and paste it into the form?"
Me (getting exasperated): "Stuart, it won't work!"
Him: "Will you show me?"
Me (weakening now): "Okay"
Predictably, it doesn't work. The text appears, but not the photo.
Me: "Right, it doesn't work - as I've been saying for the past 5 minutes"
Him: "Can you convert the document to a pdf and put in in?"
Me: "NO. IT ONLY ACCEPTS TEXT!"
Him: "Would you try?"
Me (feeling my life drain away); "Okay"
Predictably, it doesn't work. Nothing appears.
Him: "That's stupid". And then leaves the room.
Me:
Him: "Can we not put a photo in?"
Me: "No"
Him: "Are you sure?"
Me: "Yes. Only text is accepted"
Him: "Are you sure? Have you tried?"
Me: "No, because I know it's pointless"
Him: "Will you try? The original is a Word document with a photo in it. Can you not cut and paste it into the form?"
Me (getting exasperated): "Stuart, it won't work!"
Him: "Will you show me?"
Me (weakening now): "Okay"
Predictably, it doesn't work. The text appears, but not the photo.
Me: "Right, it doesn't work - as I've been saying for the past 5 minutes"
Him: "Can you convert the document to a pdf and put in in?"
Me: "NO. IT ONLY ACCEPTS TEXT!"
Him: "Would you try?"
Me (feeling my life drain away); "Okay"
Predictably, it doesn't work. Nothing appears.
Him: "That's stupid". And then leaves the room.
Me:
matchmaker said:
People who don't listen. I have a colleague who is a nice enough guy and pretty good at his job, but just won't accept what you tell him. He has to argue about everything. An example. We had to complete an online form where the entry boxes would only accept plain text.
Him: "Can we not put a photo in?"
Me: "No"
Him: "Are you sure?"
Me: "Yes. Only text is accepted"
Him: "Are you sure? Have you tried?"
Me: "No, because I know it's pointless"
Him: "Will you try? The original is a Word document with a photo in it. Can you not cut and paste it into the form?"
Me (getting exasperated): "Stuart, it won't work!"
Him: "Will you show me?"
Me (weakening now): "Okay"
Predictably, it doesn't work. The text appears, but not the photo.
Me: "Right, it doesn't work - as I've been saying for the past 5 minutes"
Him: "Can you convert the document to a pdf and put in in?"
Me: "NO. IT ONLY ACCEPTS TEXT!"
Him: "Would you try?"
Me (feeling my life drain away); "Okay"
Predictably, it doesn't work. Nothing appears.
Him: "That's stupid". And then leaves the room.
Me:
By contrast, one of the best testers I ever worked with would try things like that - ie. deliberately try things that no sane person would do. Because users aren't sane. He'd be looking for graceful failure.Him: "Can we not put a photo in?"
Me: "No"
Him: "Are you sure?"
Me: "Yes. Only text is accepted"
Him: "Are you sure? Have you tried?"
Me: "No, because I know it's pointless"
Him: "Will you try? The original is a Word document with a photo in it. Can you not cut and paste it into the form?"
Me (getting exasperated): "Stuart, it won't work!"
Him: "Will you show me?"
Me (weakening now): "Okay"
Predictably, it doesn't work. The text appears, but not the photo.
Me: "Right, it doesn't work - as I've been saying for the past 5 minutes"
Him: "Can you convert the document to a pdf and put in in?"
Me: "NO. IT ONLY ACCEPTS TEXT!"
Him: "Would you try?"
Me (feeling my life drain away); "Okay"
Predictably, it doesn't work. Nothing appears.
Him: "That's stupid". And then leaves the room.
Me:
His defect reports always contained step-by-step instructions on how to reproduce the defect too, with screen shots of any error messages or pop ups.
He really was superb.
Cotty said:
TameRacingDriver said:
People who can't follow basic instructions (seemingly MOST people nowadays).
I work in IT, and look after an entire office on my own. As such, it helps me if some people can help themselves with some of the more basic processes. Hence, I have written instructions for them to follow...
I have a lot of experience producing instructions that are clear and concise.... if you can actually read, there's no way you could get it wrong. They have been thoroughly tested (by me and several others), step by step, plenty of white space etc.... people STILL get it wrong!!!
For fk sake. Why is it so hard for some people to comprehend the most basic of task when the instructions are in front of you and its written in a manner that could be understood by a 3 year old baby?? Or is it that they feel themselves so important that they just can't be bothered to read it properly?!
Ok I have a response for you. Someone created one of those idiot proof guides and before circulating it to a large group of people asked if some volunteers could test it to see if it worked, I was one of those volunteers. Someone sat with me while I followed the instructions, we got stumped trying to install a second email address on my phone as the issued company phone was so basic I could not complete the task required even with the IT person helping me. I work in IT, and look after an entire office on my own. As such, it helps me if some people can help themselves with some of the more basic processes. Hence, I have written instructions for them to follow...
I have a lot of experience producing instructions that are clear and concise.... if you can actually read, there's no way you could get it wrong. They have been thoroughly tested (by me and several others), step by step, plenty of white space etc.... people STILL get it wrong!!!
For fk sake. Why is it so hard for some people to comprehend the most basic of task when the instructions are in front of you and its written in a manner that could be understood by a 3 year old baby?? Or is it that they feel themselves so important that they just can't be bothered to read it properly?!
If you issue a simple instruction like "kick the ball" perhaps check that everyone has a ball to kick first.
SpeckledJim said:
IT bods (and techies in general) are notorious for writing instructions that users can't understand.
Suspicions that they do it on purpose to give them the chance to be all superior and condescending when asked for help are rife!
Not this one, writing instructions and documentation, if I do say so myself, is probably one of my strongest skills. Basically, I put the effort into it, because I don’t want them coming back to bother me. In this case, I literally can’t make it any easier. That said, I’m pretty sure I know for a fact most of them simply can’t be bothered to read or try anything themselves since many of them will wait weeks or even months before trying it. I am quite happy to help if people ask, but some people seemingly don’t even want to do that either! Suspicions that they do it on purpose to give them the chance to be all superior and condescending when asked for help are rife!
I'm particularly keen on Instructions that are really complete step by step in some parts except for one bit
1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
talksthetorque said:
I'm particularly keen on Instructions that are really complete step by step in some parts except for one bit
1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
Sounds like the Mazda factory service manual for the RX7.1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
REMOVAL OF ENGINE
Step 1: Disconnect engine loom
Step 2: Remove transmission bolts A-F
Step 3: Remove engine
talksthetorque said:
I'm particularly keen on Instructions that are really complete step by step in some parts except for one bit
1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
You're assuming that users understand what a terminal window is, or where to find the Windows search bar. Many users use a computer only to do things they've been shown how to do. Any deviation from that leaves them stumped.1. Open a terminal window by typing
cmd
in to the windows search bar and press enter
2. Type in
cd temp
in to the terminal window and press enter
3. Rewire the SCSI Bridge module to reconfigure the flux capacitor so it accept incoming quirkafleegs through North and south portals.
4. Type
run mymumsdogsname.exe
in to the terminal window and press enter
Lots of car drivers are perfectly happy driving from A to B, but if you asked them to check the oil level (even with instructions) they'd be stumped. As well as knowing how to access the dipstick, you need to know that the car needs to be on a level surface, needs to know to wipe the dipstick before taking a measurement, and needs to know to leave the engine for a minute or two after it's been running. They also need to know what is an appropriate reading.
The point I am making is that even basic tasks require a certain amount of background knowledge, without which those basic tasks cannot be carried out successfully, even with what seem like clear instructions.
LunarOne said:
You're assuming that users understand what a terminal window is, or where to find the Windows search bar. Many users use a computer only to do things they've been shown how to do. Any deviation from that leaves them stumped.
Lots of car drivers are perfectly happy driving from A to B, but if you asked them to check the oil level (even with instructions) they'd be stumped. As well as knowing how to access the dipstick, you need to know that the car needs to be on a level surface, needs to know to wipe the dipstick before taking a measurement, and needs to know to leave the engine for a minute or two after it's been running. They also need to know what is an appropriate reading.
The point I am making is that even basic tasks require a certain amount of background knowledge, without which those basic tasks cannot be carried out successfully, even with what seem like clear instructions.
Correct - which is why when I write instructions for end users, I assume that they know absolutely nothing about it, other than how to use a mouse and keyboard. I even describe what the start button is / where it's found and what it looks like (including pictures). It sounds OTT but I would not assume a non technical user would know what a Start button was.... although it was far easier back in the XP and before days when it actually had "START" written on it Speaking of which, I find users are even more confused these days now that interfaces have largely moved towards fairly generic, nondescript icons. Most users find buttons with text on much easier to understand, and I'm surprised its not an option on more things. Things are only going to get worse with phones and their invisible gestures that are going to be de rigour in the next few years!Lots of car drivers are perfectly happy driving from A to B, but if you asked them to check the oil level (even with instructions) they'd be stumped. As well as knowing how to access the dipstick, you need to know that the car needs to be on a level surface, needs to know to wipe the dipstick before taking a measurement, and needs to know to leave the engine for a minute or two after it's been running. They also need to know what is an appropriate reading.
The point I am making is that even basic tasks require a certain amount of background knowledge, without which those basic tasks cannot be carried out successfully, even with what seem like clear instructions.
Edited by TameRacingDriver on Friday 14th June 11:05
Clockwork Cupcake said:
j_4m said:
Sounds like the Mazda factory service manual for the RX7.
REMOVAL OF ENGINE
Step 1: Disconnect engine loom
Step 2: Remove transmission bolts A-F
Step 3: Remove engine
"Refitting is the reverse of the removal instructions" REMOVAL OF ENGINE
Step 1: Disconnect engine loom
Step 2: Remove transmission bolts A-F
Step 3: Remove engine
TameRacingDriver said:
Correct - which is why when I write instructions for end users, I assume that they know absolutely nothing about it, other than how to use a mouse and keyboard. I even describe what the start button is / where it's found and what it looks like (including pictures). It sounds OTT but I would not assume a non technical user would know what a Start button was.... although it was far easier back in the XP and before days when it actually had "START" written on it Speaking of which, I find users are even more confused these days now that interfaces have largely moved towards fairly generic, nondescript icons. Most users find buttons with text on much easier to understand, and I'm surprised its not an option on more things. Things are only going to get worse with phones and their invisible gestures that are going to be de rigour in the next few years!
I find one can never assume too much. I started an IT response one time with "Press the left button on the mous-" only to be interrupted by "What's the mouse?"Edited by TameRacingDriver on Friday 14th June 11:05
In saying that, people are generally much more IT savvy now than when I first got into computers in early 90s. Some older people seemed terrified of them then, now they're more likely to at least use them (or a tablet) for basic internet.
carguy45 said:
I find one can never assume too much. I started an IT response one time with "Press the left button on the mous-" only to be interrupted by "What's the mouse?"
This is the reason my instructions start with the intended audience or a list of assumption. Something along the lines of "This document is intended for IT/1st Line/2nd Line/General Distribution" or "This document assumes the recipient has a basic knowledge of Microsoft Office/has knowledge of basic shell commands/can tie their own shoe laces".You will always find a few that can't tie their own laces, it's why I distrust anyone wearing slip-ons in the office.
fatboy18 said:
get it all the time in my Job, I'm a self employed Handyman, clients phone up and say It will only take 10 mins or 1/2 hr or an Hour.....Really!
Well it takes me normally an hour to get to my area of work, thats without even getting the tools out the back of the Van!
If they think it only takes 10min to do the job why don't they bloody do it!
One thing that being in IT teaches you is NOT to tell anyone else how to do their job. You get so much crap from end users who think they know better without having the faintest clue what the job entails. Well it takes me normally an hour to get to my area of work, thats without even getting the tools out the back of the Van!
If they think it only takes 10min to do the job why don't they bloody do it!
Them: "You just need to plug something it, it's not rocket science"
What I want to tell them: "No I need to plug something in, reconfigure the MFing RADIUS server, create a new zone on the Wifi Controller and do all of this whilst not breaking anything else, oh and you want it done in business hours too".
Or worse, them: "My brother's, cousin's, nephew's friend who works in IT said that you should do this"
What I want to tell them: "Does your brother's, cousin's, nephew's friend fking work here? No, then shut the fk up because I guarantee their systems are different to ours"
I'm happy to leave my barber to do his job because he knows a lot more about cutting hair than I do. I feel a fair bit of sympathy for tradesmen, mechanics et al. because we "IT bods" also get asked by random friends of friends to do all and sundry but at least tradesmen and mechanics have an expectation of payment/compensation... people expect us to do free work because we "like computers".
Gassing Station | The Lounge | Top of Page | What's New | My Stuff