Right before we finally gave up, I went back and looked at all his interview communications. As part of the interview we would exchange several e-mails to see how their communication was, because we lived and died by e-mail with clients. All those communications were totally on point.
So I asked him: Why were your e-mails before we hired you so good? "Oh, my wife wrote those for me." So I'm sitting there thinking "We should have hired your wife."
All of the jobs I have ever interviewed for casually listed "great oral and written communication" as a skill in the job reqs. I have felt that I had a problem in this area.
I have worked as a remote contractor off and on for most of my life and have never run into an issue.
For the past year and a half I have been on a remote team.
It wasn't until my team lead, who did all of the oral and written communication, left, this past month, that I was placed in the position to pick where he left off.
It became immediately evident how poor my skills are in this area. I know that I am a poor communicator, but I didn't realize just how insufficient I was. Not only grammar and spelling, but conveying complex subject matter in a succinct way for folks lacking detailed domain knowledge. This is a problem!
Regardless, there is hope. How do you get better at writing? Write more. At least that is what I am told. I am now chomping at the bit for long-form writing opportunities to get experiencing it putting thoughts and plans on paper, as well as, using a new SaaS app to commit/tracking writing 5 minutes a day.
Any and all tips are welcome.
2) Writers write. So write more. The only actionable advice I ever got.
I used to devour howtos like Bugs In Writing. https://www.goodreads.com/book/show/601222.Bugs_in_Writing
Once I felt confident that I'm saying what I meant to say, I think I stopped. I should probably revisit the classics for a refresher.
3) Simple is harder. Explaining complex stuff is a ninja power. Just keep at it.
4 bonus tip) Proofread, edit stuff you wrote 3, 6, 9 months ago. Consciously note how your writing skill and voice have changed.
Unselected, ungoverned, training, can simply reinforce bad habits.
Structure, meaning, flow, logic, and engaging the reader the most difficult.
Logic and rhetoric over grammar.
(sorry for question instead of tips)
"conveying complex subject matter in a succinct way for folks lacking detailed domain knowledge."
FWIW, I didn't have the same confusion about the post, so I don't know how lacking the author is in this specific setting.
But I have had the same general struggle.
I have an MA in English/rhetoric and am a software dev, and even with that nexus of training it has been a lot of work to get better at communicating... the struggle to communicate technical issues to non technical people is a lifelong journey with a complex path. It's just hard.
So here's my tip:
smaller sentences. More paragraphs. Simpler language.
And IME we do best when we develop a continual awareness that although communication is difficult, it is possible.
I've also found thinking about sensual clues to be helpful, e.g. what would the user/customer/whatever see (or hear or feel) at this point? What (exact) text would they reasonably anchor on based on everything they might see? I also try to visually distinguish different types of info, e.g. exact text of some kind of UI element, code.
Another really helpful tip is to confirm that the user/customer/whatever sees/hears/feels some (exact) specific thing at a specific { step / point in space-time }. If they don't provide the (near) exact response I expect, I try to notice my confusion and debug right then and there until my confusion is resolved.
If you abstract it, the general form is something like "work with concepts that your audience is already familiar with", which is good advice for any communication. And, similarly, be on the look out for any data that says your communication has started to go awry.
I believe there's two important key points: confidence (but not overconfidence) and empathy/sympathy. Putting yourself in the other person's shoe and figuring what they need to hear ie. not what you want to express. The latter is secondary!
Sure, you can practice it, but only so much. I have autism, and I'm utter shit at this (even in my native language). I've been practicing it pretty much all my life (I remember having issues with it at elementary school). I'm terrible with being to the point and keeping communication short. And if it is short, its usually too rude.
I encourage you to not criticize yourself too harshly.
Regular chatter in public chat channels seems sufficient. What really seems to matter is work ethics.
I don't know where exactly the bar is, but a sentence is certainly below it if I can't figure out whether someone told me they did X or they are asking me to do X.
Regular chatter might be good enough to communicate between people in roughly the same timezone. However, If I send an unclear chat (or email) to a colleague who's starting her day when mine has already ended, she can't act on my message and we'll have to waste another day clearing up that miscommunication.
And how are these hypothetical poor communicators performing at non-remote jobs, anyway?
That means your teammates' communication skills are sufficient! Congratulations.
> What really seems to matter is work ethics.
I disagree. Work ethics mean nothing if you don't understand the work that needs to be done, because the problem or the approach is not communicated clearly.
effective reader too. One should be able to quickly make sense out of several hunbdreds of email messages, otherwise it will end up in "synchronous mode" -- dozen of messaging windows opened at every moment.
I have a business partner that I can talk to very effective in person. I had to relocate, and now we have to deal mostly via email. I have been working remotely for ten years now and saw no problem with the change. But it has become disastrous. I figured out that he is just not an "email type". Only picking up the phone works with him, but this does not fit into my workflow. I'm undoing our business partnership currently.
Picking up a phone for voice calls is synchronous.
Responding to an email is asynchronous.
(The asynchronous advantage is probably why SMS texting & WhatsApp/FB messaging has overtaken voice calls.)
I had a friend that didn't use email and always called my phone. Whenever I shut off the ringer, he'd eventually send me an email. But the content of that email was always, "Hey I got no answer on your phone. Give me a call."
Argh!!! Why can't you just put your question directly into the email?!? My behavior of not answering his phone calls failed to "train" him to switch to the email mode of communication. It drove me crazy. I finally realized that some people in this world have brains that work better with voice calls. Unfortunately, that's incompatible with the way I like to work.
I'm not saying that this guy was thinking this through that extensively, but IMO there are times when a voice call is more effective.
Did you attempt to explain to him why you didn't answer the phone as opposed to trying to "train" him? i.e. engage in open communication and have a conversation about what works and what doesn't for each of you about various modes of communication.
His request for you to "give him a call" moves thing for you back into the realm of the asynchronous.
I wonder whether maybe you have some other issue with voice calls?
I agree that voice calls can sometimes be more effective. Some types of tech support debugging are much easier with the interaction of live phone calls.
Those weren't the type of calls my friend was making. His calls were banal questions like, "I'm looking at these cameras the Canon 10D and Nikon D70. Which do you think is better?" He could have just typed that question into an email for me to reply whenever it was convenient. Instead, I hold the phone to my ear while I'm googling "Canon 10D vs Nikon D70".
>Did you attempt to explain to him why you didn't answer the phone as opposed to trying to "train" him?
No, I never told him in blunt terms, "don't call me anymore unless it's a complex question that requires the advantages of voice communication." I was hoping that dropping a ton of hints would do it but it didn't work. In any case, I changed my number so it's no longer a problem.
>His request for you to "give him a call" moves thing for you back into the realm of the asynchronous.
Not really because what ends up happening is after I call back, his brain says, "jasode is available now" and he'll call 5 or 15 minutes later with a new question. His threshold for initiating phone calls was very low which put me back in synchronous hell.
>I wonder whether maybe you have some other issue with voice calls?
Well yes, as I mentioned earlier: it's not my preferred form of communication. I do acknowledge and respect the fact that others default to voice but that doesn't change the fact that it's incompatible with how my brain works.
There is clearly a disconnect between people who prefer different modes of communication since the gp poster (throwawaymath) seemed truly confused and therefore asked, "Why doesn't picking up a phone fit into your workflow?"
I had a pretty poor team leader a few years ago with a bums in seat type job. He would never write anything down and teh result was quite frustrating. The spec used to change frequenty and he would come and verbally tell me it. then he would change it again, then again. A week or two later when I actually got around to implementing teh said feature I would ask him what he wanted done,
"I thought we talked about that." "Yes we did but you changed your mind 4 times and I can't remember what the conclusion was."
I used to regularly ask him to put things in writing, but he was usually to lazy to deliver on that.
So I don't think these problems are unique to remote teams.
Another insists that if it's not documented, it didn't happen.
These challenges have confounded me all my working life.
My few truly positive working experiences happened when there was mutual trust, regard, esteem. First time it happened, I was gobsmacked. I'd read about trust, but had never seen it IRL. It was a never ending warm fuzzy bath of shared awesomeness.
I still have few ideas how to find, nurture, create trust (especially in a chaotic env). But I now know it when I see it. And when I'm not feeling it, I mostly just go thru the 9-5 motions, keeping my expectations and investments lower.
Then, if nothing is written down anywhere, I'd just sum up what I am going to implement (email, wiki, internal docs, readme whatever) and send it to anyone involved.
Check mate for for control-freak-undecided-colleagues. :)
"Ok, we're all here. Wait, where's Mike?"
"I think he was making coffee. Let's wait for him."
"Hey, is Zhang saying something?"
"Zhang, say something."
"..."
"I think your microphone is broken."
"Can you disconnect and reconnect?"
"Hey, he's typing something. I... will... reboot. Ok, let's wait for him to reboot."
"Hey, Mike's back. Someone tell him we're waiting on Zhang to reboot."
"I don't think he can hear us."
"Guys, I'm gonna go grab a coffee while Mike and Zhang figure it out."
In the context of this conversation around remote only companies though, everyone is going to be set up to be able to properly participate in a video call - that means making sure everyone has a decent internet connection, microphone, and camera at home. When people aren't at home tools like Zoom have the ability for them to dial in to conferences on a regular phone which deals with the remaining problems.
I've worked mostly remote for many years and please trust me - it's almost exactly the same, with every weekly meeting starting with "is everyone here", "do you hear me?" etc etc.
This is especially when working from home - typical residential connections are having less nicer SLA and may get flaky from time to time. And someone may leave their phone near mic cable. Or someone's machine may need rebooting. Or conferencing service may be experiencing problems.
Glad if it's not like this for some, but I believe it's not exactly uncommon.
Being late or grabbing coffee instead of starting a meeting are culture problems at a company, not problems with the medium.
You've had better luck than I have. Our New York team is still dealing with the problem of the Boston office being virtually inaudible, while Dublin sounds like they're speaking through a megaphone directly into my ear.
That is, assuming we didn't lose a room, or the Hangouts equipment isn't broken - then Boston uses our manager's laptop, which actually sometimes has better sound quality.
I don't do standups anymore, but at my last company, they often took about 5 minutes from dialing to hangup.
Do you have an opinion on what aspects of written communication are the most important for remote work?
Just gathering ideas to write about! :)
It's such a different skill set though compared to in-person communication, where much of this happens non-verbally. I think it's a lot easier for people who grew up with it. I spent a lot of time on MUDs and BBSs when I was younger, where this kind of communication was prevalent.
Basically this boils down to how strictly you cling to new buzzwords.
I used to work remotely as a freelancer and I miss it so much. I now work in-house at an agency and everyone here fails so miserably at writing. Almost all discussion is verbal, nothing is documented and so much double-work happens it's not even funny.
To make matters worse, the agency doesn't use any project management software. So all projects have seemingly imminent deadlines. It's miserable.
If our team was more apt to learn, adapt and document more, we'd probably be a lot happier.
Emacs needs more effort but it is an achievable goal. Very customisable so you could even ask somebody to create your own comands and circumnavigate the hairy parts for a lot of time until building enough confidence. Finding a good tutor or having somebody interested in the program in your company would help a lot, obviously.
not just remote - any and all work will be miserable. I work remote and in person with lots of people who will not write things down. When I call them on it, they say "I'm not your secretary" - but they are happy to have everyone be their secretary.
If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.
People who are not highly fluent in the company's written language or those with some level of dyslexia will struggle. Also some people get frustrated with the more analytic approach required by text, relying instead on spoken rhetoric.
I think even if you're colocated, there are huge benefits to following the remote work practices and improving your written communication. Documenting your work in an issue manager and using chat primarily for communication means no one will miss out, even if someone is sick, a new starter, or on a different team. All these things can make a dev organisation much more effective and break down silos.