|
|
Thematic Core - Apps Team meaning and scope of Collaboration
belongs to Apps Team ![]() by Brittain on Feb 15, 2008 - 09:11 AM read 779 times |
Updated: July 24, 2008
As most of you know, we have software IP in the "collaboration" space. We threw together this following diagram as a guideline for the features we consider for that space.
Comment away.

-
re: Thematic Core - Apps Team meaning and scope of Collaboration
a reply to Thematic Core - Apps Team meaning and scope of Collaboration
by Luna Flesher on Oct 10, 2008 - 04:21 PM read 49 timesThis graph does a good job of capturing the various metrics of internal communications. I think it should include traditional (non-technological) Protocols like Face to Face. I think it would also be useful to include specific "applications" of the merge between Styles and Protocols, i.e.:
Brainstorming + Web = Yammer/Twitter
Document Sharing + Web = Knowledgebase
Private + Email = Email
Then you can start to see crossovers, like:
Private + Document Sharing + Web = Knowledgebase
I also see a need for a metric that expresses whether something is structured/unstructured, formalized/unformalized, self-organizational/top-down.
For instance, on the Reality protocol, you can have informal brainstorming one-on-one face to face (water cooler talk or someone drops by). Or you can have formalized (structured) brainstorming face to face (a scheduled meeting).
You can have a spontaneous discussion start up in Yammer (this) which is self-organized, informal brainstorming unthreaded over the web that changed to Threaded self-organized informal brainstorming over the web. :)
I think maybe one of the struggles for people is the ability or preference to access all these channels. I may prefer email and Twitter and IM. Other people like to drop by my desk and ask me questions. Others like to write blog posts and get feedback in comments. I may be interested in that blog post, but because of all these channels, I'll probably miss it.
Another struggle is what we're talking about here... how do we bridge the channels?
And then Time is another biggie. It's a nice idea to get everyone's input, or every interested person's input .. but not everyone is able to focus on everything at once. There are weeks I'm so slammed I can't even read The Buzz. Other weeks are slow, and I want to catch up on certain Hub threads or Yammer topics, but the party is already over.
The answer to these issues is where the magic lies. :)
-
re: re: Thematic Core - Apps Team meaning and scope of Collaboration
a reply to re: Thematic Core - Apps Team meaning and scope of Collaboration
in a conversation thread started here
by Brittain on Oct 13, 2008 - 03:05 PM read 50 timesThanks for the feedback Luna. Based on your examples I'd say you get the concepts the diagram is meant to organize. Here's some thoughts on a few of your suggestions:
- You're 100% right that there exist additional protocols (such as your example of Face to Face); however, they're probably best saved for another diagram simply because they are out of our scope. Perhaps another, more inclusive map showing a complete picture would fill that role.
- I agree about the need to identify "applications" that merge these concepts. Ultimately, I believe the value lies in the application of these concepts in concrete ways to known business pains. Part of what PM has been working on are exactly these sorts of uses.
-




