Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Content Management

Managing Content Management

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

Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.

Older...

What I'm Reading