opensource: del.icio.us tag/opensource
.NET
backup
collaboration
Windows
distributed
sharing
opensource
opensource: del.icio.us tag/opensource
Software
presentation
Web2.0
collaboration
sharing
Online
opensource
Eclipse: del.icio.us/tag/eclipse
eclipse
Programming
Editor
collaboration
sharing
practices
plugin
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!
Lately, a number of users have asked about auto-filling in Chandler on the Users-List. Rule-based filtering is an email feature many people can’t live without and it’s definitely something we’d like to see in the product.
Then, I came across Chris Brogan’s How I tamed my inbox. I’ve seen write-ups like this before, but this post really resonates with how Chandler is meant to be useful as a companion to email. Namely: Get important stuff out of email into a trusted system that has better affordances for managing the things you need to do. Chris Brogan’s trusted system consists of a lightweight filing system, a to-do list/project manager (Things) and a calendar (Google Calendar).
With Chandler, you get the to-do-list and calendar in one, integrated package
To quote Chris:
If any of my projects are time specific, I put that information into Google Calendar. I then set up the reminders along the way. Further, if the project is large or lengthy, I set up little milestone time frames such that I will remember to work periodically on projects all the way up to their due date.
Takeaways: Nothing gets done in a single sitting. The ability to see to-dos on a calendar is critical.
I have notes and details on a new conference I’m launching for marketers for September in the Boston area.
Takeaway: Keeping track of “notes about what I need to do” is just as important as keeping track of what I need to do.
However, I haven’t seen much discussion of sharing as a way to deal with “email overload”. Instead, too-much-email is most often portrayed as a personal information management problem.
Yet, email is first and foremost a communication tool, a way for groups to collaborate. If there’s a problem with email, it’s a group information management problem.
Ergo, sharing is very relevant to “email overload”. In addition to helping people deal with “too much email”, we can and should also be looking for ways to:
To be clear, I’m not saying that the solution is as simple as: Don’t email, just share! The point I’d like to make is more precise: Sharing is an important part of how we fix email, provided we don’t create yet another collaboration medium that simply generates more email!
Chandler attempts to walk this line and while there is always more work to do, we’ve already seen success in reducing email for our users. I will follow up with a more detailed blog post on how you can “Send less email” and “Spend less time managing email” with Chandler.
open-source: del.icio.us tag/open-source
Programming
collaboration
sharing
research
Projects
open-source
open_source
opensource: del.icio.us tag/opensource
office
desktop
OpenOffice
Web2.0
collaboration
sharing
Online
podcasting: del.icio.us tag/podcasting
Applications
Web2.0
collaboration
storage
tools
sharing
system:has:for