Oct
12
2006

Office 2.0 Conference: distilled notes

Office 2.0 applications, in many cases, seek to reduce shift the tacit interactions we rely on (claim was 41% of our interactions are tacit, relying on phone, IM, email, memos, Post-its, smoke signals, etc).  The shift they implied here was that we have an opportunity to make more of these tacit interactions feel more like personal interactions through wikis, blogs, and web2.0-based collaborations.  Irrespective of whether or not these interactions are still actually tacit, they do feel more inclusive and conversational.   Blogs and wikis can, in many cases, replace the need for these tacit interactions, while adding the benefits (or hazards, I suppose) turning this information into searchable documentation, and adding individual attribution.

It took a lot of listening at this conference to distill the following:

Within the scope of collaboration, I’ve heard various iterations of 3 general rules about blogs and wikis. But most critical, understand that collaboration doesn’t happen without participation, so focus early efforts on improving participation.

  1. 1. No matter how many people are involved, lots or few, someone must be responsible for the blog or wiki. This isn’t dictatorship, but rather, just maintenance and direction on taxonomy, style, and focus. One person must be responsible. One person. One. Get it?
  2. 2. Wikis are “owned” by a team or group that includes anyone who’s submitted or even only read and chosen not to change. They still offer authorship credit, so individuals are still applaudable/accountable. Wikis are generally well suited to content that can be improved over time (think project plans, translations, )
  3. 3. Blogs are far more personalized and perceived as being a vessel for a collection of personal opinions, both the authors and the readers/commenters. Blogs are ideal for content that gets less relevant over time (like personal journals, expert advice on a specific topic, daily news)

    Adoption tricks

  1. 1. Leave obvious errrrors in wikis, and then let people fix them. They’ll immediately see how it works.
  2. 2. Corporate blogs can grow fast if you hold content contests. Ask for anything, and then let the good stuff bubble up. And let the good stuff be determined by the users.
  3. 3. Find the connectors and experts in your office and get them involved. Think of the people that have networks within the company, and who are often consulted voluntarily.
Written by chris in: General Musings |

2 Comments »

  • [...] In following-up on the Office2.0 conference, I just remembered that I neglected to link to Chris’ excellent write up one of the sessions blogs/wikis. Chris’ rounds up of some of the tips and advice that were shared for how to encourage traction of the existing tools like wiki’s and blogs within the enterprise. These notes stem from the learning that simply giving users a blank page to start with is not likely to be sufficient to gain traction with these new tools. example tips: Adoption tricks [...]

    Pingback | October 31, 2006
  • [...] In my follow-up on the Office2.0 conference, I just remembered that I neglected to link to Chris Matthew’s excellent write up on one of the better blogs/wikis sessions. Chris rounds up of some of the tips and advice that were shared for how to encourage traction of the existing tools like wiki’s and blogs within the enterprise. These notes stem from the learning that simply giving users a blank page to start with is not likely to be sufficient to gain traction with these new tools. example tips: Adoption tricks [...]

    Pingback | November 3, 2006

RSS feed for comments on this post. TrackBack URL

Leave a comment

Powered by WordPress | Aeros Theme | TheBuckmaker.com WordPress Themes