The burden of communication is on the communicator; not the recipient.
Therefore proper email etiquette is to use strong subject lines, links, numbered lists and reasonably short paragraphs. Use these guidelines on how to write a decent email that might actually produce results.
Specifically emails must use:
Subject Lines – all emails need a well articulated and relevant Subject Line.
Examples of good email subject lines:
Client X going live on Tuesday July 29 before Friday Board Meeting
Training help file on email etiquette posted on schipul.com
Feast with the Beast Presale Facebook AD text (sent to the zoo)
Bad subject lines torture your coworkers with anxiety which lowers morale and greatly reduces profitability.
Every time an email is sent with a bad subject line, a baby seal dies. This is sad. Save the baby seals! Use good subject lines!
Links – ease of use changes behavior.
Ease of use changes behavior. Without links people will NOT click through to see the work that has been done.
It is rare that an email goes out that is truly not about SOMETHING that should be linked. Yes exceptions occur, but they are rare exceptions.
It is not your coworker’s responsibility to overcome your unwillingness to copy/paste a link from a site you are probably looking at when you sent the email!
Every time an email is sent without a link, a baby seal dies. This is sad. Save the baby seals! Use links!
Numbered Lists – organize the information
Bulleted lists are evil because they do NOT convey priority by the sender. Yet the recipient invariably starts at the top assuming this is in fact the top priority.
The value of forcing yourself to use numbered lists is that the sender (you) must organize your thoughts before confusing everyone else. It has been my experience that most people do not “order” bulleted lists but numbering makes them think about it.
Raise your hand if you like numbered lists! Now raise your other hand so things balance out. Or to put it another way – be kind to people who need this structure. It benefits you if people understand your message. Embrace diversity including “diversity of types of thinkers.” Structure and prioritize your content.
Short Paragraphs – with rare exceptions
Shorter paragraphs with strong subject sentences greatly increase reading comprehension.
Speed readers tend to read the first sentence of a paragraph and use that to make a decision if they should bother reading the rest. Shorter paragraphs means more of your message is consumed regardless.
They force you to organize your thoughts before wasting everyone else’s time!
Nickel words – save them for scrabble
To repeat – the burden of communication is on the communicator, not the recipient. While it is possible to write in tongues, this needlessly reduces comprehension.
But don’t oversimplify, just make it as simple as possible and no simpler.
We all value our time. You do. I do. Everyone does. So it frequently seems expedient to send an email quickly without thought. The problem is the person receiving these emails might be receiving 500 emails a day and there is no way to Get Things Done without more data.
For example assuming you – not putting a decent subject line – costs each recipient 1 extra minute of time to comprehend (if they give you this minute), then an email that saved you 1 minute, just cost a company of 30 people 29 minutes of billable time. This is very real money. And these are very real emotions on the part of the recipient.
Don’t be mean; take the time to write decent emails.
[Note: this was an internal company help file for years, I probably wrote it around 2002 or 2003. This is just me reposting it for public consumption.]
how to backup or backup and sync users in gmail using gmvault.
Mac or Linux – although I think on my Mac.
Best to do it in a virtual environment, by which I mean virtualenv
sudo easy_install pip
sudo chown -R venvs/gmvault
#make the virtual environment
# this just gives your regular user access to the directory tree because sudo gets old
sudo chown -R eschipul:wheel venvs
# You should now see (venv) in front of your prompt
# I had downloaded the file, which is hard to find BTW, to my Downloads folder so I had to move it.
mv ~/Downloads/gmvault-v1.8.1-beta-macosx-intel.tar.gz /venvs/gmvault/
tar zxvf gmvault-v1.8.1-beta-macosx-intel.tar.gz
./gmvault sync firstname.lastname@example.org
# you have two options – you can use oauth which I did. Or if you are doing a scheduled sync
# restoring a gmail account looks like this:
./gmvault restore MYNEWfoo.email@example.com
No, I am not trying to be rude. I am just trying to explain why I am not replying to your email. Please bear with me.
The Internet is made up of what most people call â€œlinksâ€. In fact these are really part of a name-space called Uniform Resource Locators. When you type a link the system ASSUMES â€œhttp:â€ or Hypertext Transport Protocol. But it could just as easily be telnet: or ftp: or https: etcâ€¦. The main point is that the link specifies both protocol and the EXACT uniform location. It is specific. It is a specific location.
In the scenario below you were having difficulty with several profiles and images on some site. I gather that from the partial names. My bet is that at the time you were having that difficulty YOU WERE LOOKING AT THEM. And above that page was a URL â€“ an exact reference to this exact and specific page. But you did not copy it. Rather you typed a long email to me with clues about the possible world you were in at the time.
So, to help you based on the email you sent I have to commit half an hour just to retrace the steps. Make a few educated guesses on where you were at. And I still canâ€™t be sure I am looking at the same thing. On a Monday morning at work. Awesome.Â Because you donâ€™t want to bother to copy/paste you are sending me on a goose-chase. For a technical person this is perceived of as rude because it is NOT NECESSARY. The message you are sending is that our time is meaningless in comparison to the time it takes to you copy and paste a link.
While you probably arenâ€™t trying to insult the technical people in your life, it is thoughtless at a minimum. And we have talked about this 9999 times. This is not the first time anyone has mentioned the importance of links. But you continue to revert to story-book requests for assistance. Sigh.
What I am trying to say here is it would be helpful if you sent me a link when you asked me to support some other companies web products that I didnâ€™t even program. If you want me to help that is. We discussed this before, no?
Lets start by pointing out that while email is efficient, it is a symbolic representation of what evolved as something much richer; face to face communication. The writing didn’t come first, speech did. And speech was part, just PART, of human communication. And any symbolic representation of an original is going to lack in quality.
A while back I wrote what was initially an internal use only help file on how to write a decent email. The summary is below but I’d encourage you to read the original help file on how to communicate effectively in an email. What follows is an addendum to that help file that is more about dysfunctional organizations than actual communication skills. First the original list in abbreviate form:
Subject lines – all emails need a well articulated and relevant subject line
Links – ease of use changes behavior so LINK to what you are talking about.
Numbered Lists – stop with the bullets. Use numbers so that YOU the sender can prioritize your own message!
Short Paragraphs – try it. They are good.
Nickel Words – save them for scrabble.
Additional considerations when writing an email.
Don’t delegate to the recipient unless that is your intent. Specifically avoid phrases like:
“Let me know” – a polite way of delegating to someone else the decision making power for the topic. And realize they have three votes; to confirm, deny, or just let it hang out there unanswered like a bill that doesn’t make it through congress. Regardless you are ceding all decision making power to the recipient to “let you know.” Probably not what you or the organization wants. On the other hand, “let me know” is a great way to avoid doing actual work so there is that.
The “I can do A or B or C. Which do you prefer?” – a common response to a task request that again avoids risk by delegating back to the sender the ultimate decision making power. Granted this is an appropriate response to micromanagers. But then again, if you work for a micromanager you have a whole different set of problems. Stephen Covey talks about the difference between gofer delegation and stewardship delegation. What high performing organizations need is Stewardship delegation capable people who can make decisions and complete the intent of the task more than the specifics. If you are delegating everything back to the sender, you might have fallen into a gofer mindset.
Don’t be rude.
NO SCREAMING!!!! – enough said. I don’t care who you are. If you can type, you can hit a key, and the shift-lock is just another key on the keyboard. No screaming please.
“Thank you in advance” – arguably the rudest, most passive aggressive way to end an email. Typically people resort to “thank you in advance” after years of “let me know” fails thinking it will lead to greater accountability. Instead, you just piss everyone off with an implied “do it or die” type of ending regardless of having the authority to require compliance by the recipient. Best strategy to handle “thank you in advance” closings? Ignore the email. Or if you know the person at a friend level, pull them aside and say “really, do you mean to be rude every time you finish an email?” (Side note: yes I realize this is common for Spanish speakers, but it is a cultural difference that doesn’t translate well into the American culture.)
No pre-excuses – the book Absolute Honesty talks about pre-excuses. People who say repeatedly “I’m not good with technology” over and over so they can pre-excuse themselves to not try to fix their own email problem. What a pre-excuse does, quite well actually, is prevent you from doing the hard stuff and forcing your coworkers or friends to do the hard stuff for you. Very Zsa Zsa Gabor, good work if you can get it, but for most of us we need to stop the pre-excuses and do the hard work and not delegate it to our friends just because they don’t call us out on our pre-excuses. But again, in a dysfunctional organization, pre-excuses are a another great way to avoid actual work.
No Comic Sans. OK, I can’t prove there is any correlation between comic sans and a decrease in productivity, but I will say nobody will take you seriously if you send emails like a 13 year old into kittens.