I often struggle with conveying more in lesser number of words. As a result, my slack messages often go in multiple paragraphs and bullet points.
I find a need to explain myself in detail, especially when trying to resolve some queries from other domains such as product managers and QA engineers. Are there some ways to make communication succinct and to the point, at the same time conveying what is necessary.
This was a feedback I have gotten once from my manager as well, though when I asked if he had some suggestions on how to work on the same, he mentioned - "Keep it short!" ¯_(ツ)_/¯
Now, I try to vet my messages after I type them before sending, but thinking if there are some ways to improve on it further.
I really like this question as I believe it's pretty broadly applicable among software engineers, and in fact, it's something I've struggled a lot with myself.
First, I recommend the following resources on high-quality technical writing:
And here's my advice:
Here is how I may restate this question:
My slack messages are too long.
How can I shorten them while retaining detail for PMs?
The only feedback my manager gives me is "Keep it short!"
I now review my messages, but would like to improve.
Often I find value in omission. If somebody wants to know more, they ask.