Objects In Mirror Are Closer Than They Appear
Now that the project of migrating our website into a new Web Content Management system is behind us, I’ve found myself thinking back to the start of the project and wondering what we could have done differently. With my perfect 20/20 hindsight vision, I offer this list of lessons learned for those of you whole might be undetaking a similar project:
- Demos, Demos, and More Demos. During the product demos, ask for real demonstrations of all features that matter to you. Not screen shots, not verbal reassurances that something will work, not a promise that the next release will be able to do what you need. Ask direct questions about versions of the software -- what features the current version has; what features are under development. Make sure you are clearly understand the answers.
- Get Your Hands Dirty. Ask for some hands on time with the product. No matter how hard you try to keep the products sorted out in your head, they inevitably start to blur. Hands-on experience will help. And by "hands-on," I don't mean watching the sales person using the CMS; I mean you, at the computer, mouse in hand.
- Know What You Need. Will you have lots of people editing the website? Then focus on the end user interface. Will your web editors use the workflows? Is email notification as part of the workflow important or not? Do you have web editors using both Macs and PCs? Think about how your campus will actually use the WCM and build questions for the sales people around that.
- Communicate With Your Campus. Update your campus regularly about the status of the project, new developments, changes that they can expect to see. For example, if the new system is going to mean a change in URLs sitewide, make sure your campus knows this and understands the implictions (e.g. that bookmarks will break; that references to URLs in printed publications must be updated). Communication more than you believe is necessary.
- Do It Yourself. Lots of CMS companies promote some sort of "import" tool. My advice? Even if they offer such a tool, no matter how tempting it sounds, import the site yourself. You know your website inside out; the CMS staff does not. And it's the only way to really learn all the ins and outs of the product. Hire a crew. Ask for volunteers. Host a weeklong migration party. Whatever it takes.
- Be Patient. Estimate how long you think it will take to get your website into the CMS. Now take that figure and double it. Seriously. You are going to encounter unpredictable issues, convoluted challenges, and depths to your website that you never knew existed.
- Nothing is Perfect. Finally, remember what I said in an earlier entry: there is no perfect CMS system out there, even if you have the people-power to write your own. Repeat after me: there is no perfect CMS.

