Collaboration and Process

Knowledge Management August 27th, 2003

Clay Shirky writes the following in his piece about, “Wikis, Grafitti, and Process:”

“A wiki in the hands of a healthy community works. A wiki in the hands of an indifferent community fails. The software makes no attempt to add ‘process’ in order to keep people from doing stupid things. Instead, it provides more flexibility, a crazy amount of flexibility, and intoxicating amount of flexibility, allowing massive amounts of stupidity and intentional damage to be done, at will, by roving and anonymous posters. And it provides rollback.”

Indeed, a healthy community doesn’t need a formalize process or a highly specialized set of tools to successfully collaborate. Like water or electricity, they will find a way through the muck; it may not be the most efficient or elegant, but it will certainly get from point-to-point.

Related Posts

  • Collaboration Culture -- Joe Wilcox of Jupiter’s Microsoft Monitor Research Service talks about MSFT’s collaboration culture within business groups and relates it to what former Apple executive Michael Mace wrote in his rant about Who Killed Apple Computer?: From Collaboration: The Microsoft Way:...
  • Building Your First Business Process -- Scott Woodgate over at MSDN TV demos “how easy it is to build a business process using Visual Studio .NET and BizTalk Server 2004, expose that business process as a Web service, and then consume the business process inside InfoPath...
  • Wiki: Tenacious Collaboration -- Tim Bray quotes Sam Ruby’s observation of the tenaciousness of collaboration via a Wiki “[Sam Ruby] speculated that this was like rugby, if we get enough people pushing in the same direction we’ll eventually move the ball in that direction.”...
  • Retro 80’s Gig Posters -- My buddy Marc sent me a collection of old gig posters advertising shows from the 80’s at the legendary club City Gardens in Trenton, NJ. Wow! They certainly bring back great memories … As an angst ridden teenager (who wasn’t...
  • Collaboration is one of the top three trends of 2000 -- "The onslaught OF dispersed work forces along with increased competition and shorter product cycles means collaboration between employees and business partners is at a critical juncture. Collaboration tools are an important means for turning the travel time and expense of...
  • Focus on the Process not the Feature -- I alluded to this the other day, but the following from Jupiter Research sums up MSFT’s marketing positioning strategy for the new Office System, which will also include Longhorn and I suspect enterprise search. Basically, they are not selling features...
  • Collaboration, suddenly, is cool. -- the following are quotes from an interesting article titled "Culture of Collaboration", which includes 10 recommendations for getting employees to adopt collaborative tools and use them in an effective way. "The biggest challenge of getting employees to work together online...


Leave a comment Comment RSS

Previous: HOWTO Guides: Hard Drive Data Recovery
Next: Remote Shutdown

3 Comments to “Collaboration and Process”

  1. Ben Margolin | August 28th, 2003 at 3:08 am

    Wikis are great, especially for internal documentation. OK, well, that’s what I believe anyhow. Actually convincing line coders to use them for some reason, IMO, is really difficult. Even more difficult to get them to use Good Wiki Style. I know many coders (especially inexperienced ones) hate writing documentation, but aren’t the benefits obvious? I went another round with a few of the developers who work for me in our last staff meeting, where they told me how it’s so “hard” to write in the wiki because it’s not WYSISYG, and that word is much better. Of course when I let them use word, they don’t produce anything useful–but with a lot of font changes. For guys who claim to understand why XML/XSLT is useful, they don’t seem to understand in documentation, the importance of focusing on semantics and not formatting. I threatened to make them write everything in Docbook, but only one of them even knew what I was talking about.

    Hmm, sorry for venting. I feel a little better now though :-)

  2. hatch.org : Collaboration Culture : Steven Hatch's weblog | September 12th, 2003 at 12:09 pm

    [...] In addition, establishing a collaboration culture is not a technology problem, because as I said a few weeks ago, “…a healthy community doesn’t need a formalize process or a highly s [...]

  3. mickazoid | November 14th, 2003 at 8:20 pm

    We use a wiki with DocBook export, to get the most bang for the buck. It’s nice. Looking forward to a grown-up FOP!

    Using a few well placed open source apps (a wiki, wvWare, html2db, etc. you can make the barrier of entry low enough to provide pretty massive payback re consistency and collaboration. and you can even import Word whackery from the Old Era.

    Adding htmlarea or other widgetry in place of the text entry field is one way to try to placate the GUI addicts, but you may also wanna point out that the majority of people who scream for GUI aren’t users, but rather are pesky developers who will, once they go plain wiki markup, often never look back. Tell them they can use their plaintext editors and paste the text, and they often lose their noodles entirely.

    For inspiring collaboration within a team, you can combine single sourcing, wiki collaboration and markup, docbook consistency, word import, and image handling, all free, all now. It’s a nice time to be alive.