There’s value in the (intranet) mess

I like this David Weinberger ( here’s another interview with him) analysis of corporate intranets:

So the intranet at your organization is outdated—far behind that of the actual Internet. It’s marked by bad navigation. There are aging documents and old newsletter articles that belong in an archive. Maybe there’s a search engine, but if so that search engine only looks for materials in one department—not companywide.

Wading through your intranet is not only time consuming, it’s demoralizing. It’s a time waster, and a waste of the knowledge employees have accrued. This needn’t be the case.

While it’s obvious that most companies don’t really leverage the potentials of their intranets, I want to make it really clear that approaching this from a “just add more content and help people digest that information” perspective is just a little bit too tempting and won’t take you far. “Embrace the chaos wherever you are” is no solution in itself – we need to focus on the emergence of structures, and we need to figure out how the pieces fit together.

Wiki usability and Enterprise software sexyness

There’s an interesting debate going on, which is definitely worthwhile to follow. Arguments are exchanged whether, and if so how enterprise software can be as “sexy” as the all new web. Robert Scoble triggered it off (but somebody else called for it in the first place), got criticized and even flamed badly, others came to help, and so on. You know the game, see Techmeme for more. I am sure you will be enjoying the discussion in all branches and forks as much as I am.

While discussing UI, usability, user-friendliness and all is interesting (though putting lipstick on a pig really doesn’t help much) – well, even the endless arguments of “industrial-strength-software proponents” are entertaining in a way because we know better (this is dire stuff, and I ask myself if those guys ever worked with enterprise-style-software like R/3) – I want to chip in some observations from another perspective.

As a long-time enterprise software user, developer (yes, I was – years ago in my old life) and today enterprise 2.0 & enterprise social software consultant, I want to offer look at this from a position of wiki advocate (-evangelist, if you want).

Are enterprise wikis sexy? Most people don’t think so – but I think they get it wrong: Enterprise wikis are interesting not because of their advanced technology, their polished user interface or their neat mark-up language – in fact these are kind of disadvantages most of the time when we want corporate adoption to take off. Like when people doubt whether the wiki markup language will be accepted in their companies – they sure don’t deem wiki markup sexy. Yes, these are no shiny tools, they don’t offer eye candy, but they are well suited for doing their job.

The key is to start from business applications and needs – not tools. If the starting point is a specific business application like e.g. project management or business development support, users will judge the sexyness of the application in a different way – they will look for personal use and business value primarily.

Wikis soon gain “cool tools status” – just because they offer room for flexible emergent uses, coupled with great simplicity. In this light Dave Snowden opens a can of worms, which should attract more discussing, when he’s pointing to the inherent differences between complex social software and standard enterprise ware.

So yes, wikis can even be fun to use, and while sexyness is always a matter of taste, this is a good start and adds to the other wiki benefits like scalabity, connectivity and cost effectiveness that stand on their own anyway. This is no “fantasy land”, this is today, the 21st century and the changes will be great, and they won’t be about technology or tools:

Enterprise 2.0 is already upon us, providing us attractive, usable, reliable and secure applications. We just haven’t made the move to adopting it. But it’s happening now, with Generation M, mobile, multimedia, multitasking and here. Now.

More upcoming events at Web 2.0 Expo …

Planning the next five days, here’s some more: There’s an evening session on “The Starfish and the Spider” at the newthinking store (10117 Berlin Mitte, Tucholskystraße 48) on Tuesday evening 7pm-9pm.

Warum sind Wikipedia, Craigslist und Skype so erfolgreich? Wieso versetzten Kazaa und Napster der Musikindustrie einen solchen Schlag?

Weil sie das freche Seestern-Prinzip nutzen, das auf Dezentralisierung, Vertrauen und Kommunikation unter Gleichen aufbaut. Mit ihrer Wandlungsfähigkeit setzen die flinken Seesterne die hierarchischen Spinnenorganisationen immer wieder Schachmatt – und verändern damit die Welt.

Rod is an interesting guy:

[...] Stanford-Absolvent und Unternehmer, der sein erstes Unternehmen CATS Software Inc. an die NASDAQ brachte und u.a. auch ein früher Investor bei eBay war. Er engagiert sich für Umweltthemen und soziale Belange und half etwa bei der Gründung des Silicon Valley Social Venture Funds und des Environmental Markets Network. Zur Zeit verfolgt Rod mit der Firma twiki.net die Entwicklung von Wikis als open-source enterprise software.

Some reviews of his book, via newthinking store and my del.icio.us bookmarks:

Handelsblatt (german)
Welt (german)
Firstmedia (german)

Some english reviews: David Robertson and Harold Jarche, and here are some distilled book notes at the Socialtext Open Wiki – i.e. “main content of the book, but without the stories and examples”.

Some crossposts from my other blog …

Lately blog readership of this blog has taken up – yet, I suspect that some of you don’t know that there’s a sister blog on business model innovation and design (BMID) that I am writing too, and that sometimes stuff is blogged there that’s related or touching on Enterprise 2.0, Web 2.0 or Social Software. So here you go, in reverse chronological order:

Social Networks and Organizational Pathologies …

What’s the attraction in Facebook?

Make innovation a truly open and collaborative process

Marketinginstrument Community – Wie können Marken den Nutzer beeinflussen?

Portable soziale Netzwerke

Noserub @ Barcamp München Tag 2

MIT Sloan Business Insight, with a link to an interesting article (How can companies build organizational networks that encourage innovation?)

Jumpstarting innovation (and how to leverage collaboration …)

Technology, Innovation and Organization (for complex organizational settings)

Leitfaden zum Thema Web 2.0 & E-Commerce

The Impact of Web 2.0 and Emerging Social Network Models

Designing for Flexibility

IEEE Web Collaboration – Lessons Learned

Hier einige meiner Gedanken zum IEEE Web Collaboration Workshop am Freitag in München: Für mich waren insbesondere die Erfahrungen aus den jeweiligen Unternehmen und Einführungsprojekten von Interesse. Damit meine ich nicht nur die Vorträge an sich, sondern auch die Gespräche in den Pausen, die in sehr angenehmer Atmosphäre stattfanden. Ein Grund dafür war sicher, dass viele der Teilnehmer das Thema offen angehen und daher auch neugierig auf Neues waren. So standen denn auch in den Gesprächen an denen ich teilnahm eher die Chancen und Potenziale denn die üblichen Befürchtungen und Sorgen im Vordergrund.

Diese sehr offene Atmosphäre lag sicher auch an der Herangehensweise, die die Vortragenden wählten: Die Betonung der vielfältigen (Innovations-)Chancen sowie Einsatzpotenziale und -arenen. Einige Eindrücke:

Prof. Dr. Matthes (Technische Universität München) erinnerte an die Idealversion betrieblichen Informations- und Wissensmanagement (das “ideale” Wissensportal im Unternehmen) und machte dann deutlich, wie und wo sich durch Social Software neue Chancen ergeben diese alten Aufgaben und Herausforderungen neu und anders anzugehen.

Tonio Fruehauf (Rohde & Schwarz) betonte die Enterprise Social Software zugrundeliegenden Paradigmen und Prinzipien, die sich aus einem Verständnis von Unternehmen als komplexen Systemen ergeben. Er ging hier insbesondere auf die kulturellen Aspekte von Wikis ein, mithin auch Fragen der Akzeptanz und des Change Managements. Leider war hier die Zeit etwas knapp bemessen, ich bin mir sicher dass nicht nur ich hier gerne mehr erfahren und gehört hätte.

Auch bei Karsten Ehms (Siemens AG) wurde deutlich, dass der Roll-Out von Social Software in Unternehmen zwar einerseits geordnet und koordiniert (und unterstützt durch Coaching und Workshops etc.) ablaufen muss, sich aber gleichzeitig durch die offenen Plattformen eine Arena für konnektives, kollaboratives und adaptives Wissensmanagement mit vielen Freiheitsgraden ergibt. U.a. ist hier ein positives Menschen- und Mitarbeiterbild vorteilhaft, gerade wenn weitverbreitete und tiefsitzende Mythen und Vorurteile gegenüber Social Software bestehen.

Klaus Wriessnegger (SAP Inspire) behandelte dann inbesondere die Chancen von Social Software für das Innovationsmanagement, insbesondere um dieses zu beschleunigen bzw. produktiver zu machen. Weil er SAP von Anfang an erlebt hat konnte er zum einen einen sehr lebhaften Rückblick auf SAP als junges, schnell wachsendes Unternehmen (mit “Water Cooler Collaboration” und -Wissensmanagement) geben, zum anderen auf die verschiedenen Ansätze und Ideen um dann später “virtuelle Kaffeeecken” bei SAP einzurichten. Interessant sind u.a. das interne Social Bookmarking Projekt bzw. auch die SAP-interne Social Networking Plattform Harmony …

Customized wikis and out-of-the-box software

Shiv Singh of Avenue A | Razorfish detailed some of their mediawiki customizations. While he starts off questioning whether enterprise wikis are more apt than customized open source based solutions (which can be debated and argued for both ways, see the comments there …), another point caught my eye:

Furthermore, enterprise 2.0 as coined by Andrew McFee is not about cost but about what the software does for its users and how they shape the software themselves.

Well, this is an aspect of McAfee’s SLATES concept that often goes underestimated: Freeform, adaptivity and emergence. We need to prepare for these up-front, we need to design for emergence, so that usage patterns can evolve over time and to allow for easy tweaking and adapting of solutions over time. Then, scalability of social software in the enterprise does not simply equal more users/pages/page impressions/organization units involved/etc., it also implies a high level of adaptivity for a variety of tasks/organizational settings/security requirements/etc.

And yes, this (more holistically interpreted) scalability is a hard requirement for (pre-)packaged solutions … too often the need to prepare for all possible kind of tasks has led to bloated (complex and costly) software, that’s all but lightweight.

Emergence in Enterprise 2.0 implementation

More on emergence as a principle behind enterprise 2.0 concepts (add this to my post here) in Miguel Cornejo Castro’s take on the McAfee/Davenport debate (Davenport’s pov):

Integrating this “emergence” paradigm into the management methods of modern business is darn hard. It will take time, it will take experiments and failures. It’s not just a technology awareness issue (as the previous implementations of e-business and other disruptive technologies), it’s a cultural issue. A business-practices issue.

Web 2.0 is just another enabler for a cultural change that was already under way with Web 1.0. Witness forums, online collaboration tools (not invented with tags et al), and the emergence of the idea of the knowledge worker. Witness the whole latest generation of Knowledge Management as a discipline.

Now I wouldn’t define emergence as a paradigm, but rather as a principle (building upon an underlying paradigm of “complex adaptive organizational systems” and in line with principles like connectivity and adaptivity). Hence, it becomes clear that we must not focus solely on culture – yes, organizational culture is playing an important part, but it is neither the only adoption and implementation lever nor the only thing to mind when bringing web 2.0 to the enterprise.