Social Media Strategery

Enterprise 2.0 Conference in Boston

See you next week in Santa Clara!

Next week, I’m attending and speaking at the Enterprise 2.0 Conference in Santa Clara. I’ve attended many social media conferences over the years and have posted several times about my experiences at these events.While the vast majority of people I meet at these conferences are highly intelligent, ambitious, and well-meaning, I have noticed a pattern emerging among social media conference-goers. From Web 2.0 to Gov 2.0 to Enterprise 2.0, I always seem to run into the same people yet miss the people I really want to talk to at these events. Based on my conference-going experience, here are ten people I assume I’ll be meeting (and not meeting) next week:

Who I Will Meet:

The overzealous Director of Business Development. Don’t you realize that his product has revolutionary features not found anywhere else?? Well, that is, until you go two booths down… If you sit down for a demo, you’ll clearly realize that this is the ONLY product with this feature. Just listen for a few minutes and he’ll show you…wait! Come back and hear all about it!!

The Director of Social Media/Virtual Collaboration Lead/Social Collaboration Team Leader. The company’s designated social media “guru” – there to find out how to turn their company’s Intranet into a “Facebook or Wikipedia behind the firewall.” This individual is usually well-meaning and excited, if a bit in over their head. On the first day, they’re enthusiastic, ready to absorb whatever they can over the next few days. But by the last day, they’re usually simultaneously overwhelmed and frustrated by all the stories of what’s possible, yet still lack any actionable steps they can take when they get back to their office.

The codemonkey. He’s the guy in the back with all the stickers on his Macbook. Mashups, visualizations, dashboards – you name it, he can code it. Keep in mind that he probably doesn’t actually use of the tools he’s developing, the features he’s working on really only interest the early adopters at this conference, and they probably do more to hinder user adoption because while they look cool, they really just overwhelm people and hinder user adoption because all the average employee really wants are tools that are accessible, fast, and reliable.

The self-promoter. Got his (oddly-shaped) business card yet? Don’t worry, you’ll get it soon enough. He’s the CEO for some new startup or he just got some VC to invest a boatload of money in his company or he’s writing a new book – it doesn’t really matter because he’s going to tell you all about it…whether you care or not. Don’t you realize how lucky you are to get an opportunity to talk to him?

The booth babe/dude.” He or she is always very nice and very conversational, but unfortunately lack ANY details about the company they’re representing. Good luck getting any actual information from him/her beyond a fact sheet, a demo, and someone else’s business card.

Who I Won’t Meet:

The IT Security specialist. Time and time again, I find myself talking with a client about Enterprise 2.0 only to hear that their security guys won’t allow them to install any Enterprise 2.0 software or that SAAS isn’t an option, but very rarely do I actually see any of these individuals at these conferences. Just once, I’d like to meet some ambitious IT Security professional who says, “you know what, I want to attend this conference so that I can learn how to allow our employees to use these tools AND be safe and secure?” 

The Lawyer. The relationship between lawyers and Enterprise 2.0 is tenuous at best. Everyone tries to have as little interaction with them as possible, but when they do have to get involved, it almost always results in a whiny, “do we really have to pass this through them????”  But what if your legal team was actually knowledgeable about Enterprise 2.0? If they knew the success stories and the potential? Have you ever spoken to a lawyer who actually “gets it” and asks you “how can I help?” How refreshing is that?

The Failures. I loved that Kevin Jones was a speaker at the last Enterprise 2.0 Conference and will be there again in Santa Clara. He was among the first people I’ve met at these types of conferences willing to talk about how he failed, what failed, and how he would have done things differently. Unfortunately, these people are few and far between as most people only want to tout their successes, their products, and their features. We all know getting this stuff right is hard – where have others stumbled and what can we learn from them?

The C-suite. Director of Social Strategies, Social Collaboration Lead, Virtual Collaboration specialist – where are the traditional organizational leaders? Where are the CIOs and CTOs? Unfortunately, Enterprise 2.0 still isn’t integrated into the other business units so it will continue to be marginalized. Until we get more actual decision-makers to attend these conferences and learn of the benefits for themselves, we’ll unfortunately continue to have to fight to justify social to the senior leadership.

The average employee. Where are all of the project managers, supervisors, associates, and HR specialists? Where are the people who are actually supposed to be using Enterprise tools to do their jobs? I want to meet more average users and find out what they want from the dozens of vendors who will be present. I want to find out why Cindy, the HR specialist in Omaha refuses to use the discussion forums that her company set up.

Will I meet you at Enterprise 2.0 next week? If you want to meet me, I, along with my colleagues Walton Smith and Jay Leask, will be there all week. Walton and I are speaking on Wednesday at 12:30 in the Expo Hall where we’ll be giving an abbreviated presentation of our webinar, “It’s not the Players, It’s the Game,” and then on Wednesday at 8:45am, David Berry and Jay Leask will discuss how organizations have successfully leveraged SharePoint as a social platform within their organizations in their session “Options for Leveraging SharePoint as a Social Platform.“

A community of practice (CoP) is, according to cognitive anthropologists Jean Lave and Etienne Wenger, a group of people who share an interest, a craft, and/or a profession.

Over the last year or so, the term communities of practice has entered the social media buzzword lexicon along with virtual collaboration, engagement, platforms, and Enterprise 2.0. Senior leaders want to establish them, new employees are being told to join them, and middle managers are being told to support them, but what, exactly are they?

Nowhere in the definition above does it mention the words website, wiki, blog, or social network. Nowhere does it say that it has to be virtual or physical or even either/or. There is no reference to the tools that are used to facilitate the communication and collaboration, nor is there a defined set of characteristics that define how a community of practice works or what topics they discuss.

A group of people who share an interest, a craft and/or a profession. Sounds pretty simple, right? Sounds like we might already be members of dozens of communities of practice – at work, at church, at school, etc. It’s just a group of people communicating and collaborating openly around a topic that they all care about. CoPs have existed for as long as people have had a desire to learn from each other.

Whether your organization knows it or not, your company/government agency is already filled with CoPs. Just because all of their communication and collaboration doesn’t happen to occur on your designated SharePoint site doesn’t mean that people aren’t already communicating and collaborating around a shared topic of interest. Whether it’s the group of new hires who coordinate the monthly happy hours or the new parents who get together over lunch to discuss work/life balance, communities of practice are alive and well within most organizations. They just might not be the ones with a unique URL on the Intranet.

Are you creating a community of practice or are you just creating another website? How does your CoP stack up to some of these statements?

• People voluntarily spend time helping others in a community of practice. People visit a website to download what they need.
• CoPs focus on adding value to their members. Websites focus on getting new users.
• The success of a CoP is measured in anecdotes, efficiencies, and employee satisfaction. The success of a website is measured by hits, visits, and referrals.
• The members of a CoP volunteer their expertise to create new tech features. A website has paid developers who add new features.
• A CoP is built around conversation. A website is built around content.

Communities of practice have been around for decades, and for decades, they’ve helped countless organizations navigate major changes, increase productivity, cut duplication, and make work more enjoyable. In many cases, the use of social media has enhanced these CoPs by providing more tools and opportunities for people to connect with other people. Unfortunately, social media has also given rise to zombie communities filled with content on blogs, forums, and wikis, but which lack any actual human interaction. What are you building?

For more about Communities of Practice, check out Cultivating Communities of Practice: A Guide to Managing Knowledge, Harvard Business School Press, 2002 by Etienne Wenger, Richard McDermott, and William M. Snyder.

Watch your local Pee-wee football team’s practice sometime and you’ll see a lot of dropped passes, missed tackles, and a whole host of other mistakes. But…what would happen if you put that team on Heinz Field and gave them all the same amenities as the Pittsburgh Steelers? Yep, they still wouldn’t be able to complete a pass, kick a field goal or break a James Harrison tackle. Clearly, just because they were put on a better field and given the latest equipment doesn’t mean they will suddenly learn to play football.

Southern Tier Youth Football Conference, NY - Newark Valley @ Maine Endwell Gold

It doesn't matter what kind of equipment you give them, these players aren't going to win the Super Bowl

Similarly, simply adding the latest Enterprise 2.0 platform behind your firewall doesn’t mean your employees will suddenly learn to collaborate with one another. Collaboration doesn’t just magically happen because you went out and bought the latest Enterprise 2.0 or Social Business software. It happens because they have a reason to collaborate. It happens when they are rewarded for sharing information. It happens when they like working with the people around them.

Over the last few years, I’ve seen dozens of failed wikis, blogs, microblog platforms, forums, and idea management deployments, and I’m sure I’ll see many more. This is frustrating on a couple of different levels for me. First, since I suffer from HOLI (“Hatred of Losing Information“), I hate seeing the missed collaboration opportunities that result from these poorly implemented solutions. Secondly, I know that because of these failures, these organizations will most likely write off social media behind the firewall as some sort of snake oil.

Perhaps the most frustrating part of all of these failures is the reliability with which their failure can be predicted. If you’re implementing some sort of social media behind your organizational firewall, and you’re doing any of the following, I can tell you right now that you probably won’t be successful:

• The same IT department who installed your email system, your ERP system, or your databases is responsible for leading the implementation of your wiki, blog, microblogging platform, etc.
• You don’t have anyone talking about user adoption and community management on the team from the very start
• You don’t have a plan for funding this initiative beyond this year
• You’re measuring success by the number of “users” you can claim
• You’re talking about giving away iPads and candy bars to get people to use it
• There are numerous conversations among senior leadership about how to mitigate the risks of your employees using the tools “as a dating service,” to “goof around,” to complain about everything, or editing things they don’t know anything about.
• You’re more concerned with the available features instead of making it fast, reliable, and accessible
• The team responsible for the platform doesn’t even use it

Instead of trying to give the players the latest and greatest stadium and equipment, start focusing on improving their passing and tackling skills. Maybe you could have them run some pass patterns instead of installing a state-of-the art locker room?

• Do my employees have a reason to collaborate with people outside of their immediate team?
• Is collaborative behavior rewarded during the performance assessment process? Are they punished for hoarding information?
• Does leadership model collaborative behavior?
• Are colleagues encouraged to spend time with each other outside of work hours (softball teams, happy hours, etc.)?
• Are there multiple levels of approvals needed before anyone can share anything?
• Do your employees trust each other? Do they trust management?

If you’re interested in learning more about why your Enterprise 2.0 implementations are failing and what you can do to help them succeed, take a look at the webinar that I just did for UBM TechWeb.  The “It’s Not the Field, It’s the Players” webinar will be archived here, and the slides are now available below. 

[UPDATED TO INCLUDE THE PRESENTATION BELOW]

It’s not difficult to find examples of sports teams using social media. From the player (Gilbert Arenas’ landmark blogging in 2006) to the team (the Red Sox using Twitter to give away free tickets during a rain delay) to the league (the NHL’s tweetups), social media has gone from being an innovative marketing tactic to a must-have component of any marketing strategy. League and individual team marketing functions are hard at work thinking up all kinds of new ways to use social media to increase fan loyalty, buy tickets, buy merchandise, and watch/listen to the games via myriad devices. Here’s the rub – in any one league, this brainstorming is happening, sometimes 30 times over, in the league office and in each of the team’s front offices because there’s no single platform where team and league staff are sharing this information.

Enterprise 2.0 conference, Jun 2009 - 26

There are plenty of case studies of sports leagues and teams using social media for marketing purposes - where are the examples of using social media to improve league and team collaboration?

Disappointingly, a search for examples where teams, leagues, or college conferences are using social media to communicate and collaborate internally yields a much shorter, less relevant list. For all of the media attention that’s heaped on these leagues and teams for their use (or lack thereof) of social media to communicate with fans and the media, internal collaboration amongst league and team front office staff is still ruled by phone calls, shared drives, and emails. The personal relationships established among front office staff at games and league functions have become the de facto collaboration mechanism for the PR, customer service, ticket sales, media relations, broadcasting, and other front office staff. Despite all the gains in using social media for marketing, the sports industry, by and large, has failed to capitalize on the opportunities social media can bring them internally.

As I mentioned in a previous post, there are actually a lot of similarities between the sports industry and the government when it comes to using social media. While the Air Force, Army, Navy, and Marine Corps all maintain fierce loyalty to their respective service branch, they also realize they are all ultimately fighting for the same cause, for the same team, and it’s up to the Department of Defense (DoD) to bring all of these individuals together under one mission.  Similarly, the Penguins, Flyers, Bruins and Capitals are rivals on the ice, yet they all realize that when push comes to shove, they all play in the same league and all need to work together to grow the game. Unfortunately, while the DoD is using wikis to conduct intelligence analysis and social networking to get new employees up to speed more quickly, professional sports leagues continue to rely on tools that are inaccessible, unsearchable, and unorganized to collaborate with one another. By relying on personal relationships instead of using open platforms that connect teams and leagues together, professional sports leagues are missing a golden opportunity to reduce duplication, cut costs, increase morale, and increase employee performance.

What if leagues and conferences were able to create a common platform where all of their teams could collaborate with one another, sharing best practices and lessons learned?
Wouldn’t that be better than relying on phone calls and emails to share this information?

What if each league had an idea generation platform a la Manor Labs where staff could submit ideas that would be discussed and voted upon by their colleagues across the league?
Wouldn’t that be better than sending around “what do you think of this?” emails?

What if each league had one shared platform accessible to all of the communications staff from each of the teams where things like marketing campaigns, communications templates, and results could be uploaded and shared?
Woudn’t that work better than digging through old emails and shared drive files?

What if the league stopped mandating policies and technical platforms on their teams and instead co-created these policies and collaborated on the best technical platforms?
Wouldn’t it be better to be seen as a partner instead of an adversary?

Competition on the field and collaboration in the office isn’t a new idea. This idea that the whole is greater than the sum of its parts has permeated the sports landscape this year. From revenue sharing across all teams in the NFL’s latest collective bargaining agreement (the teams that bring in more money share revenue with the small market clubs) to the new conference realignments happening in college (Florida and Georgia may be rivals, but you can bet their rooting for each other if they’re both playing teams from the Big Ten), leagues and teams have realized that a healthy league makes for healthy teams. It’s hard for the average fan to understand, but just because Terrell Suggs and Hines Ward may not be the best of friends doesn’t mean that the Steelers communications staff and Ravens communications staff are necessarily at each other throats too.

What if the sports leagues and teams took advantage of these Enterprise 2.0 technologies, learned from what’s been done in other similar organizations and used technology to enable this collaboration to take place not just at the collective bargaining level, but at the day-to-day level?

Perhaps the more important question is…what happens if they don’t?