Contented Management laughing buddha logo

Contented Management

Contented Management

WCM season preview

Leon playing football

The new Premier League season is upon us in England and it was with some surprise that I noted Tottenham were being sponsored by Autonomy, purveyors of Bayesian probability and content management systems.
Professional integrity dictates that I shouldn’t exclude Autonomy from shortlists just because of who they sponsor, but this deal may cause those of you with taste to reconsider whether Autonomy are meeting their corporate and social responsibility targets. Yes, I am an Arsenal fan.
I was going to write an article that mapped each Premier League team to a WCM product, but realised I’d be sued by anyone I associated with Blackburn Rovers or Stoke City. Nevertheless, I think their are a number of useful analogies to be drawn

Beautiful doesn’t always mean effective

Some WCM products have editorial interfaces that entice you to play around with them: thoughtfully designed with user-friendly tools like drag and drop, red-lining, or DAM integration. Others practically repulse: ugly web forms with incomprehensible labelling and non-sensical reference data.

But don’t assume that a beautiful GUI makes for more effective content management processes. Just as Bolton Wanderers are restyling their footballing approach under Owen Coyle to be more appealing, this won’t mean they’ll finish higher than they used to under the ugly pragmatism of Sam Allardyce. Give free reign to your editors’ creative spark and you may find your content strategy going down the pan.

A solid financial basis

Virtually no Premier League football club is without debt. WCM vendors are in a less financially perilous situation but hardly paragons of financial stability. This should make you wary in your contractual dealings with them. Always hold proprietary source code in Escrow. It’s not much of a security but it’s better than none at all. Check the financial stability of services partners and weigh this against their ability to deliver: a team that’s doing badly is likely to have disincentivised staff and the best of them may be looking to leave.

Be wary too of cutting deals that actually disincentivise your suppliers: if you cut their profit margin too much they’ll focus on more profitable accounts when the going gets tough. And the last thing you want to do is see your team go into administration like Portsmouth last season.

Living off past glories?

Just as some Premier League clubs look down on new entrants and see themselves as the established top tier, some WCM vendors subscribe to a similarly blinkered view. Don’t choose a team just because they’re an established player and appear in an analyst’s magic quadrant. Take a look at the wider field and figure out what it is you’re really after from your supplier. Having a vendor with a good reputation in the industry won’t improve your website any more than winning the league 49 years ago makes you a better club today.

The long-term view

So if you’re ignoring the past, what abou the future? No need for Paul the octopus: take a look at company history. Has there been a recent big-money acquisition? If so, you can be certain that the vendor is going to be focussing more immediate efforts on proper integration of that product rather than on new features. Assimilating new players takes time, as Manchester City discovered last season.

Or was the last release community-driven? If you don’t have the means to engage actively with that community, how are you planning on getting the enhancement (and fixes) you need the product to deliver? You’re unlikely to hold any sway over the selection despite your investment.

Where’s the support?

A crucial consideration must be who’s going to support your team once you kick off. Is there a loyal and knowledgable fan base? Are they likely to up sticks for another trendier team the minute the going gets tough? And where are they? If all your support is in a different timezone, you’re going to have problems.

In my experience, transatlantic services particularly suffer from this Manchester United syndrome of long-distance support. Many European vendors have struggled to provide north American clients with the same levels of support as clients in Europe and the reverse is certainly true. The problem is is seldom resolved by takeovers, when a larger company may bring a much larger support team, but product experts remain few and far between.

It’s not about loyalty

In the end, remember the crucial difference between implementing a WCM and following a football team: you’re a client, not a fan. I’ll support Arsenal even when the players all inevitably collapse with cruciate ligament injuries before Christmas; I’m a lifelong fan. But if you’re not getting what you need from your team, relegate them and seek your glory elsewhere.

Philippe Parker on | 20 August 2010

Contented Management

CMS trade-in deals

Fatwire is waiving licence fees for clients who migrate to its CMS from Vignette or Interwoven. Both these vendors have traditionally had quite expensive licensing models so there are potentially big savings to be made, although FatWire has a feature set that is probably closer to Vignette than to Interwoven.

The catch is that you need to procure migration services through FatWire, but they’ve partnered with content migration specialists who you’d probably use anyway. You just lose some flexibility on negotiating the price, but you’re going to be saving money anyway.

But does that make it a worthwhile exercise? As Irina Guseva points out, the project inevitably costs more than the licence, so the cost of migrating may well be more than your existing Vignette or Interwoven maintenance costs.

More importantly, the reasons for migrating are wrong. You shouldn’t abandon your CMS just because you can get a better deal elsewhere. It’s not like switching an electricity supplier to get a better rate. Just moving from one CMS platform to another is unlikely to resolve the content management issues you’ve been experiencing. You need to think about which problems you’re going to solve then pick the processes and technologies that will address these.

FatWire’s rescue package doesn’t make a business case to move away from Vignette or Interwoven, but it does put the product on the shortlist if you are migrating. For dynamic-driven Java websites, you have to consider FatWire, but it’s not a shorlist of one. Remember, open source products don’t have licence costs either.

So let’s commend FatWire for their marketing effort, and if you’re looking to migrate from a platform other that those mentioned, ask FatWire if they’ll cut you the same deal. But don’t trade in your existing CMS just to get a better price. Address your issues, conduct due diligence and pick a product that meets your requirements.

A couple of useful links:

Philippe Parker on , , | 16 June 2009