As you might have noticed from my blog posts over the years, I like writing long essays. By long, I mean blog post long. Somewhere of the length of 800-1000 words. I can’t write longer than that, because of which my attempts to write a book have come to nought.
Now, thanks to regular blogging for over nine years, I think I’ve become better at writing rather than speaking when I have to explain a complicated concept. Writing allows me to structure my thoughts better, whereas while speaking I sometimes tend to think ahead of what I’m talking, and end up making a mess of it (I had a major stammer when I was in school, by the way).
Given that I like explaining concepts in writing rather than in speech, I write long mails even when it comes to work. Writing long emails is like writing blog posts – you have the time and space to structure your thought well and present it to your readers. This especially helps if the thoughts you are to communicate are complex.
The problem, however, is that most people are not used to reading long emails in a work contexts. People prefer to do meetings instead. Or they just call you up. For whatever reason, the art of long emails has never really taken off in the corporate sphere, Maybe people just want to talk too much.
This, of course, has never deterred me from using my favourite means of communication. It didn’t stop me when I was an employee and the people I wrote to were colleagues. It still doesn’t stop me now, when I’m a consultant, writing to people who are paying me for a piece of work. If they are paying me, I should communicate things to them in a form they are most comfortable with, you might argue. If they are paying me, I should communicate things as well as I can, I argue back, and my best means of communication is writing long emails.
The problem with long emails, however, is that, like long-form articles you send to a Pocket or an Instapaper, you tend to bookmark these long mails for later, intending to read and digest them when you have the time. So, when you send a long email, you are unlikely to get a quick response (note that you can sometimes use it to your advantage). This means that when you write long mails, you might have to follow it up with an SMS or a phone call to the effect of “read and digest and let me know if you have any questions”.
In my last organization, I worked with a number of technical people, some of whom had PhDs. It was interesting to contrast the way they communicated with my long emails. They too would put complex thoughts in writing, except that they would use Latex and make a PDF out of it. It would be littered with equations and greek symbols, in a way that is extremely intuitive for an academic to read.
And here I was, eschewing all that Greek, preferring to write in plain text in the body of emails. No wonder some of my colleagues started terming my emails “blogposts”.