Wiki Wednesday in Stuttgart

Cedric und ich hatten die Idee schon länger, nun machen wir Nägel mit Köpfen: Wir organisieren den ersten Wiki Wednesday in Stuttgart.

Vorläufiger Veranstaltungsort ist das Vinum im Stuttgarter Literaturhaus (Bosch Areal, Nähe Liederhalle). Den Termin werden wir in den nächsten Tagen festlegen … ein Mittwoch wird es sicher sein.

Wer Interesse an der Teilnahme hat, kann sich hier in die Teilnehmerliste eintragen bzw. mir eine Nachricht senden.

Enterprise social software adoption …

Dennis McDonald lays out some of the points he’s picked for his consulting in the social software space:

Importance of “viral” promotion (i.e., no drumbeating from top executives — let the users progress on their own).

Importance of making infrastructure available throughout the organization as a standard set of tools.

Ability of social media to make up for some of the natural limitations of large meetings (e.g., less outspoken people tend to do less well in open meeting settings and may not have the same disincentives to participate when using social media).

Natural emergence of experts.

Recognition that knowledge management and knowledge sharing are critical to innovation.

Recognition that creative people are what differentiates one company from another given the comparability of physical and financial assets among competitors.

Need to occasionally prune and archive inactive material in order to to keep things “fresh.”

I like his take so much, especially when he touches on this big overlap between innovation and social software – that’s my line of thinking and my inspiration (see BMID and frogpond).

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 …

Podcast on Motorolas wiki use

Dan Bricklin writeups a podcast (mp3) with Toby Redshaw of Motorola on their continued wiki use. Sound quality is not that good, it’s a telephone call recording after all, but it’s OK for me.

We learn about Motorola’s internal usage of wikis and blogs, the ways of implementation, actual usage in the organization, the role and usefulness of wiki gardeners and yet more on success factors :

They prune old and unused content, sometimes having a blog that lasts just a very short time. They work hard to keep it all fresh and up to date. They have knowledge champions in various areas who help do this. He feels these “domain owners” are an important part of facilitating the “quality” of the information and its organization. This is internally oriented, which has everybody with the same mission of advancing the company’s goals and under the same governance to keep out bad behavior, etc. This is not Wikipedia on the public web.

I also like this take on the further ways of Enterprise 2.0 concepts as they make inroads into all corporate environments (given that Motorola has probably a high geek-factor in its workforce anyway):

Toby sees an evolution towards “enterprise mashups” with business process management, enterprise information management systems, structured data management systems, data warehouses, and wikis. Process management data that shows a choke point or other problem in a process can link back automatically to a search of wiki data to find prior material relating to that situation and even identify individuals to be called in. They are trying to use both structured and unstructured information.

And there’s more interesting stuff, worthy 45 minutes.