Wiki vs Email Reply-All Dive into Information Technology http://stefanopedone.wordpress.com

Reply-All Approach In a corporate scenario, collaborative processes of reviewing docs or handling exceptions are often based on Email Reply-All approach.

In a corporate scenario, collaborative processes of reviewing docs or handling exceptions are often based on Email Reply-All approach.

Reply-All Approach

Reply-All Approach Result: “ Occupational Spam” (Gartner) http://www.flickr.com/photos/63056612@N00/

Result:

Email PROS: Simple & popular; It’s more “push”  more involving Through qualified technologies (e.g. Blackberry) In the way of perception (it’s sent to me!)

PROS:

Simple & popular;

It’s more “push”  more involving

Through qualified technologies (e.g. Blackberry)

In the way of perception (it’s sent to me!)

Email CONS: Hard conversation management; Getting lost is easy! To:/Cc:/Bcc: not a good way for differentiating roles in participation ;

CONS:

Hard conversation management;

Getting lost is easy!

To:/Cc:/Bcc: not a good way for differentiating roles in participation ;

Wiki PROS: Centralized history of variations; Knowledge is not scattered; Policies of role management;

PROS:

Centralized history of variations;

Knowledge is not scattered;

Policies of role management;

Wiki CONS: Less effective than mail in more “personal” collaborations (2 or 3 participants); Simple but less popular: training is necessary; Generally, no manageable lock policies for control of concurrency;

CONS:

Less effective than mail in more “personal” collaborations (2 or 3 participants);

Simple but less popular: training is necessary;

Generally, no manageable lock policies for control of concurrency;

Wiki+Email: a possible solution Integration of wiki and email might be a solution However, some requirements must be satisfied http://commons.wikimedia.org/wiki/Image:HNL_Wiki_Wiki_Bus.jpg http://www.flickr.com/photos/warmnfuzzy/464484822/ +

Integration of wiki and email might be a solution

However, some requirements must be satisfied

Wiki+Email: a possible solution You should be allowed to: Receive email notification about a topic or discussion; Post a new item, or modify an old one, by email; Subscribe to the history of a document by RSS; Manage levels of participation (Editor, Author, Guest, etc…) and related security policies; Manage lock policies for control of concurrency; Set which information is public and searchable;

You should be allowed to:

Receive email notification about a topic or discussion;

Post a new item, or modify an old one, by email;

Subscribe to the history of a document by RSS;

Manage levels of participation (Editor, Author, Guest, etc…) and related security policies;

Manage lock policies for control of concurrency;

Set which information is public and searchable;

“ that is the question” (from Hamlet 3/1) A product with all these features is still a Wiki … isn’t it? You can leave a comment on http://stefanopedone.wordpress.com ?

A product with all these features

is still a Wiki

… isn’t it?

You can leave a comment on

http://stefanopedone.wordpress.com