Skip to main content

The Many Avenues in A Communications Job

Organizations want their communications people to be well-versed in every possible avenue affecting communications, such as:
  • communications strategy, planning & implementation
  • writing, editing, managing written materials
  • issues management, crisis management
  • internal & intranet communications
  • public relations
  • media relations
  • promotions, publicity
  • development & production of creative materials
  • marketing
  • visual communications & graphic design
  • web development & design
  • social media
It's not until you arrive at your position and see where the organization's needs really are and what they want to emphasize in practice that you truly know what you'll spend most of your time doing. 
For example, I was hired to do a communications job where I thought I'd being doing things like: 
  • Developing strategies and plans
  • Writing key messages for senior executives and management
  • Issues management & briefings
  • Communicating with employees on behalf of management
Instead, and after a number of months, I realized it was more of a tactical marketing job where I did things like:
  • planning campaigns for promoting programs with stickers, bookmarks & postcards
  • designing posters, flyers and digital screens
  • buying advertising
  • promotion through social media
These ah-ha surprises are not necessarily a bad thing, in fact, the multiple avenues of activity in communications jobs can boost your marketability for the next job, as you learn new skills and grow in new areas.

As a communications rookie, it's important to have a jack-of-all-trades versatility in all of these areas to be able to smoothly move between platforms, disciplines and activities so employers see your value. 

Comments

Popular posts from this blog

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...

"We can't tell them that."

The scenario: A project is delayed. Employees haven't heard any updates in about a month and the manager realizes he's 'got to get something out soon' because his boss has been asking what's going on. Manager:  I need a draft message for the project update. How soon can you get it to me? Communications Officer:  How about tomorrow? Manager:  I kind of need it today some time. Communications Officer:  How about today? Manager:  Okay good.  Communications Officer:  So the reason for the delay is other projects took priority but now it's time to return to this one, right? Manager:  "We can't tell them that."  Communications Officer:  Why not? Manager:  Well because it looks bad. I hear those words from a senior manager or executive and sigh. There are precious few things we truly "CAN'T" tell employees: private information about other employees financially-sensitive information the CEO's kid's cellpho...

How to Manage Document Version Control During Communications Campaigns

You've spent all this time working to get your communications right--whether you're the client, the manager, or the communications officer--and suddenly you see an 'older' version when the director sends out his/her message or it shows up on the corporate website. Then you swear out loud and realize that the reason you're seeing one of the changes from several versions ago is because someone made a boo-boo and pulled up the wrong non-final version. This is going to happen. In Communications work, we see a lot of versions of numerous documents via email, especially, causing challenges for version control. For these very situations, I purposefully have the following file naming convention so people know they have the latest version.  I "time-stamp" them. That means when I did my 'save-as', I captured the date and time in the document's file name. I do it ever time. Always. And it has consistently saved my bacon. Also, by doing it th...