Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Managing Content Management

Freshness Warning
This blog post is over 21 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

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.