Communication is everything. The moment we’re born, the labyrinth of neurons in our brain starts processing and distributing information. Strong neural connections help our brains to expand their function so we can make smart decisions and reach our potential. Our well being relies on quick, efficient messaging. If the right connections aren’t made early on, our brains miss vital input that would otherwise instruct or protect us.
This week I have been thinking a lot about how poorly we manage data and information. The quality of the data and the lack of needed data has historically been an issue at work. We have focused a lot of our time on data mining but never really recognized that one day there would be too much data and information for our staff to sift through. Recently, our managers proposed two new data sources for the operational staff to review and I decided that it was time to hit the panic button that we're currently giving out more information to our workers than they can handle.
When a business presents too much information to their staff it is a lot like catching deer in your headlights. If the deer is too overwhelmed to run and you don't steer the car out of the way then no good can come to both car and deer. This is where I think we are at work and we're needing to slow things down a bit to give both driver and deer time to think about their next move. For the moment at least, I'm personally at a lost on how best to solve our issues with information overload.
Who really defines what is a CMS?
You do.
I'm more convinced than ever that CMS experts aren't really in the driver's seat when defining the content management system. Experts in the field of content management are more or less observant passengers that are there to help you not get lost and to point out the significant landmarks on the way. This journey takes you to places while you the customer remain in the driver seat with all the privileges and responsibilities of being the driver.
Over the past few years I've realized that my work preference is to keep things as simple as possible. Sometimes when defining information systems keeping things simple works while other times the system is new and remains too complicated to define. Thanks to my reply in a productive rant against CMS by Laurence Hart I'm not only understanding my aversion to being called a CMS expert but also my philosophy and role in defining what is a CMS. This personal philosophy is developing...
Scott Abel convinced me a few years ago on my own blog that the definition of a CMS is never static and always changing. We’re chasing our own tail when we get nit picky in our definitions of a CMS. Somewhere in all the marketing that has been done for terms such as CMS, ECM, and WCM…we have forgotten the difference between information system and information technology.
I'm one of the many CMS enthusiasts excited about CMIS. CMIS is the abbreviation for the OASIS Content Management Interoperability Services (CMIS). Please check AIIM's official guide to CMIS for further details.
Before you do go over to AIIM's site, you might want to also check out Stefan Waldhauser's "8 reasons why CMIS will transform the ECM industry" posted at Digital Landfill. I like reason number four:
4 -- No more lock-in to one ECM-vendor because of CMIS.
Until today the ECM industry was driven by high complexity and proprietary systems that prevented to switch to other vendors. Even when a vendor dramatically increased maintenance fees (many customers know what I’m speaking about) there often was no choice to go somewhere else because of the tight and proprietary integrations between the customer build applications and the ECM-infrastructure. CMIS will help separate the applications from the ECM-platform and so there will be no more lock-in to one vendor. Doesn’t that sound great?
I think the biggest thing CMIS offers is customer satisfaction in not having to choose one vendor over another. As I stated this morning on Twitter, I see CMIS as recognition that the "total enterprise solution" is a lie. I have yet to see an enterprise software package provide the complete solution that vendors often promise their customers. Somewhere in the product's life cycle the customer finds that they need more than what the current software and/or vendor can deliver but the customer also isn't ready to leave their current system behind. CMIS hopes to solve the migration issues involved with moving from one application to another by allowing both applications to work together.
There is a cost issue here with CMIS though and, so far, I haven't seem much dicussion on the subject. While CMIS allows more than one application to share and work with the content it will not always reduce costs and maintenance fees. The fact is CMIS may now require the customer to provide ongoing support for multiple applications and platforms instead of the single platform they were once supporting. In general, when the customer's IT group has to support additional applications they also need additional time and money required to provide that support. Just like the problem CMIS is trying to solve, CMIS will not always be the total solution to your problems.
"These habits and rituals, developed over many years now are hard to break. I find it quite staggering for instance that the collective wisdom of a very established global manufacturer is contained in folder after folder after folder of files on shared drives with seemingly very little actual captured knowledge, context or lifecycle management."
-James Hoskins, "#fixwcm – some thoughts from the front line…", 2020 Visions, November 5, 2009
Tony Pietrocola, Bridgeline Software, posted on their blog seven ways to "Avoid These Common Mistakes When Implementing WCM". Two of the tips he gives have been giving me trouble lately.
2. Have the requirements from all stakeholder groups been accounted for? One of the critical issues that sink CMS investments in the organization is missing all necessary input and buy-in.
I do my best to keep my two IT world's separated. One of those worlds of course is my obsession with content management systems which includes this blog and numerous discussions with almost anyone interested in CMS. The second world is my IT position as a federal employee for a small government field office. In order to avoid conflicts of interest, rarely do I allow those two worlds to cross one another. You'll find very little mention on this blog of my work for the federal government. At the same time, very few people in my agency are even aware of my CMS side hobby.
Earlier this week, Lullabot's Jeff Robbins posted an article about his company giving Drupal on-site training to employees within the Department of Commerce. In his post Jeff discusses the interest those employees have in Drupal as well as mentioning that the door continues to widen for Drupal in the federal government.
We had a great week of on-site training at the Department of Commerce in Washington, DC last week. They've already launched recovery.commerce.gov in Drupal and they're currently in the process of rebuilding Commerce.gov as a Drupal site. We spent the week with their team making sure that they understood not only how to build and present a Drupal site, but also the benefits of the Drupal community. They're a smart bunch and it's always fun to watch the synapses sparking as people realize all of the ways that they can snap together Drupal's pieces to create interesting web functionality.
There seems to be quite a buzz around Drupal in the government and as the Commerce team walked around the building with Drupal books under their arms, they got lots of comments from people in other bureaus, saying, "Oh! Drupal! We're thinking about using Drupal." Word is starting to get around about Drupal as a great platform for government websites.
Jeff Robbins is correct in saying that until recently, there was a lot of hesitation to using open source CMS such as Drupal for government portals and content delivery. I know earlier this decade my agency's Webmaster had considered using Drupal before deciding to build the agency's own CMS in-house. During this time period Drupal 4.5 was available but while my interest in information systems was growing, I had never really looked into Drupal (Mambo was in the open source CMS headlines back then) . However, just the possibility of my agency considering the use of Drupal during that time helped motivate me to learn more about Drupal.
Matt Mullenweg posted on his blog a link for how to install and run a Wordpress blog on a Palm Pre. We're not talking how to manage your Wordpress site using your cell phone as a client. Instead, we're talking about running Wordpress with the Palm Pre as the Web server. That's pretty impressive.
In ten or twenty years from now why couldn't you host your blog or personal CMS on a portable device? Could what appears to be a gimmick today actually be the future for Web applications? I don't think it's that far fetch of an idea as many might think...
I often think both IT and managers don't reevaluate their business processes enough. The TechRepublic has a great article in reminding us that this economy presents a great opportunity to implement 10 best practices for business process measurement.
Lean times often present opportunities for analyzing, fine-tuning, and improving business processes. In fact, the economic survival of some organizations may depend on such improvements. Here are some pointers to help you build a successful process measurement program.
I particulary like #9: Don't forget about IT metrics.
A number of content management systems allow for data to be classified using taxonomy (sometimes called categories or tags in a CMS). Most of us that use CMS and taxonomy aren't experts in how best to structure our vocabulary and usually end up with a mess of terms. In the end, we have a mess on our hand and wonder how best we should approach cleaning up the terms we're using.
A blog post by Lars Trieloff, The Art of Mining a Folksonomy, gives some great suggestions for cleaning up your taxonomy. The post was written for the Day's CQ5 CMS, but should be of use to almost any CMS user with taxonomy.