I started asking people (later) how I could improve my messages for a better understanding. Some admitted they skipped my messages, some pretend it was confusing (but we're clear they didn't read) and some actually provided good feedback.
As everything, it needs to be adapted to the public, so in the end what I try to do (not for everything of course) is breaking and formatting long messages in a way that is easier for people to get the piece of information they need.
In some cases I also update the original message (making it easier to digest for the next person). It's helpful when someone just tags you in a thread with a lot of messages and you need to read them all to get context.
Interesting point about updating original messages, never thought about it.
I had that problem too, but in the last couple of years I improved a lot. I mainly asked senior executives, who communicated in a way that impressed me. Concrete suggestions about specific messages helped a lot!
Last week I was discussing something and an engineer was sharp and concise. It seemed he was clear on how things worked, but I had my doubts after reading some docs. We jumped into a call and then I could see how he was not so clear about it.
I think expressing our intention in writing is important. Otherwise, someone replying with a question can be interpreted as 1) A genuine question, 2) A rhetoric question humiliating you...
I've received answers like this from engineers in the past, but during freelancing, I've worked with many different teams and cultures.
Most of the time, I work with developers (for now), and it hasn't really happened that a simple: "I think you've missed one step in my message: X Y" wasn't enough. But all the examples you gave for overcoming this are great!
“I think you’ve missed one step message” is a better and softer version, but can still be interpreted as condescending.
I think it’s more critical in communication between people of different statuses - if it’s 2 engineers on the same level, it’s much less critical. If it’s a support rep / CS and engineer, or a junior/senior communication, those nuances become more critical.
I started asking people (later) how I could improve my messages for a better understanding. Some admitted they skipped my messages, some pretend it was confusing (but we're clear they didn't read) and some actually provided good feedback.
As everything, it needs to be adapted to the public, so in the end what I try to do (not for everything of course) is breaking and formatting long messages in a way that is easier for people to get the piece of information they need.
In some cases I also update the original message (making it easier to digest for the next person). It's helpful when someone just tags you in a thread with a lot of messages and you need to read them all to get context.
Interesting point about updating original messages, never thought about it.
I had that problem too, but in the last couple of years I improved a lot. I mainly asked senior executives, who communicated in a way that impressed me. Concrete suggestions about specific messages helped a lot!
Very easy to misinterpret things in writing.
Last week I was discussing something and an engineer was sharp and concise. It seemed he was clear on how things worked, but I had my doubts after reading some docs. We jumped into a call and then I could see how he was not so clear about it.
I think expressing our intention in writing is important. Otherwise, someone replying with a question can be interpreted as 1) A genuine question, 2) A rhetoric question humiliating you...
Nice article, Anton!
That’s a good example. As we go more and more towards remote and asynchronous work, such mistakes are increasing.
I think the minimum we can do is be more patient and respectful - and as you said, communicate our intent clearly.
Great stuff, Anton. No doubt, this is a problem.
I've received answers like this from engineers in the past, but during freelancing, I've worked with many different teams and cultures.
Most of the time, I work with developers (for now), and it hasn't really happened that a simple: "I think you've missed one step in my message: X Y" wasn't enough. But all the examples you gave for overcoming this are great!
Thanks for sharing this!
“I think you’ve missed one step message” is a better and softer version, but can still be interpreted as condescending.
I think it’s more critical in communication between people of different statuses - if it’s 2 engineers on the same level, it’s much less critical. If it’s a support rep / CS and engineer, or a junior/senior communication, those nuances become more critical.