It’s Friday. Let’s have some fun and talk football!
While not my favorite, the NFL reigns as America’s most popular sports league.
Yet, social media has yet to become widely embraced by the league and its teams outside of broadcast-like promotion. For example, the NFL does not offer access to commonly accepted social networks on its front page.
Continue reading “Improve the NFL Experience with Social”
Oh yes, there are many changes afoot amongst the social networks. Facebook, Google+ and Twitter, oh my! And of course, the social media punditry has ratcheted up with the competition. Could it be more meaningless and boring?
Seriously. New feature social network roll-outs are about as exciting watching the fall line-up of TV programming getting announced.
Interesting? Yes. Meaningful? No, not until you get to experience the show a couple of times.
The difference is that instead of several TV critics, we have tens of thousand of so-called experts offering declarations at ever opportunity. The social media marketers who claim to know how these features will impact business are just ridiculous.
Sorry. It’s laughable. Can anyone possibly know how these new features will work out before even using them? Even for just a week?
Point being, who really knows? No one.
Let’s be frank, there is no social networking revolution, no dramatic change in the way people interact online that has been caused by any of these updates. Just more options. And that’s why for those of us who use these tools to communicate professionally, the current punditry is worthy of a big long nap.
In today’s world of increasingly integrated social functionality, the ability to cross-post across social networks enables time savings and multiple community engagement. Yet, as we have seen overtime, while easier for the content producer, crossing the streams can actually alienate individual communities. A Foursquare check-in is not a Facebook update, which is not a Tweet, nor a Buzz or a bookmark.
There’s no greater example of mindless stream crossing that alienates users than FourSquare check-ins. These are especially egregious when the user simply checks in with no contextual additions (such as, “at baseball game with my son, his first game ever”). Twitter, Facebook and other associated communities are treated with such fantastic, mindblowing contributions as, “I’m at Safeway.”
Add dozens of such updates to your stream, and you find yourself wondering you are on Facebook or Foursquare. Each social network has unique qualities to it, which attract repeat users and diehard community members to their sites. When the users are force-fed another social network’s lexicon and update system, some people start disengaging from the content creator.
Giga-Om featured an excellent piece on crossing the streams between Buzz and Twitter recently. The crucial point is the failure of content creators to engage in conversations across their streams, effectively spamming their friends and followers.
Content creators need to weigh the pros and cons of crossing the streams. Based on feedback from the various communities that I participate in, I tend to decouple social networks, and then selectively cross the streams. Usually, it’s for a blog post, picture or a Tweet (that doesn’t include an @ or a hashtag).
It’s my assumption that these types of content contributions have value across my streams. I’m not always right on the mark, and I can tell that with analytics as well as with occasional feedback. Here’s what Kenley Neufeld and Dave Webb said about the matter on Buzz:
Others, simply moderate the amount of cross-posted content they are producing so as not to inundate all of their networks with a never ending stream of data. Still others just couple everything and let the chips fall where they will. Finally, some never couple their networks and keep them separate for a variety of reasons, including privacy.
To me, this is the delicate art of crossing the streams. Success requires one to delicately understand which updates matter to their communities, or possess incredibly loyal communities who will tolerate such continuous updates. Otherwise, disconnects occur.
What are your thoughts on connecting the streams?
