Skip to main content

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 of honour you could wear, as a manager.

Francis Norman (@FrancisNorman) echoes some of my thoughts in his August 2010 article: Consistency of message in communicating to your team. He, too, notes the example of politicians needing to stay on message and how disasterous it is when they ignore what they've already said. Norman also points out that in the context of projects, while the results may be less 'public', it is just as important to stay focused on message and goals. And that means, reviewing anything you've said in the recent past on the subject first, and communicating second.


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