The Three Rules of Stress-Free Email
Nobody tells you how to handle
Working on the assumption that what I've ended up with might be useful to others, here's how I do email. I'm only dealing with incoming messages here. There are many other fine articles on the web delving into the art of crafting an elegant, effective electronic message. Also, this is for
First of all, don't even call all your email "email." The term has hidden connotations and expectations of responsivity. The truth is that only a tiny fraction of the messages in your
Rule #1 (The Golden Rule)
Before we get to nuts and bolts we have to lay down the overarching principle. And that is: your inbox and how you deal with it must reflect your professional goals and priorities . Which is to say that you have to categorize your email by where it falls in your professional pecking order. Usually, it goes something like this, from most important to least:
- Messages where I am explicitly on the "T" line . This means it impacts my day-to-day work, helps me make progress on what I'm doing right now, or I'm expected to respond in some way. The response could be simply chiming in with an opinion that others will take into consideration, or a straight answer to a straight question, a clear decision, or... something else. If it's something else, then email might help you get to the bottom of it, but you will usually need something stronger, like IM, video chat, or even a face-to-face to truly resolve it.
Messages to my team's mailing list
The hubof most modern teams' day-to-day heartbeatis their mailing list. I'm not going to be explicitly on the "T" line here, but the expectation is that every team member peruses this at least a couple of times a day to stay abreast of what's going on in their immediate professional environment. Is the build broken? Did someone send out a new design for review? Look at this massive change coming down the pipe!
- Messages to the mailing lists of teams that my team interacts with. These might be teams whose work you build upon, or those who build on yours, company-wide infrastructure, ops etc. Occasional perusal (a couple of times a week) is all you need here.
- Everything else . This is just organizational atmosphere. Usually not even technical. And if something really big happens, you'll probably hear about it before reading the email.
There are a couple of other ground rules if you are to stay sane while dealing with the hose of modern email.
Rule #2: Email is a Terrible Place For a To-Do List
I really don't get how one can tack on GTD to email. An email is not actionable. Once you read it and understand it, you might end up with a clear action, but your inbox is not the place to shove it.
Rule #3: Email is Not the Place Where Other People Get to Create Work for You to Do
I suspect this is the primary reason everyone is so stressed out by email. If every message is a chunk of work falling on you, no wonder it drives you mad. It took me a long time to realize this. The work you are supposed to do is discussed, clarified and assigned via other channels, usually chats with your manager. Email is for carrying out those predetermined responsibilities. Random people do not get to put tasks on your todo-list by simply sending you an email. You must hold a steady stance with this. If they do, you have to push back, politely, and clarify
Go do email. Don't
How I do email | Vivek Haldar
Vivek Haldar writes software for Google. Many years ago, he was a
Want to see your work on Lifehacker? Email Tessa .