Will's Web Watch: Blogging (Part II)

In the second instalment of his two-part column on the blog phenomenon (see part one), Will Sturgeon looks at the reasons why more and more companies are taking the well-trodden path towards offering corporate blogs, aimed at providing an insight into what is happening within the company. But how wise is such a move?

Like logos, mission statements and awards on walls, the corporate blog has become something of a fashionable 'must have' for companies keen to be seen as dynamic and progressive.

But how wise is this? It is certainly something companies must avoid rushing into without thinking first about the problems they may encounter and the issues their blog may throw up. As with all fashions there are those who will be doing it purely because it's the done thing and not because it lends any value.

Then there are companies who will be able to derive real value from running a corporate blog, and nowhere is this more the case than in the technology space. Adobe is one of the most recent companies to launch a blog, and so far seems to be handling the relationship between its corporate location and the necessity for free and un-bureaucratic speech.

There is something of an oxymoron in all of this. The very phrase 'corporate blog' sounds like a contradiction. Blogs were intended to be the antithesis of the corporate information mill and yet inevitably that grass roots popularity brought the phenomenon far enough above the parapet for the large corporate to think 'we fancy a bit of that'.

One specific area of IT where the corporate blog has a perfect fit is within the IT security industry, an environment overrun with forthright opinions, breaking news and controversial subject matter - all the ingredients of a great blog if pulled together well.

The following is certainly not unique to any one sector, or even any one industry - the disciplines should be universal - but it's an area I know well and one which throws up examples of good and bad.

For example, Finnish security firm F-Secure is certainly committed to updating its blog - with prodigious regularity - and keeping readers abreast of the breaking news within its industry.

Updates are informed, often with supporting material and the kind of facts and figures required for putting issues into perspective. Written predominantly by the techies (for other sectors, read 'experts'), such as the company's CTO, Mikko Hypponen, it is also importantly light on marketing guff, if a little too heavy on repetitive themes such as an apparent obsession with mobile phone-borne viruses (and I believe corporate blogs can suffer if they become too blinkered on any particular issue, selling the company concerned as something of a one-trick pony).

Within the security industry, information can be hugely time-sensitive. While a company may be loathe to issue a formal press release every time there is a blip on the radar screen, they will also be aware that the time from an outbreak to notifying the press and warning the wider world is also hampered by levels of reporting and the internal politics of disseminating such information.

Well maintained blogs, if they become a commonly referenced source of information, can speed up these processes while allowing for a far more informal - but arguably more useful - reporting tool.

But any time-sensitive blog can also backfire. One which I had personally bookmarked upon its launch, hoping it would prove to be of some use, was actually shuttered on the very day I was writing this column - presumably because it hadn't been updated for several months.

And that's a huge problem. Had they really missed all the breaking news from the past two months?

If you are going to launch a corporate blog and tell people it's there on your site then you have to make sure you update it. Nothing says 'we're a two-bit organisation' like a two-month old post at the top of your blog.

Therefore if you launch a corporate blog you have to ensure you have the buy-in and guaranteed long-term enthusiasm for the project of everybody who is going to be working on it. (continued on next page...)