After attended several conferences this year where tweeting was not only allowed but encouraged, I thought that it might be helpful to develop some “twips” for tweeting at a conference. More than anything, this list was created to help me reflect on how I can be a more productive member of the community at this year’s MERLOT International Conference in San Jose.
- Be courteous to those sitting around you. Even at a technology conference, there are attendees who are distracted by the use of laptops and smart phones.
- Send only one or two Updates from a session. Share a twugget not a twanscript.
- Use Updates to ask any questions you have about a session topic or the conference in general. There are no quotos on inquiry-based Updates.
- Answer other participants questions using @username in Replies so the person asking a question can see the response under Mentions or @username.
- Include URLs to important content shared by presenters in your Updates. Be sure to use a URL shortening application (e.g. http:// tinyurl.com) to reduce the total number of characters.
- Include the conference hash tag, (e.g. #MIC09) on all conference-relate Updates to help others find and organize content for their Personal Learning Networks.
- Retweet (RT) valuable Updates from other participants letting the Twitterverse know that an important idea has been shared.
- Write concise updates. It’s hard to ReTweet Updates that use all or most of the 140-character limit.
- Avoid writing cryptic Updates. Texting is for kids.
- Golden Twip: Tweet only what is appropriate to stand and say during a conference session. A critique of a presenter’s delivery skills (e.g. “David Wicks is just reading his slides. Boring!”) should be saved for the official session evaluation form.
Do you have any recommendations on changes that should be made to this list? I will be sharing it as part of pre-conference webinar, How to Twitter about the MERLOT International Conference.
Happy tweeting at your next conference!