The future is Web 2.0 is collaboration …

… says John Chambers, CEO of Intel calling for businesses to increase knowledge worker productivity by implementing Web 2.0 social software but also by fostering mashups and virtual conferencing.

Here’s a video clip of Chambers Network + Interop keynote. It’s nicely edited and a convincing speech (“preaching the gospel”), so worth a look.

Yet one has to be aware that Chambers is betting on virtual conferencing and presence and aims to attract corporate interest onto Ciscos (WebEx-powered) collaboration approach. Keep that in mind when watching the video and when pondering the future of virtual networked collaboration …

For my part I am reserved whether video is really the killer application among the collaboration tools. Requiring synchronous presence of distributed collaborators is both costly and unnecessary most of the time (think more meetings …) whereas tools for virtual distributed collaboration like wikis are a low-cost approach that can be tailored to the actual needs (think more flexibility and serendipity …).

Interested in implementation of social software for collaboration? To learn more about my hands-on consulting approach contact me …

Interview with Ross Mayfield

Paul Dunay interviewed Ross Mayfield on wikis and published it as a podcast. You can’t download the audio file, but you can listen to it via a flash player.

I like this way of presentation, as it shows the cut marks of the recording and allows to skip forward and backward in the TOC:

Start podcast 00:00:00
Enterprise 2.0 defined 00:00:28
First Enterprise 2.0 deployment 00:02:07
How to Implement a Wiki 00:02:46
SAP’s Wiki implementaion 00:04:55
External marketing Wiki example 00:06:06
The Best Way to rollout a Wiki 00:08:13
How to build Adoption of your Wiki 00:11:55
What is the typical first project to start a Wiki? 00:14:59
How to get more info on Wikis 00:15:48

This interview touches also a lot of stuff that I layed out in my presentation here. No wonder I recommend both to anyone interested in social software for the enterprise …

Emergent wiki uses in organization

Chris Fletcher on pragmatic wiki adoption, adding to Bill Ives take (“Creating Successful Niche Content Spaces on the Web“):

[wikis] work best when there is a specific business need – getting teams to collaborate around a specific business issue or building community around a service offering is a great way to get individuals to start to experiment with how the wiki can be used

Straight to the point. He also argues against big bang approaches of wiki deployment, something that I can understand very well, and argue for all the time. In fact one big advantage of wikis is their capacity for emergence, i.e. letting patterns of usage evolve over time, which is not really leveraged when we install wikis in a pre-defined top-down way. Interestingly, betting on emergence does not collide with the demand for “specific business needs”, when these

  • only define a starting point for wiki usage
  • don’t restrict extensions and cross-theme wiki-linking
  • are (constantly) evaluated and adapted

Intranet Innovation Awards

Patrick Lambe of Straits Knowledge points to the Intranet Innovation Awards, that are searching for new ideas and approaches to the design and delivery of intranets.

I think he’s right to ask for innovation in the right places – tweaking and optimizing overcome work processes won’t help. And yes, corporate intranets are more important than most CxOs realize:

Intranets are – where they work well – environments that service a variety of working practices and activities, attract participation, and foster coordination and collaboration across the enterprise.
[…]
Since work focus, work patterns, coordination needs and organisation structure change on an increasingly frequent basis, big, highly integrated homogeneous environments are just not adaptive or nimble enough. Intranets are increasingly becoming more flexible, evolving environments, becoming much more like an interdependent ecology of open applications talking to each other – whether they be workflow applications, calendaring, web content publishing, document management, blogs, wikis, media libraries, podcasting, staff directories, you name it. Some areas of the intranet will be quite stable and structured, some will be much more experimental, some will provide current awareness and content marketing on a daily basis.

Still, I wonder why effective collaboration with partners outside the corporation (and thus outside the “intranet”) is seemingly no issue. This does not feel right, when we know that distributed work processes (in virtual networks, business ecosystems, extended value nets etc.) become yet more important. For me, “tuning” and supplementing internal oriented intranets with more outward-oriented (corporate) social software like wikis is a smart move, that should be pondered in intranet innovation projects …

Corporate uses of Web 2.0 technologies

Andrew McAfee provides another short insightful roundup on corporate uses of web 2.0 technologies like blogs, wikis, RSS, tagging, social bookmarking etc. In short, use them e.g. for:

  • collaborative production of documents (and meaning, understanding, commitment as I would add)
  • build a corporate encyclopedia, a “Wikipedia” for corporate data
  • as all-purpose teamware
  • a mega-adaptive ‘war room’ for fast-changing situations
  • spreading knowledge … and searching widely
  • ‘crowdsourcing,’ i.e. leveraging emergence by farming out tasks to a distributed crowd of people who decide individually and flexibly on what they want to work on

Using collective intelligence and the wiki to improve how you work, as you work

Stewart Mader outlines wiki uses in “continuous organizational (team work/knowledge work/innovation work etc.) improvement”:

the wiki can help any group work better by adapting to how they work, and letting them see where they’re strong and weak. Because it doesn’t define the terms of interaction and collaboration from the outset, and allows structure to be created, modified and removed as needed, the wiki quickly becomes a desirable tool because it “learns” how people work as they work, not after the fact.

He’s just right, now I’ll try to elaborate:

One could argue that wikis offer space for emergence, i.e. organizational self-organization.

And one could further add that they are ideally suited to support complex adaptive systems (CAS), and that their inherent capacity for connectivity is fine too.

But all this sounds much too theoretical, and well, we’re running real enterprises – no fluffy complex organizational systems stuff – don’t we?

But theory can be useful sometimes, so calling on the theoretical background of complex systems and systems thinking is a good idea. And when we accept that organizations can be modelled and understood as a complex adaptive system, employing social software concepts and tools feels just right, exactly because they can deal with this complexity …