Hashtags have long been an integral component of Twitter. They offer much: ability to sort tweets into categories, quickly find and track information for a particular topic, and customize as needed for a brief interval or long-term use.
Given the transient nature of tweets, hashtags also provide a way to capture information and review historical information. You can go back a ways to see older tweets. We’ve been using additional tags for tech communication. I’d like to propose expanded usage.
Proposal
I’m proposing that we start using hashtags in addition to the #techcomm tag. There’s plenty of talk out there (on this blog included) about using Twitter, getting started, and making changes to accommodate trends. This provides an easy way to jump in right now and start testing – and learning. Additional reasons are described in detail below. Here are the proposals:
#techcomm (basic)
#TCdiscuss, #TCdisc, #TCchat (discussion)
#TCtips
#TCinfo and #TCref (articles, info)
#TCexp (experiments; feedback encouraged)
……………………………………………
For fun:
#TCcoffee (wake-up calls)
#TCchocolate (everyday stress relief)
Why
Here are a few reasons why I think it would be useful to have additional hashtags.
Sort
What tech writer doesn’t like to sort content into nice little categories to make life easier? Hashtags do that. With Twitter apps, you can set up tabs and columns for each hashtag you regularly use. Then you’re able to see tweets at a glance. Here’s an example of some of the hashtags I follow in HootSuite:
Note: In this example, there’s a separate tab for hashtags (Searches) and I have a column for each tag. Because I track more than three, I can scroll to see more columns I set up. Then it’s possible to easily scan each topic for quick news and information.
TweetDeck also has options for setting up content in columns. These apps provide quick access to an instant sort, information at your fingertips. A quick glance and you’re off.
Controlled Vocabulary
One excellent benefit of using hashtags it that it facilitates and supports use of a controlled vocabulary for your company. This is an integral part of content management. It makes writing easier, as use of common terms, acronyms, and the like in a company from division to division gets everyone on the same page. You also don’t have to redefine a topic or term multiple times. Ultimately, it also makes localization easier and less costly, as only one term could be used for a topic.
Plus, (a big plus, I think) is that with all the user-generated content coming our way, if you can establish a framework ahead of time and encourage users to use that, then half the battle is won. Hashtags provide structure. They can be a reference point.
Many years back, I focused on writing indexes for a bit. When doing so, you’re able to direct users to replace use of one term for another. Then you focus on the main term to encourage use. For instance, let’s say you want to use Term A. Perhaps terminology has changed in your company or app, or one term would be better for users to use in the long run. Imagine that people have been using Term B and Term C for essentially the same content. In an index, you would stop use of Terms B and C, and have only a cross-reference to Term A instead.
With hashtags, you could gently direct users to use a particular hashtag. Perhaps it’s a shorter one, which provides room for RTs or makes room for multiple tags in a tweet. Perhaps it uses your controlled vocabulary. Perhaps you can somehow import tweets (it must be possible, or will be), and pull those that match your XML tags so you can write some programming options in an XSL file to work your docs, and match database and mapping options.
Use the Techcomm Hashtags and Feeds as a Testing Ground
Companies and even documentation departments may not be ready to start using Twitter. However, they need to. It’s proven by now, of course. Just because they don’t doesn’t mean that you can’t experiment. The only way to learn it is to start using it yourself. I’ve run some experiments myself and have learned much every time.
Why not use these communication feeds as sandboxes, as vehicles for experimentation? I’m in no way suggesting to put confidential information out on the web. You can test with anything. I’ve done it; it’s easy. I’ve tested use of serial tweets and hashtags. I’ve tried procedure tweets that include steps and links to more detailed information. It’s easy to do, and I’ve received helpful feedback each time. Just go for it! Try things out. If you use #TCexp for your tests, we would know to look at what you’re doing and offer feedback.
Collaboration
Use of hashtags provide a perfect opportunity to collaborate. It’s not unusual to get used to the old “we’ve always done it this way” in a company. Step out the door; see what opinions are there from people outside your company. It never hurts to get some new ideas.
You can obtain advice and usability feedback from other tech writers. Obtain input from writers around the world. In this new age, I think that is wonderful. How lucky are we?
Expand Use of the Feeds
So far, we all use the #techcomm to relay interesting articles and links to pertinent to writing. There is sometimes some discussion as well. Using more hashtags would provide additional ways for us all to explore and collaborate. In other words, I don’t think we’re currently using the main tag to its full potential. Let’s widen the scope. Lets share and learn more. Use of hashtags provide the perfect opportunity to try things, discuss, & collaborate.
Again, my suggestions are listed at the beginning of this post. Any thoughts of using them are appreciated. Or, what the hey? Lets try them and see how they work.
For all these reasons, imagine a similar setup for your company. How might the experiments and usage on tech comm tag categories apply to your work, to your company, to your docs, to your users? Make the leap. Apply what you learn.
Let’s Try It!
Let’s try using the items proposed above. Why not? They might be helpful!
Comments