△ MENU/TOP △

Holtz Communications + Technology

Shel Holtz
Communicating at the Intersection of Business and Technology
SearchClose Icon

Clear disclosure in 140 characters

The FTC’s freshly-minuted disclosure rules for bloggers and the companies that reach out to them may be sounding alarms among those who aren’t already disclosure-minded, but a lot of bloggers and companies have always been mindful of candor and honesty. Long before the FTC even began looking at governing a practice that PR people, marketers, advertisers and bloggers weren’t policing for themselves, some businesses (SHIFT Communications and Ogilvy PR) were promoting clear policies of disclosure.

But disclosure can be problematic, even among those with honorable intentions. How, exactly, should a blogger disclose a relationship with a company in such a way as to satisfy all possible readers (and, now, the government)?

Twitter makes it an even dicier proposition. With only 140 characters to get across your message—and part of that taken up with your account name—you may think you’ve disclosed your relationship as well as you can, only to find some followers think you’ve been deceptive. And the FTC’s $11,000 fine is nothing to sneeze at.

Digitas Emerging Channels Specialist Jon Burg (who’s also the brother of a non-communications family friend) has taken a stab at creating a protocol for Twitter disclosure. The idea of Jon’s “short-form disclosure” is simple and elegant. It requires only four of your 140 characters. For example, if I worked for Ford Motor Company as a social media representative talking about the Ford Fusion, I would send a tweet like this:

Great customer testimonial about the Ford Fusion. >SPK

>SPK discloses that you’re a spokesperson for the brand or campaign.

Here’s Jon’s complete list of proposed short-form disclosure codes (click it to enlarge it):

Shel Holtz

I’ve already seen it suggested that widespread adoption of Jon’s short-form disclosure isn’t likely, but I disagree. We’ve seen Twitter’s user community create several conventions that have become standard, including the @ symbol, RT, and the dot before an account name. If the user community decides to embrace short-form disclosure, it’ll spread.

Of course, not everyone on Twitter would have a reason to adopt short-form disclosure, so it would be up to us who do have a legitimate need to disclose to start using them.

At this point, Jon’s not proposing we start running with these, but rather have a conversation about them leading to eventual refinement into something we can all agree on.

I’m hopeful Jon’s first pass at short-form disclosure gains traction, produces discussion, and leads to a standard. It won’t happen if you don’t join the conversation and commit to using the resulting codes. Feel free to comment here, but I’d encourage you to share your thoughts on Jon’s post, too.

10/06/09 | 6 Comments | Clear disclosure in 140 characters

Comments
  • 1.Interesting. I can see the use of some of these, but some others don't make sense.

    The spokesperson code, for example - if you're a spokesperson, shouldn't that be in your bio? If it's a corporate account, an emerging best practice is to list the users in the bio or on the account's Twitter background and to identify the individual in each Tweet. Not sure how the code advances things.

    On the flip side, I think ">AD" and ">SPO" are interesting ideas. Curious to see if they gain any traction.

    The ">EMP" idea is an interesting one, too. If people are tweeting from personal accounts but commenting on company issues, I can see how that might be useful.

    Dave Fleet | October 2009 | Toronto, Ontario

  • 2.Firstly Shel, thanks for sharing!

    @Dave - I agree that corporate accounts/spokespeople should call out their information on their profiles and profile pages, I'm just not sure that everyone clicks through to profile pages before engaging someone in a conversation. For a number of brands, disclosure is a major issue, and it needs to be clearly evident in every conversation. By including >spk in the text of the tweet, it calls out there there is something happening here, and you may want to look at the profile for more info.

    Thanks for sharing!

    jon burg | October 2009 | NY

  • 3.My view is similar to yours, users need to embrace it for it to work. My main criticism of Jon's suggestions is that they are too complex with seven different ones to remember and understand. Professionals will get it wrong, let alone consumers on the receiving end!

    Stuart Bruce | October 2009 | London/Leeds, UK

  • 4.Stuart, we've heard that before and would love to get your thoughts on distilling this while staying true to the nature of the relationship.

    jon burg | October 2009 | NY

  • 5.@Jon, @Shel -- Think the codes are a great start to a conversation that needs to be had, discussed further.

    @Dave -- Seven codes may seem complicated at first, but betting ppl thought RT, hashtags, @ symbol was complicated at one time. If people use the codes, they'll catch on. I've been disclosing tweets about clients with a parenthetical (client) reference at the end. Why? Because a friend from Weber Shandwick was using that method.

    I'm ready to give these codes a try and provide feedback if issues arise. Sent them to our office at Fleishman KC as a suggested way to point out our relationships to tweets we make. Agree that most don't read the user bio. Takes too long.

    My additional question is: "What about disclosure on Facebook?" If I become a fan of a client, do I need to disclose that? How do I? In my profile by saying I work for FH? What if my profile isn't open (mine happens to be) and only friends can see it? Where's the line?

    Justin Goldsborough | October 2009 | Kansas City, MO

  • 6.Good stuff Shel. I think that adoption of John's short forms could possibly happen when the tags can be automated by applications like Tweetdeck or Seesmic - and since both companies seem to be pretty good at "having BIG ears" maybe they will pick up this post and start working on it. Key to adoption in Twitter is ease of use. RT's and @ replies have been automated ever since desktop clients started to gain popularity. They will lead this charge as well IMHO...

    Keep it coming!
    @nateriggs

    Nate Riggs | October 2009 | Columbus, OH

Comment Form

« Back