I presented this in Dallas in September to a room full of 100+ CIOs at the Dallas Chamber of Commerce CIO Symposium. We had CIOs from Mary Kaye, Boy Scouts of America, Bank of America, and the moderator was the Strategist for EDS that helped lead them to an Acquisition by HP. It was a lot of fun - I hope I can come again and share some more. I promised them I would upload this presentation. It may not make full sense to all, but if you’d like me to come present it to your organization, contact me! Some day if I get some time I’ll do a recording on top of it so it makes a little more sense, but at least you can get the idea for what I shared.

I’m a sucker for a deal. Let’s just say I’m a cheapskate. That’s why I was excited when I heard that Chick-Fil-A stores were offering free chicken sandwiches nationwide today. So I went out and voted, excited to celebrate my vote with a nice chicken sandwich from Chick-Fil-A. Never mind the $5 in gas it cost me to drive there.

I get there after a long drive telling them about hearing online about them offering free sandwiches, showing my “I Voted Sticker”. They’re response was “Chick-Fil-A isn’t doing that - it was a ‘Media Error’”. I responded arguing it was all over the web, and all they could do is tell me their manager said they couldn’t give anything out.

So what did I do? I got on Twitter (well, actually FriendFeed, which goes to Twitter) and hashtagged it #ep and #votereport (as a joke), and shared with my 1400 or so friends on Twitter, along with anyone monitoring #votereport and #ep, not to mention the near 800 friends on Facebook and near 700 friends on FriendFeed how Chick-Fil-A had made this huge PR error. And now I’m blogging about it to at least 500 more people, and who knows if others share this with friends and how many more people end up seeing it.

Here’s the problem - I noted to them that I had heard the offer on the internet. That means I have reach. I most likely share things with my friends through this enormous, now social tool. This should signal that to them, regardless of who I am. I know not all their customers have heard of the offer, so therefore they aren’t going to go broke giving stuff away. However, if they would have just given away a free drink (which, from my fast food experience, costs practically nothing), or free fries, or even a coupon to come in next time for a free sandwich, they could have taken advantage of that reach. I would have been tweeting about my great experience getting free food at Chick-Fil-A, they would have gotten more customers and more people aware of their location, and this blog post would have been much more positive in their favor.

Social Media is powerful, people. Yes, I did end up buying my own sandwich and I still like their food, but they could have taken advantage of a much greater opportunity to spread the word about their brand and promote that particular location. Chick-Fil-A, and especially that particular location, missed out on a huge opportunity here.

Representative John Culberson, the Twittering and Qik’ing Congressman from my good old home town of Houston, Texas, has been on a rampage this morning about a proposed new regulation for the House of Representatives, which, he claims, will require all world wide web communications from the House floor from those in congress to receive “prior approval” from a Democratically-controlled Committee on House Administration before it goes out to the web. From the letter:

“

• Official content posted on an external domain must be clearly identified as produced by a House office for official purposes, and meet existing content rules and regulations;
• To the maximum extent possible, the official content should not be posted on a website or page where it may appear with commercial or political information or any other information not in compliance with the House’s content guidelines.
• Any link from a House website to an external site on which the Member video is hosted must contain an exit notice.
• CHA, the Office of Web Assistance(OWA), or other designated House entity should maintain a list of external sites that meet whatever requirements are established by the CHA

”

Per the above proposed recommendations, this would rule out any Twitter communication because by law, each Tweet would need to be prepended by a disclaimer, identifying it as being produced by a House office for official purposes and, as Culberson puts it, that will most likely in and of its self exceed 140 characters. Also, it would mean that any Congressman wishing to use a site such as Twitter to share publicly what is going on in Congress with their constituents will have to get prior approval, censorship essentially, before using such a site or technology.

I find it ironic that it is a Republican that is trying to show the Democrats how to use technology on this, but Representative Culberson has a point here, and we need to speak up if we’re to continue seeing social media propagate through our government. Social Media in government means a more open government, and that’s a good thing! I’d like to encourage all that read this to write your Congressman or Congresswoman about this (Pelosi is part of this!) and get them to see things straight rather than requiring censorship of our House floor.

You can read the Proposal here. (Which, were this proposal to take effect, I believe I would be breaking the law by sharing with you)

UPDATE: Want to discuss? Let’s discuss in a nice open format right below this post via the FriendFeed link below!

I mentioned this at the Hackathon in March, but have not had the time to blog about it yet. Thus far all announcements for the Utah Social Media Developers Garage Meetings and Utah Facebook Developers Garage Meetings have been announced either through this blog, or our Facebook Group. I’ve now created a Google Group for us at http://groups.google.com/group/utsmdev. Please sign up there and I’ll issue all announcements via that list. Google Groups provides a more neutral ground in the sense that users don’t have to have an account to use it (to an extent), as compared to the Facebook groups. We’ll keep the Facebook groups around, and depending on membership I’ll still send announcements there as well, but I encourage all to sign up on the Google Group if possible. In addition, having a mailing list will allow us to have more of a discussion. This way if you are working on a project in Facebook, or OpenSocial, or even Wordpress or Twitter or other APIs and you run into issues, you can ask the group and we can work together to solve the problem. I figure this way we’ll be able to all build a strong Social Media Development community here in Utah that others can rely on. Google groups will also give us a page we can tell others about the group, when the next meeting is, etc. If you have some graphics and HTML skills to help with that I am open to volunteers!

Also, I have created a Google Code repository at http://code.google.com/p/utsmdev/. For anyone okay with producing their code under the GPL, this will give you a place to store your code, and collaborate with others on the code, track issues, etc. If you want commit permissions to that repository please contact me and I’ll add you. As Google App Engine gets more integration into these things we’ll also set up a hosting option through Google App Engine to actually host your apps. Hopefully all these options will make it all much easier for everyone to get out and collaborate in their coding. It’s a good time to be a developer…

P.S. - We will continue on in our every-other-month meeting structure now, so our next meeting will be the second Tuesday in May. I’m working on a speaker, so if you know anyone or have ideas let me know!

According to Mike Arrington (I know, I said I wanted to boycott TechCrunch but it’s just so dang hard to avoid! I’ll stick to boycotting Crunchgear for now.), Google is having another “Campfire One” event tonight. The last Campfire One event they announced OpenSocial. It was the OpenSocial team that announced the event, and the biggest bloggers and developers in the industry were all there. Mike Arrington thinks this one is going to be the announcement of “BigTable”, Google’s answer to Amazon SimpleDB.

I think otherwise - see my thoughts at OpensocialNow.com.