PageOnePR
'; } ?> 
  • \"Services\""; } elseif (($page == "capabilities") || ($page == "best_practices")) { echo "\"Services\""; } else { echo "\"Services\""; } ?>
  • \"Clients\""; } elseif (($page == "current") || ($page == "past") || ($page == "testimonials") || ($page == "results") || ($page == "makingnews")) { echo "\"Clients\""; } else { echo "\"Clients\""; } ?>
  • \"Careers\""; } elseif (($page == "culture") || ($page == "benefits") || ($page == "watercooler")) { echo "\"Careers\""; } else { echo "\"Careers\""; } ?>
  • \"Contact\""; } else { echo "\"Contact\""; } ?>
  • \"Blog\""; } else { echo "\"Blog\""; } ?>
  • \"Japan\""; } else { echo "\"Japan\""; } ?>
  • Subscribe to this feed

    The Page Wonders

    Social media is changing PR in new and exciting ways. More than ever before, companies want help from a PR partner who can put smart, creative, independent-thinking professionals on tough problems using these new tools to seize opportunities and solve problems. Read here about some of the exploits of our Page Wonders and tell us what you think!

    Other Staff Blogs:Craig Oda | Shelly Milam


    Tweeting Live Tech Events: the 7 Golden Rules
    posted by Jesse Casman at

    Here are seven golden rules to keep in mind as you prepare to tweet your next tech event:

    1) Establish a hashtag, and start using it before the event in all Twitter communications. Without doing this, you may find yourself in a "hashtag war" where your company suggests one but users use another. This is not a disaster. But it can be sloppy. One reason users will pick a different hashtag: yours is too long. Because hashtags will be appended to all related tweets, they should be short, to take up as little room as possible. Consider changing #mycompanyevent to #mce. You lose a little in obvious branding but gain a lot in Twitter usefulness. Searching for this hashtag at any point gives readers a quick summary of all tweets related to your event.

    2) You'll tweet a little bit about your event leading up to the day, and then you'll turn on the fire hose of tweets as the event unfolds, in real-time. If you're worried about how the big change in the number of tweets coming from your account will be received, don't be. In general, in Twitter, more information is welcomed, not criticized. By all means, in the days leading up to the event, give your followers some warnings: "Event coming up, we're trying something different, live-tweeting it."

    3) Make sure your tweets are short enough to be easily retweeted. 140 characters MINUS "RT @yourcompany" means that others reading your tweets can retweet them without any editing. At a live event, this is a major advantage.

    4) Not all issues are technology related. Don't forget politics. Live tweeting panels, even though it's a public forum, requires taking into account participants' opinions as well, and can be a bit tricky. If you have someone running the Twitter feed who can take political considerations into account real-time, you'll be better off. Too sharp of comments and there are potential participant issues. Too bland and your Twitter feed is useless. Most likely, other Twitter feeds will fill in with sharper criticism.

    5) In one case, Page One PR's client was very open source centric, so giving a nod to Identi.ca, built on open source software, was important. All tweets were initiated through Identi.ca. You can easily configure Identi.ca to automatically post to Twitter. All tweets are then signed "half a minute ago from Identica," marking you as an open source supporter. (As you should be!)

    6) Timing is of the essence. With other people enthusiastically tweeting, five minutes late looks really late. Preparing informative tweets ahead of time helps. In a separate document, if you know, for instance, 3-4 panels that the company will be tweeting about, line up 3-4 tweets that announce "XYZ panel with John and Jane Doe, just getting started..." Interspersing prepared tweets with live ones will help significantly with your real-time workload.


    Bonus rule for the expert Tweeters to consider:

    7) How to work with panels. Soliciting questions for a panel may feel like a good idea -- real democracy! -- but there are several important things to consider. Are you confident you can get enough questions live? If not, soliciting questions ahead of time is smart. How do you transmit them up to the podium? IMing them is possible, but whoever is receiving them needs to both scan and summarize real-time. They can not be actively participating in the panel. Summarizing and reporting the answers? Not possible with one person running the Twitter feed. Ideally, you need two people to properly handle: one who is monitoring the Twitter feed, one who is listening to the panel and summarizing and condensing answers into tweets. (Not easy!) Tweeting back answers? Again, not possible with one person.

    Labels: , ,

    2 Comments:

    Blogger Martha de Monclin said...

    Great post Jesse and very timely!

    April 27, 2009 at 5:33 AM  
    Anonymous TravisV said...

    This blows my mind that Tweeting at events has become this scientific. I've been sort of blind to the hashmarking and value thereof, so this was enlightening.

    About four years ago when I was working at MuleSource, Michael Cote nudged me to try to use Twitter with our attendees to get the most out of it. I tried it for 10 mins and scoffed at it. And for three years I had this really venomous attitude about Twitter and people that used it. Man - what a waste of time that outlook was!

    With ITDatabase, one of the biggest sources of site traffic for us has been Twitter. I only got onto it a few months ago and our following is relatively modest compared to others that have been using it for a while. But it's been quite useful, and has really led to some word of mouth type of stuff that wouldn't have occurred otherwise.

    This post on Tweeting at events gave me some other ideas. And the blog in general has helped me acquaint with other social stuff in the last six months (after I pulled my head out of the sand).

    May 7, 2009 at 10:28 PM  

    Post a Comment

    Subscribe to Post Comments [Atom]

    << Home