Skip to main content

What do you do? Communications. Huh?

One of the things I've noticed over the years about working in Communications is the lack of understanding of what it is we do. It goes from zero idea of what 'working in communications' means to 'but what is it really that you do?'

I suppose over time I have had to learn what it all means, too. I recall asking the difference between communications and marketing in a communications class at University of Ottawa. I'm not sure I can recall the answer, but I do recall the indignation of my fellow students who could not believe I'd ever consider the two the same function.

There is much variety in the profession, and there is even more interpretations.

I have heard or overhead people refer to Communications as the following:
  • marketing
  • media relations (some people believe media relations to be writing press releases. some of those people actually work in communications, too.)
  • public relations (some people have difficulty explaining the differences between media and public relations! and some people can't make up their mind what the differences are.)
  • advertising
  • writing stuff that isn't true
  • telecommunications
  • managing websites
For some reason, if I say, 'oh it's like marketing', then they know what that means. 
Or, if I say media relations, that, too, gets a comprehensive nod, but the term communications is simply too broad and too vague for numerous folks to appreciate my job. I can't say that I do a lot of writing because that doesn't explain it either--even though I do tend to do a lot of writing. 

Perhaps the easiest way to describe what I do is to say that I help organizations figure out what to say, when and how to their employees and to the public. I often get a blank stare in response, not because they don't understand; they just can't fathom that this could be or is somebody's job. Don't organizations know what to say and when to say it to their people? Isn't that common sense?

I agree. It is common sense...to me. But when you run an organization, sometimes you're either too close to it to see the bigger picture or you've not had enough experience to realize the fallout of certain communications faux-pas. It's always better to double-check with a professional.


Comments

Popular posts from this blog

If You Clarify, There's No Need to Explain

Clarifying is not the same as explaining. Let me explain. No, wait: let me clarify that...which is it? When I hear the word 'explain', I envision multiple paragraphs of additional text that may not be necessary. Whereas the word 'clarify' evokes a beautiful landscape of writing where every word means something and no word can be left out. In the meantime, yes, 'clarify' and 'explain' are synonyms, which means they are similar, not exactly alike. In the context of writing well and writing to engage, I recommend clarity over too much explanation; perhaps that's a better way to put it. If anyone needs me to clarify that, let me know.

Dear Executive: Say What You Mean

If you read Clare Lynch's article called: " 10 Ways to Protect Your Copy from A Verbose Exec ", you'll see the following sentence: "There's nothing worse than some verbose exec "improving" your finely crafted copy by inserting references to "delivering key learnings," "driving employee integration strategies," and "interfacing holistically with clients." If you're anything like me, you actually want to tackle rewriting those mucky terms she's highlighted. Let's start with the first one: delivering key learnings. The word 'learning' is a noun; that's not the problem. When you put an 's' on it, you are attempting to count an abstract concept like learning, and that causes confusion. Allow me to give you an example:  Merriam-Wester defines learning as: "knowledge or skill acquired by instruction or study." You do not typically count the number of knowledges you've acq...

What did I say yesterday?

Look at what messages have gone out before communicating new ones. A huge mistake managers often make is to communicate new messages without reviewing what they've already said on the subject in the past, hoping no one will notice. Imagine how far a politician would get using that approach. Unfortunately, we can imagine it all too well. The mistake is not in forgetting what you've said before; with all the messages coming from the CEO, the website, from various marketing and customer service campaigns, it's no wonder we cannot remember what we said yesterday. However, it is our job to either know or find out exactly how we characterize our messages and what we share, even long after we've shared it. For example, if you tell your team to focus on continuous improvement and then a week later, in a weak moment, yell at someone for taking too much time to reevaluate a process, you'll lose trust and credibility--probably two of the most important badges...