The Twitter Roadblock Strategy?

If you are on Twitter, you’ve seen companies and individuals who do this. All of the sudden your Twitter feed is filled up with six Tweets in a row from the same account. Here are a couple of examples to show you exactly what I’m talking about:

Screen Shot 2015-03-19 at 3.50.23 PM

I want to know what’s behind this strategy. Is this mindlessly pushing out several Tweets all at once? (We’ve collected all of this news today and now we’re going to share it.) Or is it a well-considered strategy for getting attention by carving out a distinct block of real estate in your followers’ Twitter streams? (By doing this, our Tweets won’t get lost.) I find it annoying, but would love to have insight into the thought process of the people and organizations who do this.

Of course the problem with this strategy, unless they share this same content multiple times in different dayparts, is that the only people who see this block of Tweets are the followers who are on Twitter at that very moment. And we all know that Twitter followers are like flocks of geese flying overhead in intervals throughout the day (and night). Much depends on the audience we’re targeting.

I am a firm believer in Tweeting out an important piece of information more than once. But this notion of Tweeting five or six messages at exactly the same time (meaning they were scheduled to go at that time, because you couldn’t do that manually) is beyond me.

What are your thoughts? I’d love to get a reality check from others in the know. Thanks for bearing with me!

0 comments on “The Twitter Roadblock Strategy?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: