Thinking through your Content Management System Needs

You've been talking about it for a while, but now your organization has finally decided to get a new content management system (CMS).  This is the "BIG" project of the year.  All of your hopes and dreams for where your website is heading are wrapped up in your CMS project. 

In fact, if you're a typical organization, everyone has started to project their own goals onto the project.  "We'll have that fixed when we get our new CMS," they say, and, "That will all be addressed with our new CMS." 

Goals for almost every CMS project:

• Keep content more up to date
• Allow individual "content managers" easier access to update their areas of the website
• Create a more consistent look and feel for the organization
• Make search indexing and search within the site easier
• Improve navigation
  

More advanced goals for your CMS project:

• Improve content structure: Produce content in multiple standard formats so it can be reused by other websites and systems
• Support improved navigation: Publish content with appropriate tags and categorizations so that new content appears in all appropriate locations rather than just in one place.  For example, if you publish three safety publications on water, fire, and snow, the publication on "fire" should appear in the fire safety area of the website as well as the "safety publications" area without much extra effort
• Works well with other technologies (Web 2.0 widgets, other systems you buy, etc.):  Your CMS needs to "play well with others."  If you are looking at CMS vendors and the vendor says, "we do that" in response to all of your questions, that is red flag.  CMS are not best in class at everything.  You may want to use YouTube for video, Google for search, GovDelivery for email communication, and Wordpress for blogging.  Find out how the CMS will work with these systems rather than hoping the CMS will do everything you want.
  

5 outcomes you should expect from your content management project:

1. New content can be posted within 15 minutes by any approved individual in the organization. 
   
   I know that some content has to be approved, but if your project is more focused on "workflow" and approvals rather than efficiency, you may want to rethink things.  The fact is that in order to be current, Web content cannot be bottle-necked by cumbersome approval processes.  Set policies and guidelines for content and let people publish without too many extra steps.  As long as you're not publishing the new interest rates, you can make edits later without major consequence.
   
   
2. Any web page can be published as an XML / RSS Feed at the same time as it is published in HTML.
   
   This ensures that other Web managers, bloggers, and even other systems (including GovDelivery) can read and interpret your page in an automated way.  In the Web 2.0 world, this type of openness and sharing is important and will ensure that your content "has legs" and gets reposted and repurposed across the Internet.
   
   
3. All web pages are easily indexed by major search engines.  I'm not an expert on this, but it's an easy topic to research online.  Google has all kinds of tools for this at www.google.com/webmasters
   
   
4. Content can be published to multiple locations at the same time without too much extra effort.
   
   
5. Your system supports a user-centric design. 
   
   Oops, you thought your CMS project was going to give you a "usable website."  If that's the case, you should stop right now and focus a bunch of time on the design and usability of your website.  A CMS is for managing the content on your website.  If you have a poor design and a good CMS, you will just have very up to date, but unusable content.  

Finally, you need to have a way of capturing information from people who are interested in your content so you can reach out to them when updates occur.  My company, GovDelivery, works with government websites on this and has found the following best practices to support the rollout of new content management systems.

• Have a proactive communication system in place before you launch your CMS. Why? You want to know what people are interested in on your current site so you can focus more effort on that content and make sure people know how to find it when the new website is up and running.  Even the best redesigned websites often annoy their most regular users.  You can help prevent this frustration by allowing regular users to signup for updates before you rollover to the new CMS when links/designs/navigation will typically change dramatically.
  
  
• Make sure that your new CMS will work with whatever proactive communication solution you are using or plan to use to allow you to automatically send updates when you publish Web content.  You don't want to publish Web content and then have to login separately to send email.  In GovDelivery's case, if you publish information in RSS or can connect to a Web Services API, you'll be able to automate your outbound email communication.
  

This is a complex topic that I will return to if there is any interest.  When I mentioned I was writing this blog entry, I got some great links to other resources on vendor websites and regarding open sources CMS.  If the topic is of interest, I will write another article on vendor selection.