Skip to main content
eLearning choices for content developers -- Docent, Inc. looks like a good choice for enterprise-level courseware development & curriculum management, while Qarbon provides a more open, ad-hoc tool/service (quick-and-dirty tutorials).

I expect many companies can justify using both tools, assuming teams can effectively match content to delivery technology. However, content providers are likely to take the "path of least resistance" in creating and publishing their goodies, which means Qarbon is likely to see higher numbers of content creators/publishers in a given period.

As an example, I introduced a project manager to the Qarbon tool and 3 hours later he'd built two tutorials for his project constituents. In that time he'd downloaded and learned the "builder", then created and published the actual training content.

Comments

Popular posts from this blog

InfoWorld published this excellent brief overview video on cloud computing. Worth a look if you're in the dark about the cloud!
One Laptop Per Child - Poor Use of Funds? A digg post links to a blog posting by a representative of European think tank Globalisation Institute who believes that the OLPC initiative is a waste of money and that its organizers and backers should "leave computers to the market economy." Interestingly enough, it's because of OLPC that "the market economy" is finally recognizing the opportunity emerging among developing nations. Just last week Microsoft announced a $3 software bundle for developing economies. "Microsoft and others needed to begin reaching out to the developing world through existing, lower-cost technologies such as cell phones and television to provide basic computing and educational opportunities, according to Gates." While cell phones will undoubtedly permeate emerging economies more quickly than traditional PCs, they fall far short of delivering the educational value of devices like OLPC . Governments around the world are re
Planet PDF - PDF Collaboration In Action - WebDAV -- Adobe is leading the collaboration charge on WebDAV in much the same way that Userland/Dave Winer are doing so for SOAP and XML-RPC. I've been struggling to define an architectural view that clarifies the complementary nature of WebDAV and SOAP/XML-RPC ; both are promising collaboration platforms, each takes a different approach to collaboration. There's no question that people and systems will continue to use and manage digital files in the traditional (e.g., file system-based) way that WebDAV supports, but these two technologies certainly begin to blur the lines, as both virtualize file location & movement in ways that previous network protocols & implementations have not. We may ultimately find that WebDAV just provides the industry with a stepping stone to a more flexible "file-sharing" environment based on SOAP, but once adopted WebDAV may be difficult to unseat. I guess we just have to wait