Good Messaging Is Worth 1,000 Pictures

Thinkshift recently completed messaging work for several clients, which got me thinking about what good messaging is all about.

Good messaging is credible and exact. It handles the communications task at hand, whether it’s a pithy quote from the CEO in a press release, a boilerplate description of the company, or the brand voice and framework for a report, presentation or website. A messaging document should provide messages that are as close to plug-and-play as possible, with examples for as many contexts as makes sense.

Good messaging gets used. Reporters use it when writing about the company. Partner organizations use it when they describe you on their website. Employees use it, not just in presentations and formal communications, but also on their LinkedIn and Facebook pages and when they talk about their work with friends. For one client, the test came with the release of significant company news requiring media outreach and a new partnership. It was extremely gratifying to see the messaging work take hold and appear in newspaper articles, customer blog posts and on the partner website. Meanwhile, employees used it on their LinkedIn pages and elsewhere.

This doesn’t just happen naturally. We don’t just create messages, toss the client a guide and expect them to get it right away. Introducing the messaging, explaining how to use it and when, showing examples and providing training for written and spoken use are key.

Good messaging is flexible. Messaging should be used consistently, but shouldn’t be rigid. It should grow and change with the organization, and be adaptable to the person using it, the communications vehicle, audience or a other factors.

The key test—and I find this especially satisfying—is whether people genuinely like the messages. They won’t unless the messages are written in natural, ordinary language, so that people are comfortable using them without rewriting. When that happens, employees and others become advocates. They are able to provide the right message and information succinctly.

And that kind of communication brings an organization to life. You can’t do that with jargon, corporatespeak or vague and imprecise phrases.

Tips for Writing Better Bios

We’ve been working with clients lately on bios/profiles for websites and backgrounders, and it’s reminded me of how difficult it is for most people to write about themselves—or even get comfortable with what someone else writes about them.

Faced with a bio request, people often retreat to the safe familiarity of resume-style recitations: jobs,  accomplishments, education. That’s not wrong; it’s just not great—especially for networking via social media. Ideally, a bio will evoke a real human (not some kind of business bot) and will communicate something about how you approach your work and what makes you stand out (note to modest types: there’s always something).

A few tips that can make it easier:

  • Have someone interview you (or your team)— it’s often easier to talk about we do than to put it in writing.
  • Develop a list of questions for bios (our colleague Kelly Parkinson has a great one here) and answer them stream-of-consciousness style. People often have a hard time writing because they try to edit while they write. Write first, then edit.
  • Think about (and write about) the ultimate results you deliver—not just what you know how to do.
  • Talk about why you do what you do.
  • Having a hard time pinning down that extra something you bring? Think about what others have said about  you—friends, a former boss, your mom.
  • Include something about what you like to do in your off time—it gives people a way to relate to you. And be specific: “I walk dogs for the SPCA,” not “I like animals”; “I’m addicted to gritty crime novels,” not “I like to read.”

In general, think about what you like to know about others; they want to know that about you, too. And try not stress about it. You may never get comfortable with your bio, but that doesn’t matter—you don’t have to read again until it’s update time.