Re:Embracing Asynchronous Communication at Gitlab
by Tainnor on Friday October 16, 2020 @05:57PM
(#24805441)
Sure, that might work for simple questions. But sometimes you really need to ask a nuanced question, and then what?
Re:Embracing Asynchronous Communication at Gitlab
by teddyh on Friday October 16, 2020 @06:24PM
(#24805615)
I’d ask the question first, then explain it. Possibly ask the same question again after the explanation. If the question could/would be misunderstood without the explanation, I’d change the question to instead be confusing without the explanation. But you really have to work hard at being able to explain enough things with a very short text.
Re:Embracing Asynchronous Communication at Gitlab
by m0zg on Friday October 16, 2020 @10:36PM
(#24807037)
> Ask the single most important question as the first sentence
Exactly. And also, NEVER ask the questions you'd like answers for on Friday afternoon. Or any afternoon in general.
If it doesn't say what it wants in the first sentence or two, I'm hitting delete, unless the email is from my boss. And I currently do not have a boss.
You have to adapt. Ask the single most important question as the first sentence. Don’t write a lot of text after the question either – it would only make people feel they can put off reading it, and therefore put off answering the e-mail. Don’t ask an easy question later in the same e-email (people would answer that question only, and ignore the rest of the text). And so on.