The cost effective wiki based intranet

Last Wednesday I spoke at he Intranet Benchmarking Forum’s Global IBF meeting in London.

Afterwards, I spotted Richard Dennison's post about one aspect of the event: the Financial Calculator.

Richard's post along with the single response by shaidorsai got me thinking about the cost/benefit equation of using a wiki for one's intranet.

During the meeting, while Lars Ploughmann of Headshift was giving his exelent talk, a senior figure from one of the global IBF members commented that a Confluence wiki was not that cheap. Though the licence fee was only GBP4000, the total installed cost was likly to run to 70 – 90k.

This could turn out to be true but I would argue that this expense is more-or-less a one-off.

During a typical year (for our Notes/Domino based intranet) I paid 30k for our business partner to develop an image library, 90k for a Powerpoint presentation storage and download area, and 20k for enhancements to a bespoke meeting booking system. This pattern was repeated each year as new business requirements emerged. For each requirement, a lengthy making-of-a-business-case process was needed.

Because the wiki imposes no business logic, process or work flow, once I have paid the first year cost, these types (and other currently un-thought off types) of application can emerge for free (OK, there is my salary and those of the business departments, but these would have been a factor of the old way of working as well!).

In addition, because the wiki supports self organizing, I expect business users to emerge, creating their own applications, with only a minimal amount of support from me (the central intranet management function).

If of-the-shelf commercial plug-ins, or even bespoke code is needed to support some of the more elaborate emergent apps, it should be possible to develop working prototypes for free using the base functionality of Confluence. Benefit could then be measured over a period and used to justify the additional spend as part of a phase II.

To steal a phrase from our head of corporate comms: "it's easy to get [financial] approval if the 'i' in ROI is kept small"

Use the wiki to bring in the lurkers

Often during my meetings with Euan Semple he refers to corporate intranets as "knowledge coffins". This is pertinent as one of my worries about the intranet that I manage is that, though I can see numerous items of fresh content posted each week, I am far from convinced that anyone is reading it!

I see enterprise strength wiki integration as a major way to address this and reinvigorate the intranet. Notification features such as granular Watch, E-mail Notification, and of course RSS, features of enterprise wiki offerings like Socialtext and Atlassian's Confluence will draw a regular audience into the wiki, and, just perhaps, the legacy intranet content via hyper-links.

This new crowd of active and frequent lurkers boost the ROI by consuming, and hopefully acting on, the wealth of business knowledge that the weekly posters so diligently supply.

To boost this effect, I would love to find a way to integrate the wiki's built-in search and labels (tag cloud) such that it returns relevant documents from the legacy intranet in addition to wiki pages. The converse of this would be to also have the intranet search include wiki pages.

Does anyone have experience of integrating wikis and legacy intranets in this way? I look forward to hearing your comments.

DotNetNuke Goes Social?

I have just returned from the Software Developer Conference (SDC) in Arnhem. My area of interest was DotNetNuke (DNN) the open source CMS and web application framework for the Microsoft environment. An entire conference within a conference, (DNN Open Force 07) was planned.

Although I no longer develop I have recently used DNN to deploy a number of corporate websites. Readers of this blog will know that my focus of interest is the intranet and enterprise 2.0. My experience of DNN had taught me that it has huge potential for use inside the firewall for corporate intranet/extranet apps but that the social tools were rather weak and underdeveloped. I wanted to hear from the core DNN team, whether 2.0 was on their radar?

I was not disappointed! Shaun Walker’s (DNN’s dynamic founder and CEO) keynote bristled with references to the social tools he was determined to bring to the core product. The topic also came up in break-out sessions by Salar Golestanian, Stefan Kamphuis.


Blog Platform

I gathered from later sessions that plans for a blogging platform module “as good as any out there” were well advanced and perhaps we would see this within six to twelve months.

Although the blog platform tool market on the consumer web is more or less sewn up by the likes of Typepad, Google Blogger and others (therefore the barrier to entry is huge) I see a significant niche market within the firewall.

Forward thinking intranet managers are crying out for a economical business blog platform that can be easily integrated with core intranet facilities like authentication and notification. If DNN get it right (provide the essential features and also the permissioning tools to allow the intranet manager to balance workforce self-organising with an element of control for both employee and customer blogging) they will be on to a winner.

I am considering offering my services to help them with their requirements definition.

Tomorrow I will post about the possibilities for an enterprise wiki within DNN.

All comments welcome.

Reinvigorate that legacy intranet

1. A recent post by by Stewart Madder on the Atlassian blog prompted me to explain how I believe an enterprise wiki can be used to re-invigorate a legacy intranet.
   
   Typically, the intranet tools which are in use today have somewhat clumsy publishing processes. There is a form to fill out with half a dozen fields (categories / sub-categories, Title, expiry, attachment and a few more) Some of them even have an approval/authorization process and other impose a conversion routine where word attachments are converted to HTML. Information is usually categorized via a taxonomy and it exists in silos that mirror the companies’ organizational structure.
   
   Thos who know wikis will appreciate the magical qualities they bring to content management, some of which are.
   
   - Incredible ease of publishing
   - Anyone can publish / anyone can read
   - There is no clear content owner. This reduces the feeling of intimidation thereby encourages others to pitch-in and improve the text.
   - The tags (labels) provide for a folksonomy and a way for one piece of information to be categorized in many ways thereby enhancing discovery.
   - Notification: Advanced enterprise strength wikis like Confluence have sophisticated “watch” tools that provide both email and (spam/virus free) RSS notifications of new and changed content.
   
   It is my hope that the workforce will create new documents within the wiki that reference, via hyperlinks somewhat more formal documents that exist within the traditional intranet thereby driving traffic to and reinvigorating the legacy intranet content (or the sub-set of that content that the workforce decide is still relevant/useful.
   
   As part of a future phase I would like to investigate Atlassian’s social book marking plug-in to see if this can be used to boost this effect.

Quechup Sucks!

I am very angry.

Yesterday I went through every contact in my Gmail account and inserted spurious characters into each email address. I then cancelled my membership at Quechup.

This morning at around 06:00 Quechup spammed everyone in my address book using the email addresses as they were when I signed up last Tuesday.

I implore all of you in the Blogosphere to get the word out regarding the shameful behaviour of this "service"

A public letter to Quechup

I have canceled my account with Quechup. The cancellation process gave one the opportunity to give a reason. I reproduce my response below as an open letter to the Quechup operators.

----------

I heard of outrageous and unacceptable behavior of your site/software re: spamming. I have read many reports of your software spamming every person in one's mailbox without first requesting permission!

I trusted your site with my Gmail password and elected not to email any of my contacts. I will be most annoyed if you spam them after I resign (as I have heard has happened to others)

I have blogged about this unacceptable behavior and advised everyone to stay away from your site. You have made a lot of people out here very angry with you. I suggest immediate cessation of the spamming and a public apology. Do not underestimate the power of the blogosphere to negatively or indeed positively impact your business!

You claim to be a social network is in my opinion rather unbelievable too. In my opinion you are a front for the iDate dating outfit!

Alek Lotoczko
lotocz@gmail.com

Don't have anything to do with Quechup!

This is a WARNING. There are many reports of this new site (that claims to be a social network) spamming ones entire address book without permission or warning.

I received an invitation from Euan Semple to join him on this network and accepted (based on my complete trust of Euan) Later when I attended a meeting with him I learnt of the outrageous and unacceptable behaviour of this site. It seems that the spamming can occur at any time after initial sign-up and the act of resigning from the site often triggers spamming.

HAVE NOTHING TO DO WITH QUECHUP!! and tell all of your Friends.

It seems that Quechup is operated by the iDate corporation: Shame on you!