Web content migration: disastrous strategy

There is probably no worse strategy for an intranet or public website than content migration. It is doomed to failure from the very start.

Joe the manager picks up a jug. Inside that jug is milk that is curdled, sour and foul smelling. As Joe shakes the jug the solids and water separate and slosh about and the smell rises further, choking the air. Joe has a problem.

How is Joe going to solve this problem? Here is the traditional web management solution. Joe decides he needs a new jug. Joe gets a team together to decide what sort of jug is needed. They specify a really cool, all-dancing, all-singing, high-tech portal jug and they go out and spend a lot of money on it.

Then what happens? Another team is assembled to take the old jug and migrate its contents into the new portal jug. Once all the putrefied milk has been drained into the new portal jug there’s high-fives and lattes all-round. Job well done, Joe! Project complete.

If you’ve been involved in the Web for a while then the above story will be all-too-familiar to you. It is nothing less than shocking how little attention and genuine strategic focus most managers give to their websites. Even in 2008, I’m still coming across stone-age strategies that revolve around buying cool new technology.

From a management perspective, content has little or no value. It does not even deserve to be managed. Whether it is good or bad is irrelevant. Just shovel it onto the website. If it was written for print, so what? Just shovel it onto the website. The old website didn’t work? Buy new technology and hire a fancy graphics agency. The content? Just migrate/shovel it over from the old website.

You get the website you deserve. Quality content is at the heart of all great websites. This sounds like a self-evident, no-brainer statement. However, as we approach 2009, it still needs repeating.

Taking your old intranet content and migrating it into a new software system is doomed to failure. If your website isn’t working then ask this question: why isn’t the website working? Is it because of the technology? Is it because of the graphics and the layout? Or is it because of the content? Nine-times-out-of-ten it will be the content.

Content migration-and its first cousin, website “redesign”-are all about pouring sour old milk into new portal jugs. At some stage, we have to address the core web management challenges. Why do we have such bad content?

  1. We allow the organization to publish puff, fluff and vanity, instead of focusing on the needs of our customers/staff.
  2. We don’t hire web content professionals. Instead we find the most junior person in the department and give them the job of managing the website.
  3. We don’t see the Web as a unique medium-we just take print content and print thinking and shovel it onto the Web.
  4. We don’t review and quality control. We have practically no processes to take old content off our website.
 

14 responses


  1. If getting a fancy new technology is the only motivation, I see your point.
    On the other hand, there are sometimes good reason to go to a new system:
    - The current system is not supported anymore.
    - The current system is not flexible enough and does not allow you to fix basic usability issues.
    I also might add that migrating to a new system can motivate some to clean up old content. Migrations are pretty big and complicated processes, so the cleaner your content is, the smoother it will go.


  2. I was once tasked to provide advice to a number of webmasters in a very large Intranet with multiple subsites. Invariably, the webmaster was the administrative assistant of the department. These people had only been trained on how to enter content. They had no web related knowledge whatsoever. Needlessly to say, usability, information architecture or simple web copy writing were foreign concepts to them. No wonder content was so poor on that Intranet.


  3. We don’t hire web content professionals. Instead we find the most junior person in the department and give them the job of managing the website.
    Too true & great analogy there with the rancid milk in the jug Gerry.

    Previously, I have thought of a factory analogy for organisations that want to transact on the web.

    An organisation wants to manufacture high quality widgets. They invest in the highest tech plant available on the market and employ the cleverest management team money can buy. When it actually comes time to produce the widgets (web content) the clever management team decides enough capital has already been allocated and doesn’t bother employing skilled labour to make the widgets. Instead they decide that the people in accounts will have to take on the role of manufacturing the widgets in addition to their normal duties.

    A “Garbage In = Garbage Out” situation occurs instead of producing high quality widgets (the core purpose of the factory.


  4. I agree with Florence that systems need to evolve but disagree that migration is an effective clean-up strategy. Data is often cleaned to a point where it will import into the new system but there is rarely an actual review of whether it needs to come across at all. I am in complete agreement with Gerry that far too much content is published ‘because the boss wanted it up’, not because it serves any business or customer requirement. Being able to self-publish online cheaply and easily is great, but did we throw the baby out with the bathwater doing away with commissioning and managing editors when we moved from print to web? Someone who could say “that’s rubbish” or refuse to print dross. I also agree with Gerry that webmasters are often too junior to tell managers this common fact, even the good ones who know it.


  5. What an excellent, well-observed commentary on website ‘redevelopment’. I hope it hits home in the quarters that need to learn the moral of the story.


  6. The milk jug analogy has an important flaw: the “manager” still has to acknowledge that the milk has gone sour. Our life would certainly be easier if outdated content had the capacity of making itself known without us having to engage in costly reviewing activities–or even worse, resorting to hiring a full-time web editor. Don’t you sometimes wish rancid web content could actually make someone puke? :)
    On a side note: Gerry, I’m really beginning to wonder what’s your problem with lattes.


  7. Because organizations think good content has low value, sometimes it gets thrown away during a migration. Here is an example: I manage the site of a city government. On the edge of our town is a large tract of undeveloped property. It’s been the subject of a lot of study and “what should we do with it” planning in recent years. During the height of that planning phase, we had lots of content - maps, aerial photos, public comments, etc. - on the site. When we migrated to a new design, the plan was done and the planning department told me we didn’t need to carry that content forward.

    Later, the project began to get some attention again, and the planners wanted to put their final plan (100 pages, PDF, highly technical) back on the site. I pointed out that we still had the old content, including a few paragraphs describing the whole situation in layman’s terms, and that content could be useful to a lot of people who didn’t want to wade into the depth and detail of the final plan. No, the planners said. They didn’t want the other stuff. I argued that we already had it available, and we could review it and make it available with little effort. The planners still weren’t interested, so I gave up, moved on, and the public lost out.


  8. Thanks for the useful post. I agree with Florence that a migration can help force cleanup, and with the main thrust of Brian’s comment that the cleanup for migration may not get to what *really* needs to be cleaned. I would argue that what’s needed is Product Management for the Web site (just like a product manager for the iphone), similar to how even a new CMS platform needs to be product managed rather than just project managed to some arbitrary migration level (see http://welchmanpierpoint.com/blog/cms-implementation-product-or-project-manage).


  9. Hugo, actually I’m being a bit ironic, because lattes are my favorite drink! (But I don’t have a cool haircut.)


  10. Gerry makes a valid point, and always does, when it comes to content vs. technology. But, there shouldn’t be a “vs.”

    To add to Jim’s comments, how do you migrate good content? CMS is the latest, greatest, got to have it, make it so, thingamajig that management wants ’cause it’s supposed to reduce labor by and give control to anyone who wants to post content. It automagically takes care of dead links. But does it keep content in context?

    Like alot of theories, it sounds good, especially when sold as cost effective. But, what if you already have good content using a system that may take a bit more labor, but ensures that content is top quality and well maintained?

    Gerry, I would really appreciate hearing your take on the reverse of this article — how to manage good content regardless of technology.


  11. It’s more than doing a clean-up at migration. People don’t know how to write for the web in the first place, so they are often “cleaning up” content that will still be bad. Have you ever seen a mission statement on the home page? It’s totally irrelevant to completing a task. I’ve been working with my clients to get them to identify the major tasks that need to be done on any page and then clearly and concisely presenting information in a way that will allow site visitors to complete the task(s). SMEs need to be taught critical thinking about why people are coming to their web site and how to present the information in a way that assists them in task completion.


  12. Gerry,
    For me you’re right on the money! Regarding content I recently heard from an intranet manager who dumped 80% of his intranet content and he didn’t receive a single comment.
    Perhaps the way forward would be to take the exception route. Tell staff that all intranet content is going to be wiped next Wednesday unless it can be shown to be of some value. Bet the response would be underwhelming


  13. Patrick, I hear lots of stories about deleting 50-90% of content and how nobody notices. In another large organization the COO got sick of so much stuff being published that he banned publishing to the intranet unless for absolutely essential content. The intranet team thought there’d be war, but strange, there wasn’t. It worked. It’s time for some hard and ruthless decisions in relation to web content publishing.


  14. hopefully part of a website re-design would be re-designing the content as well, not just making the site have a new jug to sit in… I agree with what you’re saying, I’ve seen it happen (even programmatically where there’s no thought put into it at all… Being part of a web design firm handling a lot of re-design jobs, I can tell you that we always try to talk the client into re-thinking their content strategy as well, hopefully others do the same.

    brent
    @
    mimoYmima.com

One trackback

Leave a Reply