Nina Platt likes this alternative intranet 2.0 implementation advice from Chris McGrath, who is one of those smart guys at ThoughtFarmer, where he suggests the first step is to blow up your existing intranet – McGrath writes:
“Step 1: Blow up the old intranet.
Why? It’s irrelevant to employees’ day-to-day job. The cumbersome updating process alienates people. It’s out of date and usage is dismal.
How? Find the intranet server, get to a command prompt, and type >rm -rf * (that’s a server admin joke…) Alternatively, unplug it. Seriously, it’s not worth trying to fix; you’ve got to start over.”
I think we all know where he is coming from – If you’ve ever been faced with a terrible intranet as an end-user, I’m sure you would love to see it blown up. However, while we might *think* about it, I’m not sure this is a good strategy in the long run. Blowing up your current intranet encourages that design once, fixed in stone mentality around intranets that got us into this mess in the first place. It could also be organisational political suicide. Also, which part of the intranet and its existing content are going to blow up?
I would prefer to see a transition and even co-existence, with the view of getting users and management stakeholders used to the idea of another Web 2.0 idea, the continuous beta.
BTW Along those lines, check out this article, The Search for the Perfect Intranet.