Managing Content Management

Freshness Warning
This blog post is over 20 years old. It's possible that the information you read below isn't current and the links no longer work.

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? (drop.org): 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.

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2022 Adam Kalsey.