A common pattern in a lot of frustration with IT systems is the users’ inability to grasp that not all systems were designed by them and how they would like a system to work. In other words, when something doesn’t work they way they would like it to work, they blame the system rather than learning how the system works.
“I can’t get Word to X to Y, Word must suck!”
“I can’t get Firefox to do Z, Firefox must suck!”
The reality, however, is that the “I can’t” to them translates to “Someone else should have done this the way I wanted them to do it” and “It’s certainly not my fault I lack the knowledge about this system, after all, I browsed a lot of web pages, just like I want learning this system to work, and I still haven’t got the foggiest about squat, so now the training system is at fault too!”
Then, when someone tells them that they may want to reevaluate their stand because this is a fairly trivial problem to solve, that someone now become the idiot because they suck up to Microsoft, scam people, or have no clue what they are talking about.
At no point during this entire tirade does the original user for a second contemplate that their decades of experience in doing things a certain way may not always work, and that they cannot expect to apply 1:1 the knowledge they already have. Either the system sucks, the training sucks, or the people that understand suck.
Found this article valuable? Want to show your appreciation? Here are some options:
a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.
b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.
c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!