How Do You Explain Computer Concepts to Non-Tech Types?

by Chris Foley on December 11, 2009

confusedThis is a great question, and to be fair, is the story of my (professional) life.  I found this article on LifeHacker.com.

I’d love to hear your ideas and stories.  Who knows, your comment my wind up in the book I’m writing on exactly this topic.

Enjoy!

If you’ve ever been called on to diagnose, fix, upgrade, or shop for a new computer, you know that hardware and software features can be hard to convey in plain English. We’re searching for the best non-geek explanations you’ve heard.

In response to the How-To Geek’s roundup of explanations at the Q&A tech forum Super User, reader Allan sent in this explanation of computer basics he’d heard a sales person use while helping a couple pick out a computer for their grandchild:

He used the library analogy: The hard drive size was compared to the amount of shelving for books. The CPU speed was the librarian’s quickness on his/her feet (this was a full service library), and the RAM was the size of the table at which one sat. Larger table meant more books could be opened simultaneously. When the table had been covered with books, each time a new book was to be opened, one from the table would have to be closed (pagefile). The last part seemed superfluous in this scenario, but the overall description, with a few stated benchmarks and questions about the grandchild’s habits, seemed a much better than average sales transaction.

That’s pretty clean and simple, and a good variation on the “desk covered with folders and files” metaphor I can recall from my early school days.

Now it’s your turn: How would you explain why Firefox or Google Chrome are so much better than Internet Explorer, if you’d already covered the security angle? Why do 64-bit processors and operating systems matter to the average user? Let’s hear the best explanations you’ve used, or received from others, in the comments.

Check out the comments people left on the original article HERE at LifeHacker.com.

Author Credit: Keven Purdy

Share and Enjoy:
  • Print
  • email
  • Reddit
  • Tumblr
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • StumbleUpon
  • Digg
  • Twitter
  • Facebook
  • Posterous
blog comments powered by Disqus

Previous post:

Next post: