Following up on last week’s notice concerning a significant bug in Blackboard’s “quiz tool,” we are awaiting a patch that is now being tested at institutions using the same system that we are using. Once the patch has been tested and is thought to be successful, we will install it on our servers. Notice will be posted here once the patch is applied.
In the meantime, you might be interested in reading this from the online message boards. It reflects our experience at UT. Comments are welcome:
From: XXXX
Date: September 26, 2011 4:35:44 PM EDT
To:
Subject: Re: Why Blackboard Learn S****s
Reply-To: blkbrd-l – A list for Blackboard course administrators and faculty
I’m a bit late to this thread of discussion, but having almost sent similar messages to this list on a few occasions this opportunity can’t be passed up. My personal, private citizen answers to the question Kevin poses.
1. Blackboard moved to Learn too fast. When Bb first acquired WebCT, the WebCT reps assured us two things would happen: 1) Blackboard wouldn’t leave WebCT customers out to dry – they would combine the best of both worlds. 2) The process for bringing the two systems together would be an orderly one.
They showed us a reasonable roadmap that had three versions of each separate LMS in the future before a single version would come out. That included WebCT 6, which had just been released. By my count, Bb is a version short on that roadmap, Learn 9 having come out instead of the separate versions we were told would be produced but have common APIs to prepare for the eventual merged product. Blackboard should have waited until it had a stable, smoothly operating product that would support as seamless a transition as possible. It feels like someone decided to gamble instead that they could get enough people to switch and commit to make up for dissatisfied customers who dropped the product because it didn’t meet the expectations they set.
Consequently, 9.1 was a rushed response when it turned out that there were far more in the dissatisfied camp than expected.
2. Blackboard pressures WebCT clients too much. Most of us in the WebCT world were used to WebCT telling us we needed to get on the Enterprise version, WebCT 4 wouldn’t be supported much longer, etc. so this isn’t necessarily alien to us. However, Blackboard’s initial assertion as to when the CE support would run out seemed clearly designed to get us on board and committed to a joint product as quickly as possible. The Learn product itself seemed designed more for that end then actually meeting the needs of former WebCT customers (and clearly Learn 9.0 was embarrassing deficient in many of the standard CE features).
The problem with such a strategy is that it gives the game away. It’s pretty standard practice now for software companies to bolster the adaptation of new products by discontinuing support for the older versions. However, most software companies with really good products don’t do this. Why? Because they wait until the new product is stable and improved enough to entice customers to move. If Blackboard Learn were a substantial improvement over the CE product, moving would be a natural transition for customers (especially as the licensing is the same). It may yet become that product, but only because the user community has returned the favor.
3. Not enough end-user focus. Blackboard seems to suffer from a lack of vision about end-users. “How will the product work for the intended audience?” should be a question that every software manufacturer answers comprehensively before a product is released. No one expects a perfect product. Software of this kind is too large and complex to not have some deficiencies. However, customers expect the product to work in ways that make sense and do not require them to recreate work. Too many bugs, and the notorious “work as designed” issues left users with the daunting task of redoing work. I had at least one instructor drop out of our pilot because of the Test question image resource bug. He had well over a hundred questions with images.
The course copy issues were especially daunting. I just about feel out of my chair the first time I copied content from a course, got to the new course, looked in Files and found… nothing.
There are just too many instances where users are left asking the overused catchphrase, “Really?” Instead of rushing a version out and patching it up, Bb needed to commit to more extensive testing and making sure that deal breakers for any new version would include bugs or errors that caused their customers to do more work.
What Now?
Obviously, we’re past the point of no return as far as Learn 9.1 is concerned. There are some things Blackboard could do though that would help their customer base:
1. Commit to supporting current versions of CE and Bb classic until Learn 9.1 is far more stable and developed. Bb has pushed deadlines back before. They need to go another 6 to 12 months or longer. Let the improvements in Learn draw customers to it, instead of pushing them over (or away entirely).
2. Do a better job of publicizing their patches. People know that the SPs are coming out but that has a counterproductive effect of saying “your problem won’t get fixed until…” Blackboard needs to be upfront about doing and distributing patches for problems, especially problems that directly affect the work of faculty and students. Given the condition of Learn, Bb’s customer focus should be support. Like the power company after an outage, it should be “we’re coming to the rescue as fast as we can,” instead of “we’ve got a plan and it will all work out.” Timeliness and prioritization are what we’re interested in. I realize there are a lot of new features that need to be added to Learn, but if some of the more fundamental problems are still occurring, it won’t matter.
3. Eliminate the defensive approach. People don’t want to hear “it’s working as designed.” That only undermines confidence (as in, “Why on earth would you design it that way?”) It’s a “bug” or a “flaw” or even a “mistake.” If we hear that we know (or assume) Bb is working to correct it.
4. Involve users as much as humanly possible. Not in the hokey, incredulous “I designed Winows 7″ way, but in a way that addressed not only changes, but testing and release. The average end user would have spotted a lot of things that are now headaches for the company. Bb is getting there but needs more commitment. For example, instead of telling people, “Join the bug squad,” how about this: “That’s a good point and I will personally forward that to…”
Blackboard Learn 9.1 could still be a good, even great product (and it has some real strengths). SP 6 has made some improvements on key problems. Right now though, it still feels like a work in progress, which is the last thing in which people want to conduct their business.
Sincerely,
