This link has been bookmarked by 2 people . It was first bookmarked on 21 Aug 2009, by enterprise2open links.
-
Mark BlairWe 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. -
enterprise2open linksThe 2 Types of Collaboration series by Oracle's Billy Cripe is getting interesting - in #3 he's writing about usage and context patterns, what makes business intelligence 2.0 interesting and more.
I say it's not the data, it's meaning and the wisdom that comes from interpreting and understanding ... yes, we're talking about social acts here, benefits that are sometimes underestimated when thinking about collaborative performance - all the while clever thoughts here from Billy, who still manages to call all this ECM ;)
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.