Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Managing Content Management

Freshness Warning
This article is over 18 years old. It's possible that the information you read below isn't current.

A number of articles are being written recently on the care and feeding of Content Management Systems (CMS). Many of these articles discuss the fact that the users of such systems often find them more difficult to use than the way they used to do things, so they circumvent the system.

Below is a digest of some of the more interesting and well-reasoned articles on this phenomenon and what can be done about it.

Failings catch up with Web content management’s consultingware (Lighthouse on the Web): Companies are begining to get fed up with the high cost and poor results of customizing what was supposed to be packaged software. CMS vendors need to start rethinking their pricing if they plan to continue selling consultingware. Companies in need of CMS systems should consider building their own.

When is a CMS needed? ( Highlights from a discussion on when a site needs a Content Management System.

How to revive a zombie content management system (Step Two Designs): If a CMS is not designed for the needs of its users, it will cease to be used. There are a number of steps that can be taken to ensure that users will begin to use a CMS again.

Goal-directed content management (Cooper Newsletter): The failings of packaged CMS installations may not lie with the CMS vendors. Companies often hastily implement a CMS in order to gain control over the flow of information to their customers, employees, and partners. They expect the introduction of a CMS to be a panacea for bad management, convoluted workflow, and lack of ownership, like a house built on a shakiy foundation, the system will not last long.

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.


Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Recently Written

A framework for onboarding new employees (May 15)
There’s no single good way to onboard an employee that works for every role. Here's a framework for creating a process that you can adapt to each situation.
TV hosts as a guide for software managers (May 10)
Software managers can learn a lot from journalists or late night TV hosts and how they interview people.
The Improvement Flywheel (Apr 29)
An incredible flywheel for the improvement of a development team. Fix a few things, and everything starts getting better.
Managers and technical ability (Dec 26)
In technical fields, the closer you are to the actual work being done, the closer your skills need to resemble those of the people doing the work.
Dysfunctions of output-oriented software teams (Sep 17)
Whatever you call it, the symptom is that you're measuring your progress by how much you build and deliver instead of measuring success by the amount of customer value you create.
Evaluative and generative product development (Aug 30)
Customers never even talk to the companies that don't fit their needs at all. If the only product ideas you're considering are those that meet the needs of your current customers, then you're only going to find new customers that look exactly like your current customers.
Product Manager Career Ladder (Aug 19)
What are the steps along the product management career path?
Building the Customer-Informed Product (Aug 15)
Strong products aren't composed of a list of features dictated by customers. They are guided by strong visions, and the execution of that vision is the primary focus of product development.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2020 Adam Kalsey.