I also appreciate it when people take the time to write out goals and objectives for the project. Q: Can you describe the details you write to ensure that recipients will like reading your emails or project notes? But the report also needs to be posted on Trello because it’s an important part of our project documentation. So, to manage your communication platforms, you have to be aware of how each platform is used and what kind of information your teammates expect to find in each one. Even if this means you occasionally share duplicate information across platforms, it’s better to do that than not have the information where it’s needed. For example, if one teammate only ever communicates important information in Slack and uses “@channel” in every message, it quickly gets annoying and isn’t useful, and then someone else has to translate it to the project management tool. Loryn: The easy answer to this question is that good processes and documentation save time — if everyone knows where things are, people can get their jobs done faster, like the professional kitchen analogy I mentioned earlier. But more importantly, when everyone knows where to find the information they need and how to communicate, teammates feel more ownership over their work, and the conversation moves from “Where do I find stuff?” to “How can we do better?” Productivity isn’t just about getting stuff done; it’s about getting the right things done and making progress on your goals. To cut down on these, you need to do two things: Clearly document important information and make sure everyone knows where to find it. Q: What’s one thing people can do, starting today, to communicate more effectively with their co-workers, clients, or bosses?
Since lately I’ve been interested in small tweaks we can all make to improve our communication skills (even if we already pride ourselves on them), I wanted to talk with my co-worker Loryn Cole about the topic.
Loryn is Copyblogger’s Data Analyst, and we share a similar style when it comes to communication.
Some might call it over-communicating.
We call it avoiding miscommunication.
Here’s my conversation with Loryn about successful communication in the workplace.
If you’d like to get more “You rock!” email replies from your co-workers, clients, or bosses, check it out.
Q: What elements make up the type of emails or project notes you like reading?
Loryn: I tend to like emails and project notes that have two seemingly contradictory qualities: They are clear and concise, but also comprehensive and wide-ranging.
Good project communications use as few words as possible to communicate what’s important, but they also make sure to cover all the important details.
The writing is brief, but the content is thorough.
I also appreciate it when people take the time to write out goals and objectives for the project. Too often, we assume that these are obvious to the people involved — and maybe that’s true some of the time, but it’s definitely not true all the time.
If you don’t write anything else about a project, write down your goals, strategy, or objectives, because, if you missed something else, these will help your teammates fill in the gaps and take ownership of the project.
Q: Can you describe the details you write to ensure that recipients will like reading your emails or project notes?
Loryn: I can’t say for sure whether or not other people like reading my emails … But, I can say that I do my best to make them easy to read. This means using lots of punctuation and formatting instead of full sentences, and always breaking up paragraphs when they get longer than two to three lines.
Writing emails always reminds me of that Mark Twain quote — “I didn’t have time to write a short letter, so I wrote a long one instead.”
We forget that writing a concise and useful email or project description takes work.
You can’t expect your first messy draft of notes to make sense to the person who needs to execute on the project.
Slow down, take your time, and empathize with the person who will need to take action on your words.
Q: Do you have a process for reviewing your written communication before you send or post it?
Loryn: Not particularly, but I do try to limit the work that the next person will have to do by making sure to link important resources and documents.
For example, if I reference a document, I link to it, or at least tell them where to find it.
And, of course, I review what I’ve written for clarity, grammar, readability, and thoroughness.
Q: How do you manage all the different ways you communicate at work (email, Skype, Slack, Trello, etc.)?
Loryn: Each platform serves a different communication niche, which means that sometimes you have to double-up.
For example, when I finish a report on one of our completed projects, I add the report to the Trello card, then also send the report to the team on Slack with a short summary.
I do this because Slack is generally a better medium for getting faster interactions — ideally, I want people to read the report (or at least the summary) and ask me questions about…
COMMENTS