Our Blog

For content problems, technology is not the thing.

by Kristina Halvorson on August 19th, 2009

Hiya. I figured that since the book has been finished for, oh, two months now, that I didn’t really have an excuse not to start blogging again.

Anyhow.

So, earlier this week there was a little Twitter exchange that began in response to j. boye’s post, Who Should Be on Your CMS Shortlist? (Because j. boye is a "vendor neutral" consultation firm, its findings are very well-respected throughout the EU and beyond.)

Initially, there was a flurry of responses from people who thought one CMS or another really sucked. I also had people asking me which CMS I would recommend, which was kind of weird, as I obviously have no idea about their organization’s content management needs.

But here’s my point. While the CMS Shortlist is useful in many ways, it’s certainly not the best place to start when trying to solve your content problems. No matter what your CMS vendor tells you.

I’m a big fan of iSite’s The CMS Myth (and wish they would post more often!), whose central tenet is this: In reality, CMS success hinges on your plan, your people, and your process behind your web content management initiative.

That’s content strategy, folks. No matter what CMS vendors promise, no matter how "powerful" a CMS is, a CMS is not going to help make your content more useful, usable, or relevant to your end users. Moreover, a CMS isn’t going to solve anything for anyone in your organization who struggles with the day-to-day realities of content creation, delivery, and governance.

Don’t try selecting a tool until you really understand what you’re trying to build, and for whom. Start with your content strategy.

Here are two related posts by j. boye analyst Dorthe Raakjær Jespersen, well worth reading:

> Why IT Should Not Run a CMS Project

> Why IT Should Run a CMS Project

One last thing: I’m really excited to be a part of the j. boye Conference in Aarhus, Denmark, November 3-5. Tagline: "A knowledge sharing summit for online professionals." Bring it.

  • Spot on. Choosing one technology over another in order to solve obscure, poorly documented needs, quickly turns into a more or less relevant shouting contest over who thinks which features are most important, and which tool shines best.

    The question people should ask is "why are we on the web" and "what do we want to achieve there". Then make a plan.

    If only..

    That said, changing platform simply to get away from something else *can* be a good thing, as long as you don't marry the new platform. It might help us solve critical issues while letting us move on with our content work. It's not all bad.
  • An Old Friend
    Good post, but I would suggest that your claim is overstated. It can't solve *anything* related to delivery and governance? If your content development process is humming along just fine, but you can't get content published in a timely, regular fashion because an antiquated IT release process? Most any CMS can help you with that, as long as your users can use it. Or by the same token, if you need to able to frequently update your site with small but important changes...say interest rates, for example. I'm talking about things that can be filed under site maintenance. A CMS will pay immediate dividends, whether your internal processes are screwed up or not.

    I like your overall point, though. A CMS is not a salve for process or staffing problems within an organization.
  • Thanks for your comments, Old Friend.

    I re-read my post, and I see where I didn't choose my words carefully. Of course a CMS can help folks who struggle with the logistics of content creation, delivery, and governance. Thanks for catching me on that. What I should have said is that, without a governing strategy that is built on people and process, it's not going to fix their problems.

    Right on!
  • jeffcram
    Amen! Great post and thanks for the shout out to the CMS Myth (and the kick in the rear to start writing more often!). :-)

    Jeff Cram
  • Dwayne Fishel
    Great post...
  • joebachana
    Great post, Kristina!
  • Totally, agree Kristina. Also agree the The CMS Myth should post more often! ;-)
blog comments powered by Disqus