Entreprise 2.0 and more

Wikis or Blogs?

Posted on: August 26, 2009

As mentioned in my previous post, I have planed to make a proposal for replacing the common email of my division by a wiki in the hope that it will help limit the information overload and improve the knowledge management within the division. However, after my attending last week lecture on enterprise (or corporate) blogging, an question about the choice of wikis or blogs was brought up.

Trying to answer this question, I have made a research on the internet and come across some interesting ideas, which I would like to share in this post.

First of all, let’s have a look at this comparison between these two web 2.0 applications presented at Everything Wiki (a wiki about wikis) which advocates for the merits of wikis

A collaborative website which can be directly edited by anyone with access to it A personal or corporate website in the form of an online journal, with new entries appearing in sequence as they are written.
Many authors, various personalities & experiences, opinions face scrutiny of community or are listed as such. Typically one author, one personality, one opinion.
Knowledge comes from community of dozens or even thousands of topic experts. Knowledge limited by single person.
Growsrapidly at all hours of the day. Grows slowly, one post at a time.
Articles constantly change and continuosly updated. Each post becomes stale over time.
Discussions can take place on pages or in the discussion forum (at least in Wetpaint wikis). Discussions take place in the comments of a post, typically approved by blogger.
Ranges from easy to setup to very difficult, depending on chosen solution Ranges from easy to setup to very difficult, depending on chosen solution
Most solutions take care of themselves Many solutions require constant security updates
Spam policed by the community Spam policed by the blogger
Publishing very easy, no html needed on some platforms (like Wetpaint) Publishing very easy, some html knowledge useful

However, I found Josh’s thought quite convincing as it answered my concern about authoring (one element of SLATES model) in the enterprise context.  In his blog post, Josh argued that one of the strong point of Wiki, “the free control over content” can lead to unaccountability, which can be solved by the “log-based management” of a blog (authority and responsibility of a blogger over his post).

From these arguments, I decided to continue to design a wiki for my department with more attention paid to content management, e.g. different levels of authority and revision tracking. A blog will still be applied, possibly for improving relationship with our users.


1 Response to "Wikis or Blogs?"

Great finding Thu. I always ask myself about this web2.0 applications. I also wonder that creating a blog page or wikis are not hard for some people, but it’s not that easy for some. WIll it be great if you can provide a guide or instructions to create a wiki for example? Thanks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Library 2.0

August 2009
« Jul   Sep »

Twitter Updates

Error: Twitter did not respond. Please wait a few minutes and refresh this page.


RSS Enterprise 2.0 Community

  • An error has occurred; the feed is probably down. Try again later.
%d bloggers like this: