Wednesday Sep 02, 2009

Ten Requirements for Achieving Collaboration #4:Enable The Humans

We are in the midst of a series investigating collaboration. We previously wrote about the two types of collaboration - intentional and accidental. INTENTIONAL: where we get together to achieve a goal and ACCIDENTAL: where you interact with something of mine and I am never aware of your interaction While intentional collaboration is good it is not where the bulk of untapped collaborative potential lies. Accidental collaboration is. But the challenge is to intentionally facilitate accidental collaboration. For the full list of 10 requirements see the original post. Last time I wrote about requirement #3: why usage and context patterns of information are so important.
meat.jpg
This week we continue the series investigating requirement #4 where we change gears a bit and move from our previous automation focus and consider the humans. After all it is we-the-meat that actually create and use information. It is the meat part of life which can transmogrify data to information to knowledge to action. So our topic is how and why human revisions of information, annotations to and classifications of information must be enabled and preserved.
Reblog this post [with Zemanta]<script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script>
[Read More]

Thursday Aug 20, 2009

Ten Requirements for Achieving Collaboration #3: Usage & Context Patterns

We are in the midst of a series investigating intentional and accidental collaboration: INTENTIONAL: where we get together to achieve a goal and ACCIDENTAL: where you interact with something of mine and I am never aware of your interaction
cabbage_sm.jpg
While intentional collaboration is good it is not where the bulk of untapped collaborative potential lies. Accidental collaboration is. But the challenge is to intentionally facilitate accidental collaboration. For the full list of 10 requirements see the original post. Last week I wrote about requirement #2: why the automated aggregation of content bound data is important. This week we continue the series investigating requirement #3 which continues on the aggregation theme: Usage and context patterns must be able to be automatically created, extracted, enhanced and preserved. It bears repeating that the reason we're spending so much time on aggregation is because it is in the aggregate that patterns and meta-patterns emerge that provide real intelligence that simply cannot be seen when looking at a single object. It is the difference between spotting "striking similarities" in two sets of DNA then pulling back and seeing that one belongs to a person and the other a cabbage. [Read More]
About

Enterprise 2.0 and Content Management

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today