Skip to main content

Digging deeper into CMS requirements (#4: Costs)

This is the fourth post about digging deeper into content management requirements. See also

This is perhaps the most important factor for WCMS buyers.

The total cost of an information system is easily displaced as buyers have a tendency to ignore the total lifecycle of the software. A CIO in a small company could explain that she spends zero on web content management since she does it all by herself, but the number of hours she spends updating the web content each week might amount to a significant expense relative to the size of the company.

A WCMS has costs upon acquisition. The software is bought, and additional modules or plug-ins will likely add to the price. It must be tested, deployed and tweaked by developers to fit the company's environment. A web design must be applied to the templates. Users must be instructed on how to use the system. Older content must be imported.

There are maintenance costs to be considered. Content managers receive wages. The WCMS is customized, extended and maintained by developers, adding cost to the investment.

The final step of the lifecycle is migrating away from the WCMS to a newer one, or perhaps the web content is to be absorbed into an enterprise content management system. The content has to exported from the old system and imported into the new system. Finally, the value of the previous investments are nulled as the intellectual capital put into the use of the legacy WCMS is no more.

Depending on the amount web content and the complexity of the software, all these tasks involve considerable costs.

Like in any form of company profiling, there is no immediate return on the investment (ROI). This can lead to an negative process where the WCM division of an organization gets low priority and receives low-funding, the division performs worse web content management, and the web-site returns less revenue. However, many of the WCM systems benefits, like in any IT-investment in general, are intangible and hard to find and measure [Weill & Broadbent, 1998]. Intangible benefits of running an advanced WCMS can include a smaller need for WCM-staff. One less full-time employee could quickly make such a large WCMS investment worthwhile.

Measuring all investment down to an economical figure can prove to be an inaccurate measure of a WCM system's success. There may also be other infrastructural business values which should be investigated. A quality web-site is a crucial part of the identity of a large IT-company. All in all, finding the ROI is a complex task which is not the center focus of this research, but it has been explored in many others [Hallikainen, 2002], [Ward, 2003]. I recommend exploring some of these before planning a CMS acquisition.


Hallikainen, P., Kivijärvi, H., Nurmimäki, K. 2002, "Evaluating Strategic IT Investments: An Assessment of Investment Alternatives for a Web Content Management System", conference proceedings from HICSS-35, IEEE International

Ward, T. 2003, "Find ROI: Measuring Intranet Investments" Retrieved 30. April, 2006

Weill, P., Broadbent, M. 1998, "Creating Business Value through Information Technology & Rethinking Technology Investments: The Information Technology Portfolio", Leveraging the new infrastructure, HBS, ch. 1 & 2, p. 1-4

Comments

  1. I wrote some articles on ECM/CMS planning here:

    http://www.scanguru.com

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp