Dear readers, you've in the past endured me ranting about the horribly-designed Requests for Proposals (RFP) that regularly cross my desk and the desks of my Blatant^ colleagues. (See my previous posts titled "Why Your RFP May Not Get You the Best Learning Management System" and "The Worst Type of Question to Ask in Your Learning Management System Request for Proposal (RFP).") These RFPs often ask hundreds of open-ended questions such as:
"Describe the procedure to create a report showing the progress of a group of learners in a curriculum."
The vendors with enough time and mental fortitude to tackle submitting a proposal in response to the RFP then deliver 50 to 100 pages of answers to these questions. The organization looking to acquire the technology then needs to read hundreds if not thousands of pages containing answers that look like this:
- On the main Admin Control Panel dashboard, click on Reports
- Select the Learner Progress Report
- Add the appropriate courses
- Show or hide the columns you wish to display
- Define which learners should be included
- Etc.
A textual description of a feature that should be demonstrated is a waste of everyone's time. Since few vendors will respond to your lengthy and poorly-designed RFP, you'll be less likely to find a great system. The proposals you do receive will contain information that in no way helps you select the right learning management system. You believe you are doing your due diligence in issuing an RFP; what you are actually doing is significantly reducing your chances of finding the right system. There's a simple alternative. Every once in a while, I receive from a prospective customer a short, elegant, Request for Information (RFI). Typically, these RFIs consist of one or more tables that simply require Yes/No answers from the vendors. Whereas a full-fledge RFP might take an LMS vendor 40 hours or more to complete, an RFI can take one-tenth the effort. The result is that the organization looking to acquire a LMS gets a 100 per cent response rate from vendors. In addition, the information received from the vendors can be easily compared and scored. Gone are the thousands of pages of materials, replaced with tables that illustrate feature sets at a glance. Here's a sample:
CAUTION:Your RFI should not contain a laundry list of every LMS feature in existence. The tables should only list your most important requirements. The longer you make your RFI, the lower the response rate from vendors. You're aiming for a 100 per cent response rate, which means keeping the RFI short and focused on your top-level needs. An RFI designed this way will quickly weed out the systems that aren't a good match for your learning initiative. Demonstrations of the remaining systems, ideally employing use cases, will then identify the best system. The vast majority of RFPs I see are horrible tools to select enterprise software. An RFI, if designed as illustrated above, is totally awesome and effective, and a very simple tool to help you select the right LMS.
