Why IT should not run a CMS selection project

Written by James Robertson, published August 3, 2009

Categorised under: Content management

Dorthe Raakjær Jespersen has written a post on why IT should not run a CMS selection project. To quote:

This discussion often comes up during CMS selection projects, sometimes even after the process is well underway. The consequence is a delayed project, with much time wasted on meetings and emails discussing ownership. Too often the online communications team ends up having to argue why a particular system proposed by the IT department is not a good fit; a difficult task.

Tags: , ,

One Comment:

  1. Ariel Araos commented on August 11th, 2009

    IT Doing CMS? Don’t Think So.

    Soon after I finished my Masters in Environmental Science, I worked for almost ten years in IT in various roles. I definitely agree CMS should not be done by IT staff.
    Information Technology has a strong emphasis on technology, and not in the management or the content of the information. In the last 15 years, I have seen a gap growing between the technical perspective of IT and the needs of information and knowledge managers (specially in the tertiary education sector. If Information Technologist take charge of CMS, it would be like our urban infrastructure being design by auto-mechanics.