I love this title – the new meeting the old. Social is
“the new kid on the block” and the
intranet is
“the old stale guy”. Making them work together – side by side – is one of the missions in your
Enterprise 2.0 strategy.
That might be true today, but not tomorrow. My belief has always been that you should marry the new with the old. That’s the only solution to the fact that you invested loads of money into your intranet (read:
Sharepoint). It simply doesn’t work to tell your CIO to
“scrap that, we are going to do the wiki & blog dance”. So my thesis is that the “social” will record the journey to the fact that is published on the “intranet” – there’s the marriage.
That
was my thesis. Until I spoke to the CTO @
SBAB who simply said
“why should we keep the old stale guy – he is… old and… stale”. Why should you keep something that takes you three weeks to publish content? Why keep something that prohibits collaboration?
With a successful
E20 strategy the
intranet becomes obsolete.
Why? Because the users behaves like a herd, they will simply move over to
“the new kid on the block” because it's much more easy and accessible.
The same herd behavior is seen on the net. A new and more easy to use service gets users to move.
So... are you going to lead the herd or be a solitary?