Emails need to be refactored
I just read a long winded email from a colleague. I had to read it several times and still had trouble extracting "the point". A long three paragraph email could be boiled down to four short bullet points. It occurred to me that as a programmer, I may be more susceptible to frustration. I spend all day trying to avoid this in code. Do you re-factor your emails before sending? How do you deal with others that don't?
5 comments
[ 1.9 ms ] story [ 24.9 ms ] threadAnd just like excellent code when you see some great writing you tend to think 'that looks amazingly simple!' but when you attempt to produce the same sort of elegance it somehow isn't so easy!
How to deal with it: accept you can't change the world, move into a position where you have the freedom to ignore e-mails when you like, get good at scanning!
i do my best, when i'm about to communicate an idea in any form, to condense, polish, and qualitatively validate the idea/message/whatever before i actually communicate it, whether that means actually verbally saying the words, or hitting send on the email. not everyone will understand my internal dialog. you have to translate your thoughts into a real-world message before it gets sent.
dealing with others that don't? ask questions and take notes if you have to. other than that, you just have to adapt to understanding other people's brain dumps if they can't filter them on their own. look for topic sentences and latch onto them.
Hmmm, instead of typing out free form text, just click on certain verbs, adjectives, and nouns to get across your point. Kinda like xml for humans. The possibilities are endless.