opensource: del.icio.us tag/opensource
Development
community
design
collaboration
tools
activism
opensource
opensource: del.icio.us tag/opensource
community
design
Web2.0
collaboration
opensource
marketing
cool
opensource: del.icio.us tag/opensource
Applications
community
design
blog
collaboration
opensource
webdesign
opensource: del.icio.us tag/opensource
Development
Software
community
CMS
design
blog
collaboration
Eclipse: del.icio.us/tag/eclipse
Development
eclipse
design
collaboration
visualization
Computer
foss
Development
Programming
design
collaboration
repository
cool
git
open-source: del.icio.us tag/open-source
Software
community
design
collaboration
education
research
system:has:for
Yesterday I lamented that I wasn’t seeing any discussion about how email overload is fundamentally a collaboration problem (as opposed to a personal information management issue).
Then of course, I immediately ran into this one.
So, is it true? Will a new generation of collaboration tools help us wean ourselves off email? (The same way IM and social networking have already weaned us off email for social interactions.)
We hope so.
This should be true if you’re just using Chandler for yourself. This is doubly true if you’re sharing with others because at its best, Chandler opens up an alternative, more ergonomic channel for collaboration that results in fewer bits of information to keep track of and allows the group to leverage individual efforts to manage and organize information.
Here are some lists of email characteristics we want to emulate and avoid in Chandler.
What we want to keep: Email doesn’t get in the way of your ideas!
Bite-sized means it’s easier to get started on tackling hard problems.
Bite-sized also means you can manage email like a task list (as many people do). This in turn helps you multi-task. You can start, develop, fork and resolve dozens of threads at the same time. You keep track of it all by flagging/filing individual messages. With email, big, intractable problems are conveniently broken down into bite-sized next actions.
What we want to avoid and improve on: Email begets more email!
The very qualities that make email the defining tool of the information workplace are also its Achilles heel. Email is too easy to send. Each email in turn spawns more email to the point where you can no longer see the forest for the trees and you need to create more bits of information to keep track of the bits you’re losing in email.
There are a dozen different ways in which Chandler strives to meet the ideal described above. We’ve already begun to see success stories of users moving their work from email into Chandler and we’re using them to help us become a better alternative to email!