Sakai, Blackboard and Moodle

Yesterday at Educause I was one of three panelists in a “Point/Counterpoint” session entitled “Blackboard, Moodle and Sakai.” The session was completely overcrowded. There were probably 400 people in the room 20 minutes before the scheduled start time, many others who were trying to watch on a TV screen outside the room and many others that gave up and did something else. Luckily it was recorded so you can watch the session online. And you can view the slides we used to structure the conversation.

The interest in the session shows that a large proportion of universities are thinking about what system will best meet their needs. So expect to see lots of change in the coming years. Interestingly, John Norman of Cambridge posted great advice about choosing a system on the Sakai email lists at about the same time the session was going on (he’s not at Educause this year):

The [feature & function checklist] approach to purchasing decisions is widely used because it gives the appearance of objectivity and is relatively easy and low-cost to operate.

In my personal opinion, this is a naive approach to purchasing that explains a great deal of the subsequent unhappiness in large IT deployments. Much information is lost in mapping to the ‘feature boxes’ and the boxes themselves are often defined from a base of a particular implementation.

Given the cost of adoption, and the later costs of switching if the wrong choice is made (or the cost of trying to justify the decision that _was_ made), the value of investing in the process of selection cannot be under-estimated.

I genuinely believe that there is tremendous value in identifying these technology-neutral faculty (and student) goals and then dispassionately (and ideally with users) assessing how readily the product facilitates those goals, and that this is the right approach to making a choice. Unfortunately, the process can take time and investment and can be challenged as open to subjective analysis. The good news is that the subjective analysis may be the way in which institutional culture is allowing into the decision and much of the investment in investigation will be valuable and reusable when you come to deploying the chosen system.

So if you’re looking to change, take your time and ask the right questions. All of these systems will meet the functional checklist over time (and I’d like to mention Desire2Learn, who was not represented on the panel). This is a long-term decision about a core mission of the university and should reflect the values of your institution.

One final note about our Educause session. It didn’t produce the fireworks that some people may hoped for. We chose to take a more reasoned tone for a variety of reasons. We, as panelists, didn’t know each other well and we didn’t want to seem to be fighting with each other personally. Also, because Moodle and Blackboard were represented by implementing universities (respectively Melody Childs of LSU and Dave Swarts of American), I certainly didn’t want to put them in a position of having to defend products/communities that they don’t work in on a day to day basis. But really, at the end of the day, while a verbal “fight” is more entertaining, all three of us wanted to generate more light than heat. We hope you find it helpful.


Unicon Market Research Session at Educause

Unicon has been invited to organize a Market Research session at this year’s Educause conference. This is an interesting and innovative program that the conference organizers are piloting this year. As I understand it Unicon is one of three companies invited to participate, the other two being SunGard and Google, so this is a big honor and a big deal for both Unicon and the entire open source community.

I encourage you to attend this session and then head over to the Open Source reception….read on for more information

Continue reading