Interesting Paradox - Choices

Gladwell - TED Talk - Malcolm Gladwell talks about providing choices that people don't even know that they want.





Barry Schwartz takes aim at a central belief of western societies: that freedom of choice leads to personal happiness. In Schwartz's estimation, all that choice is making us miserable. We set unreasonably high expectations, question our choices before we even make them, and blame our failures entirely on ourselves. His relatable examples, from consumer products (jeans, TVs, salad dressings) to lifestyle choices (where to live, what job to take, whom and when to marry), underscore this central point: Too many choices undermine happiness.

Understanding eLearning 2.0

My article - Understanding eLearning 2.0 - was just published on ASTD's Learning Circuits.

I would like to thank readers of this blog for helping with contributions. As I said in the article:

Thanks

This article would not have been possible without considerable discussion and input from many different people who have taken part in discussion around this topic via the blogosphere. For example, in the discussion on the blog post, "e-learning 1.0 vs. 2.0 - Help Needed," you can see that Howard Cronin provided the analogy of AM/FM, CD, and iPod adaptor. Thanks, and I look forward to the continued conversation.

Aide RSS Filtering Tool

AideRSS looks at a variety of sources of information including comments, technorati, bloglines, icerocket and del.icio.us to determine what posts are generating the most interest. It provides a widget that allows you to show your top posts for month or year. You can see what it thinks are mine in the right column of the blog.

I've been creating similar information manually for a while, so it's nice to have an automated support for it.

I've not quite figured out how to take a very large list of blogs, e.g., all edublogs, and have it filter those down. It imports OPML, but the interface didn't seem intuitive. I'll let you know if that works later.

Change Your RSS Feed?

A while ago, I created a feedburner feed for this blog so I could add lots of stuff to the feed - most importantly I publish a daily summary of my new del.icio.us links. It appears that most people still point to my Blogspot feed.

I would suggest that readers of this blog might want to change over to the FeedBurner feed to get this added functionality: http://feeds.feedburner.com/eLearningTechnology

How Wikipedia Works and Wikis in the Enterprise - HBS

Great article - How Wikipedia Works (or Doesn't) that looks at Andrew McAfee's experiences around the "Enterprise 2.0" article and Wikipedia's Articles for Deletion process. It's an interesting discussion of the net impact of Wikipedia's process - which can be frustrating, especially to casual users. At the same time, I've also had some very good experiences such as when my 10-year old son updated Wikipedia.

At the bottom of the article, the author interviews Andrew about the use of Wikis in the enterprise. A couple of things jumped out at me:

Sean Silverthorne: Is Wikipedia a good model that transfers to a corporate environment?

Andy McAfee: No is the short answer here, simply because (a) how valuable is the corporate encyclopedia, and (b) how much enthusiasm or incentive do we have to contribute to the corporate encyclopedia? But an encyclopedia is only one of the things you can build with wiki technology.

This is a somewhat strange answer. In my experience, Wikis often start (and sometimes end) as an easier-to-use replacement for simple web publishing (an intranet that's easy-to-edit). For example, you have a bunch of resources that get shared and you want to put them up. Or you have a set of reference pages. The old way would be to work with your IT staff's content management system or to hand-craft web pages and go through a painful posting process. The new way is to use a Wiki and just click the edit button. Often, you don't really expect end-users to edit the pages when you start out. Sometimes, they end up editing them, sometimes they don't. But it is still easier. My strong belief is that:

Anytime you think about creating a web page, you should probably think whether it wouldn't be better to make it a Wiki.

The article later discusses:

Silverthorne: Have you used wikis yourself?

McAfee: I can give you a couple of examples because I try to use wikis in a fair amount of my own work. I was organizing a 40-person conference of academics and needed to take care of all these administrative tasks that I really hate doing, like putting the schedule together. And I thought, "Ding, I'm going to outsource this to the people who are coming to the conference." So I put up a couple of initial wiki pages and e-mailed them to everyone. I said, "Here is the bare -bones schedule. You guys tell each other and tell all of us what you think we should do in each of these slots, and if you want to present in one of these 4 daily slots, just add your name to the list." And with very little pushback, the Web site for the conference self-assembled, and most people were quite happy with it. The amount of overhead went through the floor.

I also use them in my MBA course Managing in the Information Age. I tell my students that about half their grade will be based on wiki contributions. So I solve the incentive problem that way. And then I have to deal with all the problems of, "Well, what do you want us to do?" ("I'm not telling you.")

A couple of great examples. Both are uses in smaller workgroups which is probably an early place to look for adoption. I've similarly used Wikis in conjunction with a class environment, and it's quite natural, especially if you have collaborative exercises defined for the students.