Have you decided to become a Switcher? Or do you want to do an even-handed comparison between your current CMS and others out there that may or may not be a better fit for your institution?
I almost said, “meet your requirements.”
I avoided that because I want to make the point that when institutions begin the process of comparing solutions, we often don’t even know what our requirements are.
We may think we do. And so the traditional method of preparing a Request for Proposal (RFP) is written with everything we think are our requirements. Generally technical requirements. A big honkin’ document.
The vendors who self-select, or whom we invite to respond, return a similar major document in response. We invite them to campus; they demonstrate what their system does and during this demonstration we actually learn a few more of our ‘requirements’ as the vendor shows us. Sometimes we learn most of what we need to know about what we want that way. Sometimes we misunderstand what they said their system could do, and sadly, find out while implementing.
But what if there were another way?