Mark DiSciullo — Thu, 17 Jan 2008 21:39:10 GMT

I’m quite surprised at the lack of information out on the web to inform a decision NOT to use CMS. What if all of the sites my organization manages are are all required to be very unique in order to allow them to remain competitive in each of their brand spaces? What if my current team has efficient and savvy interactive designers and developers that can meet the unique needs of each of our marketing team clients? What if content is only occasionally updated after the initial launch and rarely updated during its lifecycle? What if content is typically created from scratch and rarely requires pulling from a shared central repository? What if the current workflow requires interaction with other organizations that have their own workflow management tools that they do want to give up? Sounds like I don’t need a CMS system. But a CMS vendor will try to convince you otherwise. CMS is not always the solution. No one seems to talk about this. Optimized processes, clear communication plans, design and content styleguides, involvement of legal and compliance teams (content approvers) early in your project as a partner in the creative process are all sound alternatives for instituting a complex CMS system into a very dynamic process.

Boxes and Arrows: Comments by Mark DiSciullo