- SCORM compliance. There was a time when every LMS had its own proprietary course format, but those days are over and if you encounter a system that doesn’t support SCORM, you should look elsewhere. It should, at minimum, be SCORM 1.2 compliant and be listed on the Advanced Distributed Learning site (http://www.adlnet.gov).
- Data import utilities and bulk actions. When you have more than (say) a hundred users, it is extremely time-consuming and expensive to maintain the system using only an administrative web interface. Most systems will have a way to do an initial data import of users and transcript history, but, at some point, it is inevitable that you will need to make a change for a large number of users (or courses). If the system doesn’t support the ability to make bulk changes through the web interface or an accessible API, you will regret not making this a requirement.
- Customizable reports. Getting access to data is one of the most important functionalities of an LMS, and yet many systems do not have the ability for administrators to easily create custom reports. Even if you think you only need course completions and scores now, those requirements could easily change down the road, and then you will need to pay to get that functionality added to your system (often an expensive proposition). Whether it is creating reports directly against the database or using a web-based WYSIWIG report engine, it is essential to have the ability to get the data that you need when you need it.
- Reliable and responsive Support. System support is essential to an LMS’ success, and yet enterprise-level solutions are notorious for having horrible system support. They may solve an issue, but it often takes weeks and numerous meetings to get any momentum. This can be more than a little frustrating when you need to spend hours creating hacky customizations just to make the system work the way it should. So, make sure that any vendor does more than just pay lip service to supporting their product.
- Cost-appropriate features. Learning systems can have a wide assortment of features. They can include special assessment and analytic tools, synchronous meeting integrations, competency management, asset management, wikis, forums, et cetera. Often these features were built to fit a specific client’s requirements and then folded into the base offering, rather than having been designed as part of a comprehensive product “road map”; still, LMS vendors can justify a high base price because of all the included features. Once you have an understanding of the features that you will use, make sure that you are not paying for all the ones that you do won’t.
This clearly is not a comprehensive list of what I look at when I am selecting an LMS vendor, but if the system doesn’t meet these requirements, I look elsewhere.
0 comments:
Post a Comment