>Most people will do this for anything but computers, though, which is weird. If their favorite road to the CHEZBURGER store is closed, they will find another road. But if it happens online... panic, frozen.
I think you overestimate people's ability to find different models for things in their life. Their ingrained model just happens to have a fall-back plan, but outside of that most people simple aren't problem solvers. But I agree that it's particularly bad when dealing with anything electronic.
One thing that I have to keep telling myself is that most of my world, the stuff I do, the people I interact with regularly, etc., is a world composed almost entirely of people, tools, philosophy and mechanisms steeped in the mystique of "problem solving". Whenever I get out of that world, I'm usually mystified at how generally people run into very simple real life problems they can't seem to surmount.
The second is that half the human population gets by with an IQ under 100. (I also use this to motivate myself).
> Skilled computer users, on the other hand, don't let a failing model bother them. They just try something else.
I like this analogy, problem solving then seems to be the ability to quickly craft and test mental models against a situation till one of them provides a good enough estimate to describe with the situation. This is actually a powerful way of thinking about problem solving. Once you think of building models, a whole host of new cognitive tools become available.
Anecdote: I worked with a guy with a background in business, educated at absolutely the top schools, MBA, the works. He spent his formative working years selling a shrink-wrapped product that had no support tail whatsoever. There was no execution part of a client engagement outside of ensuring proper delivery of the product. Later he found himself in a different company, with me as a sales engineer, selling a very high touch product - every sale had to have a support tail (it seems onerous, but is a great opportunity to build a strong relationship with the customer).Yet he kept acting like he was still selling the previous kind of product.
After a couple years of this, and seeing lots of missed opportunity because he simply didn't get the "client relationship building and execution" part of the business (so getting follow on sales, or expanding business with a previous client was very challenging) I finally lamented to our mutual boss...he, an engineer by training, but since then with decades of experience in highly successful businesses, told me, "you simply can't project your problem solving mindset onto him. You see the client engagement issue as a problem to be solved, and it agitates you like a nervous tick that has to be scratched. I've worked with many many people like this, business trained types, and problem solving doesn't run in their blood, they think of the world in terms of how to extract money from it."
I responded, "but I'm interested in making money as well".
He responded, correctly, "wrong, you are interested in solving the problem of making money, money is a secondary motivation."
I tell her "the plugs will only fit one way round into the correct sockets, you literally can't go wrong".
She calls me back, saying that her mouse isn't working.
I go over and take a look. She'd forced the USB connector on her mouse into an Ethernet socket with such force that she cracked the network card.
The lesson? Elderly women are strong.
The lesson? I need to learn to write some people off as jackasses not worth dealing with. (My grandmother, on the other hand, is pretty cool. If she needs cables plugged in, I'll happily help.)
The lesson? ???
A lot of people learn to use computers by memorizing a sequence of steps which, if followed exactly, will produce the right result. To send an email, first double-click on the "internet", then click "bookmarks", then "send an email", then press "compose", then type the email address of the recipient into the field, and so on. This is a very brittle kind of knowledge, and if the computer goes off-script, people who've been trained to interact with computers this way tend to just fail, hard.
I'm not sure what the answer to this is, because for most of these people, learning how to figure things out on a computer would be a lot of work for not much immediate gain.
Maybe the problem will go away on its own. How many younger people read the manual for their cell phones, or a video game? And yet they figure it out anyway, by exploring.
I agree, this seems to be a problem I notice far more intrinsic to older generations.
I'm going to give another anecdote (I'm full of them today, see my other post in this subject): I once worked a very interesting job where we staffed people who traveled with an extremely sophisticated technology package into a workspace, and literally "embedded" as a super-user of the package, who acted as the user-lead for the package, and got the rest of the users up to speed by solving real world problems. There were literally dozens of components, pieces of software, data sources, etc. The data flow graph of the system covered a wall when printed out on a plotter.
Between cycles acting as a super user, we'd rotate on a cycle of training new hires (about an 8 week training cycle) to do this job. Intrinsically it was a problem solving job. You'd go to a site with the package, and when the users had problems, you'd craft a solution. Over time, you'd more or less build a work book of solutions to most of the common issues that particular user team would see.
From time to time we'd end up with an "older" person filling that position and going through training. I ended up on a couple of the training rotations with these folks, all great guys, but simply unable to put together a solution to very simple problems. To the person, every one of them asked us to build out a procedure manual covering all these various problem solving exercises.
Let me repeat that, they wanted to field novel problem solving questions by looking them up in a procedure manual for the appropriate solution. We're talking about a system with dozens of components, each of which with an operating manual the size of a phone book, and an 8 week training course covering thousands of slides, dozens of exercises, review, scoring, scenarios, private discussion etc. If a procedure manual could have existed for every conceivable problem scenario, it would have been tens upon tens of thousands of pages.
They simply couldn't fathom not having a procedure manual. And to the man, they left shortly after ending up in their field assignments because they "couldn't solve any problems and didn't have a procedure manual". Other than being a terrible waste of everybody's time, it was a repeatable pattern time and time again. Whenever we hired somebody over about 50, they always seemed to fall back in the need for procedures.
And as you've said, that's a terribly brittle kind of knowledge.
Or sometimes people see an unfamiliar UI, think "ugh---yet another drain on my time to figure this out", consider the value of what they are trying to do, and may decide it's not worth it. This is why I largely stopped using MS Office when the "ribbon" debuted. It seemed to me to be an arbitrary change to something that had been long familiar, and I decided "I really don't need Office anyway" and stopped using it.
I think the reason for this is that computers are too easy to stuff up. You see this when you go to fix someones computer, and you have no idea how they got it into that state. They can not describe how they did it.
This is why so many people love the iPad, you can not screw it up (at least, it is a lot harder).
I'm not so sure about that. A majority of people (no data, sorry) confronted by danger or an accident will panic or freeze. People can have extensive familiarity with physical tools but be blind or even reject nonstandard configurations or uses when first proposed.
There are complex problems I can solve in my head and simple ones that make me go stupid; my wife is way faster at abstracting information from a 2d layout like a videogame or a map, I'm much better with 3d or data with multiple overlapping layers. So she kills me at Tetris, Scrabble and reading transit maps, whereas for me Space Giraffe, wire puzzles and tree scheduling come easy. She likes LISPs, I like assembler, and so on.
I don't get it either. The only reason I can think of is maybe it's more interesting because it's less natural? She claims not to like geometry much either, which just baffles me.
a) they've been burned before, and broken something or lost data
These people need to be untaught that you can break computers, which is much harder. As is writing fault-tolerant software and humane interfaces.
b) mental models are abstractions, and there seem to be a large number of people who just don't cope with abstraction very well.
I'm hopeful that touch-based computing will help some of these people by eliminating a layer of abstraction from systems that already have too many.
Then I printed this out and put it next to the computer. http://xkcd.com/627/
I do think that the blue screen of death and similar things of the past have created this idea of the possibility of catastrophic failure on a computer and it is important to make the users feel more confident that their actions will not cause any irreparable damage.
I bought my Dad (74) one this year, as his first "computer", and the first thing I told him was not to worry because he couldn't break it by doing the wrong thing. Now he's sending email and playing Words with Friends. It's been transformative for him, and I believe his acclimation has been made possible mostly by the software's resilience to mistakes.
Thank you for this. It seems so obvious now, but this wonderfully captures something about the iDevices I couldn't quite put my thumb on...I think I need to go and do some deep meditating on this.
The issue here is not so much that people need to be taught they can't break computers, but what the map of states is. On the other hand, if they don't even want to learn that... well, then I'm not sure what the (software-side) answer is.
Because lots of apps are linked up (emails can be filed so Document management, which integrates with CMS....) users don't know where the boundaries are. So it's a small wonder that they get scared of the system. And I think that fear reinforces any uncertainty with computers in general.
EDIT: typo
I bet there are a number of Windows users that never update, in fear that it will break something. (To be fair, it might, but usually it's unlikely).
> Skilled computer users, on the other hand, don't let a failing model bother them. They just try something else.
I don't agree with you. The fear of new ideas and places is a human quality, not a consequence or a property of a particular group of people.
I, for example, feel very comfortable learning a new programming language. I feel excited and content when I'm picking up some new language or library -- I can easily hunt through pages and pages of information that does not help me without being deterred in my goal. To phrase it objectively -- it's an environment that's completely foreign and largely without immediate payoff, yet I feel comfortable within it.
In stark contrast to that, I've listened to the same ~20 songs for the last 4 months. I know there are plenty of great songs out there, but I'm happy with what I'm listening to right now. I don't want to explore and find new or neat music -- I'm perfectly happy with what I've got. I know there are countless "unknown unknowns" -- wonderful gems of music just waiting to be discovered -- but I don't want to hunt after them. When I feel comfortable with these 3-4 albums, I'll go look for something else.
I don't think advanced computer users are in any way immune to feeling, at least, uneasy or uncomfortable when exploring a particular set of new ideas or places. It's just a question of what type of things they're comfortable exploring.
I happen to be pretty comfortable with programming, but I am hesitant and uneasy when exploring new music. Why? I don't know. I've come to accept myself as I am. :)
I think at one point she changed the default language to Swahili. It was impressive.
This was more or less true until the internet came along. Now computers are full of booby traps and hungry wolves and the things you do on the screen actually affect the real world. It's not so much that you will break the computer, more like the other way around.
Sorry old coots, you had your chance to practice and you wasted it being stubborn. Now the real game is on and there is nothing us nephews can really do for you.
Skilled computer users, on the other hand, don't let a failing model bother them. They just try something else.
Most people will do this for anything but computers, though, which is weird. If their favorite road to the CHEZBURGER store is closed, they will find another road. But if it happens online... panic, frozen.
People basically need to be taught that you can't break computers. Programmers need to provide better undo functionality, so that this is not a lie.