So, if you're deploying social tools internally, what kind of community is your organization creating?

• What group/community receives the most visits and/or posts on a particular day?
  1. The Intranet development team
  2. The Social Media/Web 2.0/New Media Community of Practice
  3. The Android/iPhone User Group
  4. An group focused on the core mission/operations
• On any given day, what % of your organization participates (reading or contributing) in your community?
  • Less than 10%
  • 10% to 49%
  • 50%-74%
  • More than 75%
• Senior leadership participation can best be classified as:
  1. Shhh! Don't tell them or they'll shut this site down!
  2. Big Brother-ish
  3. Lurking, but not active
  4. Active and insightful
• If someone posts, "I can't get my email to work on my phone – help!" What kind of response will they get?
  1. Total Silence
  2. "Call the help desk at 1-800-555-5555"
  3. "What problem are you having – maybe I can help?"
  4. "Many people have had issues with this so we created a wiki page to walk you through how to set it up the right way"
• Your CEO announces large-scale layoffs. You visit your online community later that day – what do you find?
  1. "I'm not going near that one!"
  2. Complaints and criticism
  3. Praise for leadership and the difficult job they have to do
  4. Balanced, professional discussion containing constructive criticism, ideas, and empathy
• Most of your employee profile pictures look like:
  1. 
  2. 
  3. 
  4. 
• Someone publishes a blog post highly critical of a senior leadership decision – what's the reaction?
  1. Trick question – all posts have to be approved by management and that never would have made it through
  2. The administrators delete the post and send a note to the employee's manager
  3. Other employees leave comments recommending that the post may be unprofessional and warrant some editing
  4. The senior leader in question posts a comment himself thanking the employee for his feedback and explaining the rationale behind the decision
• You create a wiki page for your team containing the text of a report you're working on. What kind of edits can they expect to receive?
  1. Yours and yours alone, since no one else your team understands how to make the edits themselves
  2. Your project team's edits because no one else can access the page
  3. No edits, but you do receive several comments and questions on the page
  4. A wide variety of edits ranging from minor to major and coming from your team as well as from people you don't know
• Your boss asks to review the latest version of a document you've been working on. You sent her the link to the wiki page where it's stored. What's her response?
  
  1. Can you attach the file and send it to me?
  2. I couldn't figure out how to make any changes so I've just included them in the attached MS Word file
  3. She makes her edits as comments to the page
  4. She edits the page directly
• The conversations that occur within your community most resemble:
  1. An empty room
  2. A board meeting
  3. Happy hour
  4. The hallways at the office
• It's Friday night and you just discovered that you have a TPS report due first thing Monday morning. To do it, you need some examples of similar reports that have been produced by other teams. Where do you head first?
  
  1. You email your immediate team
  2. You send a blast email out to multiple distro lists asking for help. After all, at least one or two people have to respond, right?
  3. You search your Intranet with every keyword you can imagine
  4. You search the TPS forum and post your request there

Do you have a better idea of what kind of community you're building? Healthy communities aren't just about collecting users – they're about interactivity, a positive atmosphere, usefulness and more. Why do you log into Facebook every day? Not to play with all of the cool features, but to interact with your friends and family. Internal communities should have some of these same qualities – they need to have a purpose and be based around human interactions, not the latest technology.

If your score was 16 or less, you don't have a community, you've got the man cave of a new dad. The place is filled with the latest technical toys but no one is around to use them. From the Xbox to the pool table to the fully-stocked bar, you had envisioned many nights partying with the boys watching football, but now that you have a new baby, the only thing all those toys are doing is collecting dust…just like your blogs, wiki pages, and profiles.

If your score was between 17 – 24, your community most resembles China. You've got a lot of users (primarily because people are forced to create profiles), but very little sense of community. People talk with one another because they have to, and only when they need something. Conversations are guarded and transactional, and information is protected even more closely as trust between individuals is lacking. Non-work conversations are prohibited – none of that "social networking" stuff here!

If your score was between 25 – 33, your community is most like a high school full of people still trying to figure out who they are, who their friends are, and how to communicate with each other. The adults are confused by the kids, the kids are kind of wary of the adults, but they all co-exist fairly peacefully. Diverse cliques form early and often – iPhone enthusiasts, social media geeks, developers – all with different goals and reasons for being. A few individuals stand out and connect these cliques across the entire school. Social conversation occurs, but is often forced, as people are trying to fit in and test the boundaries of what is allowed and what isn't.

If your score was between 34 – 44, congratulations! You've got the makings of honest-to-goodness social business community. People willingly share information freely across geographic, administrative and cultural lines not because they have to, but because they realize that by pitching in and helping, everyone benefits. Conversations run the gamut – some days, they're about LOLCats, but on other days, they're focused on how to best create a culture of innovation. They are overwhelmingly professional in nature, but the content is also overwhelmingly informal. People are only vaguely aware of the number of abbreviations following someone's name and the titles that precede it, but hold the value an individual brings to the rest of the community in high regard. Employees willingly (and often) spend their own time and money to improve the community, whether via handing out awards or creating new features. And most importantly, this sense of community exists both online and off. From the conference room in the morning to my couch late at night, I know I'm not just an employee number, I'm a valued member of a community that depends on me.

I took this test for my own company's social Intranet tools, and I discovered that we're most like a high school. We still only have a fraction of the firm using the tools on a regular basis and the relationships between staff, management, and senior leadership are in that awkward stage where we're all still trying to figure out how to talk with one another.

(note: this isn't meant to be used as some formal "diagnostic" or "roadmap" or anything of the like so please take it for what it is – a fun way to gauge how well your community is actually acting like, you know, a community)

- Clay Shirky at TED Cannes in June 2010

This is one of my favorite quotes from one of my favorite people in the business, Clay Shirky. I particularly like it because it illustrates the period many organizations find themselves in when trying to integrate social media internally.  Before wikis were used by the Intelligence Community to develop reports on IEDs, people were creating user badges to show off their favorite NFL teams. Before my own company's Intranet won any awards, we had people talking about how they enjoy skinny dipping on their profile. Before our VPs starting using Yammer to communicate with the workforce, we had groups of Android geeks and fitness gurus.I'm telling you this because if you're implementing any type of social media behind your organizational firewall, you should prepare yourself, your colleagues, your bosses, your senior leadership for this one inexorable truth.

If you will freak out when you see this on your Intranet, you're probably not ready for a social intranet

Accept and embrace this fact now and your communities have a much better chance at succeeding. Or, continue thinking that things like this are a waste of a time and are unprofessional, and get ready to pay a lot of money for a system that ultimately no one uses unless they absolutely have to.

Unfortunately, "social" seems to have become almost a dirty word in the workplace, conjuring up images of employees whittling away their time on Facebook, talking to their boyfriend on the phone, or taking a three hour lunch break.  Let's all agree now to stop trying to take the social out of social media. "Social" interactions not only needs to be OK, they need to be encouraged and rewarded. Shirky explains why at the 5:33 mark of the below TED video:

Shirky says:

The gap is between doing anything and doing nothing. And someone who makes a LOLcat has already crossed over that gap. Now it’s tempting to want to get the Ushahidis without the LOLcats, right, to get the serious stuff without the throwaway stuff. But media abundance never works that way. Freedom to experiment means freedom to experiment with anything.

The same principle holds true when talking about social media and the business world. There's this tendency on the part of senior leadership to want to skip the blogs about company policy workarounds and the wiki pages detailing where to get the best burritos near the office and move right to co-creating methodologies with cross-functional teams and crowdsourcing initiatives that save millions of dollars. It doesn't work like that. Collaborative communities don't just start innovating because you build a website and send a memo. Just like we had to experience erotic novels before scientific journals and LOLCats before sites like Ushahidi, we will also have to accept the fact that your employees will be talking about fantasy football and what they're doing over the holidays before they're going to be ready to use those tools to conduct "real" work. 

This makes intuitive sense though, doesn't it? Isn't posting about fantasy football or your favorite lunch spot a lot easier (and less frightening) than uploading that report you've been working on for three weeks? If someone doesn't like your favorite restaurant, who cares? If, however, someone criticizes the report you've spent weeks writing, that's a little more intimidating.  Once you've taken that step – that step from doing nothing to doing something - it's a lot easier to take the next step and the step after that. After engaging in that conversation about your favorite burrito, it's suddenly easier to join the conversation about the new IT policy. Then, maybe you upload a portion of the report you're struggling with to see if anyone can help. Viewed from this perspective, even the stupidest posts and most worthless conversations have value, because they provide a safe, low risk means for people to dip their toe in the water and take that first step. 

It takes time for employees to feel comfortable using these social tools at work. If you give them the ability to grow and learn together at their own pace, your community will become much more scalable and sustainable.

So embrace the LOLCats, the fantasy football threads, the lunch discussions, and the custom avatars – at least your employees will be creating and sharing something with someone else. Because what will follow is that these stupid, silly, foolish discussions will lead to relationships, questions, answers, and finally, very cool innovations, products, and solutions that will save you money, win you awards, and really and truly create a social business.

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.“

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]

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?

Now, take a look at who is posting and commenting on these topics. Are these the same people who also have the most overall comments, posts, edits, and connections? If so, Mr. Popularity may be taking over your community and the worst part of it all? He may actually think he’s helping you.

You see, while these active champions are responsible for seeding a majority of the content, answering questions, posting content, editing pages, and creating topics, they can also skew the content to suit their own agenda and create a chilling effect on opposing viewpoints and topics. This makes your communities far more social media and technology-oriented than your organization really is. In the early days of your online community, this may be of little concern to you – content is being created, new members are joining, and discussions are happening. This creates a vibrant community for those employees interested in social media and technology, but unfortunately, further dissuades those interested in other topics from joining. Mr. Popularity, once an ally, now becomes a challenge to be overcome.

I’ve actually experienced the pros and the cons of being Mr. Popularity on our  own hello.bah.com community a few years ago. I was one of the first community managers and was a very visible and active champion for the platform. I became known as the guy who could get conversations started, who could help increase traffic to a post, and who would be willing to give an opinion when no one else would. Our internal communications staff was even pitching me to get me to share official corporate messages because I had built up a decent sized following on my blog. This worked out great in the beginning – I was able to help drive some additional traffic to the platform, increase user adoption, and create a ton of new content that was shared across the firm. The double-edged sword of being Mr. Popularity hit me right in the face though when I got the following email (excerpted below):

“When I ducked into our VP’s blog, I noted you had already jumped in with what appears to be a standard, or getting there, pat on the back and tutorial…  Are you becoming too intrusive beyond cheerleading?  The speed at which you’ve already entered the room is giving me the thought that you are becoming Master Control from the movie Tron. I can’t recall reading anyone’s blog that I can’t remember seeing you there in the first couple of replies.  You write extensive replies very quickly that to me verge on being somewhat inhibiting for others, like me, to weigh in so as to not repeat a point.”

Wow! And here I thought I was being helpful! I thought by commenting on everything I could get to, I could help build and reinforce the collaborative culture we were trying to create. And at first, that’s exactly what I was doing. Little did I know that as the community grew beyond the early adopters, my hyper-activity that was a boon at the start was now becoming a detriment. Instead of a community manager, was I becoming a community bully?

To find out if your Mr. Popularity is negatively impacting your community, ask yourself these questions:

1. Does Mr. Popularity know that he/she is having a negative impact? These active champions probably don’t even know that they’re causing harm. Quite the contrary – they probably believe that they’re helping. Like the email I received above, reach out to them and have a discussion with them about their contributions and show them areas where instead of helping create conversation, they may have inadvertently stopped it.
2. Who are your most active contributors beyond social media and technology? The best way to lessen the influence of Mr. Popularity is to identify people in other business areas who are willing and able to post and discuss content areas like HR, Legal, and Operations.
3. What is your role in the community? Do a bit of self-reflection – maybe you are Mr. Popularity. Talk to your colleagues and find out what they really think of your online presence. Do you come across as overbearing? Too focused on one topic? Closed off to other opinions? Publicly, you may be receiving all kinds of positive reinforcement. But what are people saying among themselves that they aren’t sharing publicly?
4. What other possible reasons exist for the gluttony of social media/tech-related topics? Are community members discouraged from discussing operations? Has the Director of HR banned his staff from participating? Having a few individuals who are hyper-active on your online community and skewing the conversations toward their interests is like having two good quarterbacks and not being able to decide which one to start. It’s usually a good problem to have, and despite some of the challenges identified in this post, they are still likely helping more than they’re hurting your community.

Mr. Popularity isn’t necessarily a detriment to your community. Quite the contrary – they’re likely some of your most valuable members. But, left unchecked, they do have the potential to take over the community – its members, its content, and its discussion. The key is in channeling their energy and enthusiasm and focus it on helping grow the community as a whole, to include topics other than social media and technology.

*This post originally appeared on my AIIM Enterprise 2.0 Community blog.

I’ve written before about the need to start talking about failures at conferences so that others may learn, so that’s why I was excited to attend Kevin Jones‘ presentation, “Enterprise 2.0 Failures – And What We Learn From Them,” yesterday at the Enterprise 2.0 Conference here in Boston. Kevin is a Social Media & Network Strategist/Manager at NASA’s Marshall Space Flight Center, and he gave us several “ways to fail” at Enterprise 2.0 based on his experiences at NASA. Update: Make sure you check out Kevin’s post on his presentation as well as his slides/video that he used.

Here are ten that I particularly liked:

How to Fail at Enterprise 2.0

1. Work in a Culture of Low Trust - Kevin said he was talking to one manager who said, “I just don’t trust my people. “If they bash another group, I don’t want that group to see it. Their English is really horrible – I don’t want anyone else in the organization to know that my people are idiots.”  You could have the greatest tools in the world, but no blog or wiki is going to work if this is the culture in which it’s implemented.
2. Rely on Stats - Trotting all of the latest industry stats on Enterprise 2.0 adoption and spending is great, but nothing resonates as well with a senior leader as actually getting them to sit down and use the tools until they have that “ah-ha” moment for themselves.
3. Underestimate the Political Landscape - Kevin had “a NASA employee assigned to watch over me to keep me out of trouble, but I still got my hand slapped multiple times.”  He was told by the CIO to let him know if he encounters any problems, but then another senior leader told him that he wasn’t allowed to speak to the CIO unless he was accompanied by this other leader. Not understanding the unique office politics at play and how to make them work for you is a recurring theme in Enterprise 2.0 failures.
4. Ignore people who have done this before – This is the “but I’m unique!” argument. Everyone thinks their organization is unique and different from everyone else that they ignore the lessons learned and best practices of others in their organization and assume that they know best. Unfortunately, they usually don’t.
5. Treat this as YOUR project – At first, Kevin thought of himself as the Head of All Things Social. He soon realized that he was spinning his wheels as others weren’t buying into his vision. Not until he gave others ownership over certain parts of the strategy did he start to garner support.
6. Treat this as an IT project - In Enterprise 2.0 implementations, the money often comes from the IT department, and unfortunately, that means that these initiatives are often implemented like an IT project. “Let’s just get the tools up and running – we’ll worry about the people later!” Enterprise 2.0 has to be treated like people project with an IT component, not the other way around.
7. Go Cheap – You get what you pay for, in terms of hardware, software, and people. Kevin mentioned that he led this huge promotional push to get people to log into the platform and it worked! Unfortunately, it worked much better than the IT people thought it would, and they didn’t have the right server space/bandwidth in place to handle the influx of people. So instead of a good news story about user adoption, it turned into people logging into a new collaboration site, only to receive a 404 error. You can’t commit halfway to Enterprise 2.0 – you can’t say, “well, we can afford the tools, but not the community managers” or vice versa.
8. Assume this is about collaboration, being social - Enterprise 2.0 isn’t about creating a Facebook behind the firewall or giving people a way to collaborate. It’s about using technology to help employees do their work. The ability to create a blog that your co-workers can read is meaningless to most people. The ability to easily update and share your weekly status report with your entire project team without having to sift through multiple versions in your inbox? Now that’s something they can get on board with.
9. Make Policy Ugly – Forcing your people to read and agree to a lengthy document filled with do not do this, do not do that legal-ese is akin to putting up a “Beware of Dog! No Trespassing!” sign on your front gate. That doesn’t say come on in and collaborate – that says, we’re protecting our butt because we don’t trust you.
10. Forget that you’re working with humans – These aren’t “users” or “visitors” you’re dealing with. These are people. These are your colleagues. They want to feel like they’re joining a community of other people who can help them, not using some impersonal tool with strict rules and policies governing their every move.

*The title is a quote from Ben Franklin

In the fall I wrote a guest post entitled, “But I Don’t WANNA Change” about using change management techniques to encourage the adoption of social media within organizations. Over the past six months, I have seen how many people are interested in this topic, and I will be discussing it again at the Association for Change Management Professional’s conference May 1-4. One thing I have learned, however, is that even though social media is sweeping the world, that doesn’t mean your internal platform will engage your employees.

Social Media is Fast

Collage of social media icons

Photo Credit: Flickr, myretailmedia

Over the past five or six years we have seen a societal transformation take shape. Social Media has forever changed the way the world communicates. At the root of that change is behavior change; the idea that people had to learn to start doing something in a new way. There are always those early adopters (think Twitter users in 2007, Facebook users in 2004), but generally large-scale adoption of new communications tools takes years, often decades (think radio and television) – until now. Social media has raced across the globe in just a few years, with billions now taking part.

Social media has even had time to have what I call ‘nano-changes’ (nano as in rapid changes within a larger change). In the last several years we’ve seen a remarkable shift from blogs and discussion forums to instant update platforms like Twitter and Foursquare. There has also been a substantial move to mobile technology.

Behavior Change is Slow

A turtle slowly plods along

Photo Credit: Flickr, jhoward413

So how does understanding this information help you build a successful internal social media platform? Because to unleash the power of social media you have to understand human behavior. We are social creatures, but businesses that assume our social tendencies will ensure the success of a new collaboration platform are gravely mistaken. Why? Because they underestimate one crucial human behavior, we are social creatures AND creatures of habit. Change is hard, change is work, and getting people to change behavior requires significant effort.

These platforms often fail because:

1. They are poorly implemented and explained
2. Users don’t have a clear understanding of why using the site will help them
3. Leadership doesn’t lead by example and engage users via the platform
4. The tools don’t provide meaningful, updated information
5. They weren’t designed with the end-user in mind, so the user interface is complicated or confusing
6. They don’t continue to evolve

Here’s my take on each of these issues.

1. Solve a specific problem: A poorly implemented and explained IT implementation will always fail. (And make no mistake building an internal collaboration platform is an IT implementation.) My previous post has some detail around this particular issue, but one point reigns supreme: build the platform to meet a business need. Define the goal clearly and help employees understand how this new platform will achieve that goal. Is your goal to train employees, improve morale, or communicate more effectively to a global workforce? Define the goal, then design the platform to achieve it, and then communicate the hell out of it!

2. Clear vision: If users don’t understand what it is or why they should use it, it’s because the vision for the project was not clearly articulated. Take this example:

We are designing a web portal that through a user authentication process will enable simultaneous global interactions in a safe, behind-the-firewall employee collaboration platform.
OR
We’re creating a secure website where our employees can collaborate, share ideas, and inspire one another.

Articulating the vision is leadership’s responsibility, and the first step is to make certain people understand the critical elements. The second message clearly explains what it is, who it’s for, and what the benefits are, without using jargon.

3. Lead by example: If your CEO is still sending mass emails to everyone instead of launching the latest firm initiative via the new platform, then employees are receiving conflicting messages. Not only that, but if leadership is noticeably absent from the blogs, discussion forums, or communities created in the new platform then they are not reinforcing the use of the tool by modeling the behavior they expect to see – the employee thinks, ‘well the boss doesn’t use it, why should I bother to learn how?’

4. Content drives adoption: If people find the content engaging, informative, and useful they will return, if they don’t they are history. There are two parts to this: first, the content must be provided in an interesting manner. Don’t just post the company’s newsletter on the platform – make it interactive, use the discussion forum to determine the content for the next newsletter, etc. Second, the content needs to be consistently updated, which means you have to allocate enough resources to make sure the platform stays relevant and organized.

5. User first! It is always surprising to me how often the simplest (and arguably most important) issue is lost in the myriad of technical details – if the user experience is poor, they won’t use the site. Very few people will take the time and money to do a full, extensive usability review, but there are other options. First, there is ‘do-it-yourself’ usability that can be quite helpful. Steve Krug has a great book on this topic that has practical tips that really can improve any website. Another solution is to launch your new platform in beta, tell everyone it’s in beta, ask for their honest, candid feedback, and then (here’s the trick) listen to them! People are MUCH more forgiving of a new platform if they can see the site improving and evolving, which brings me to my last point…

6. Evolve, evolve, evolve: A platform that doesn’t grow with the needs of its users, no matter how well promoted it is, will ultimately stagnate and die. You don’t have to have a complete overhaul every six months, but you do have to continue to provide your users with more value. The other key here – don’t just add stuff, go back to your business drivers and add the stuff that reinforces those business objectives. Ask users what features or functionality they would like, and if it’s technically feasible give it to them.

Each of the issues above are core change management principles: creating a sense of urgency, articulating a clear vision, leading by example, and gathering feedback to continually evolve are all crucial steps to ensuring a successful internal collaboration implementation. It’s not build it and they will come, it’s more like build it, do all of this hard work, get them involved, and then they will come! But hey, better that than yet another wiki that no one uses, right?

Michael Murray is an Associate at Booz Allen Hamilton, where he has helped clients use social media to engage people around the world and in the office across the hall.

It's a living

The Internal Community Manager wears many hats

While these positions may sound like the perfect job for the social media evangelist in your organization – moderate forums, write blog posts, garden the wiki, give briefings about social media, develop user adoption strategies, answer user questions, monitor and analyze user activity – the internal community manager actually wears many other hats, some of which aren’t nearly as fun and exciting, and many of which aren’t going to be high on the wish list of potential candidates. Let’s take a look at the many hats of the internal community manager:

• Referee – When someone posts a link to a political article and the conversation is starts to devolve into partisan name-calling and vitriol, guess who gets to be the one to steer the conversation back toward professionalism and healthy debate? Oh yeah, and you can’t use your admin privileges (the nuclear option) to just “lock” or delete the conversation either because then you’re not community manager, you’re big brother.
• Ombudsman – When the community starts complaining about the speed, reliability, or accessibility of the platform, you need to be the one to bring up those concerns with the developers and push to get these issues fixed. If a new feature is riddled with bugs, you can’t just toe the company line and say it’s great – you have to be able to offer your honest, unbiased opinion. After all, you’re the advocate for the community, not a mouthpiece for the development team.
• Party Promoter – Know that guy passing out flyers outside the club you walked past earlier today? Yeah, that’s going to be you. You’ll be handing out flyers, sending emails, giving briefings – anything you can do to get people to come by and check out your community.
• Comedian - You can’t take the ‘social’ out of social media. There has to be someone there who can show the rest of the community how to have a little fun, and the community manager has to be comfortable using humor in a professional environment (no, those are not mutually exclusive).
• Teacher – Ever try to teach someone to change their golf swing after they’ve been doing it the same way for 20 years? Get ready for a lot more of that feeling. It’s very much like trying to teach someone to use a wiki for collaboration instead of using email. Get used to people copying and pasting the content off the wiki and into a Word document, turning on track changes, and then sending you the marked-up Word document for you to “take a look at” before uploading to the wiki.
• Inspirational Leader – You will not have enough hours in the day to do everything you want. You cannot possibly garden the wiki, write your blog posts, moderate all of the forums, stay active on Yammer, run your metrics reports and do everything else a community manager is asked to do by yourself. You’re going to need to identify others in the community to help you, and oh by the way, you’ll need to get them to buy into your approach and do the work but you won’t have any actual authority and they’ll all have other jobs too.  Good luck!
• Help Desk – When the WYSIWYG editor on the blogs isn’t working right, guess who the users are going to call? The answer isn’t the help(less) desk. It’s you. You’re going to receive emails, Yams, phone calls, and IMs from everyone asking for your help because you’re the person they see most often and using the platform. Who are they going to trust to get them an answer – the person they see using the platform every day or some faceless/nameless guy behind a distro list email?
• Psychiatrist – When that executive starts a blog and no one reads it or comments on it, you have to be ready to go into full out touchy-feely mode and help reassure him/her, manage their expectations, give them some tips and tricks, and build their self-esteem back up so that they will continue being active. For someone who was able to live off their title for so long, getting out there and having to prove oneself with their content again can be a tricky proposition.
• Troublemaker - Work conversations can get pretty boring – a community filled with blog posts about your revisions to the TPS reports aren’t exactly going to elicit a lot of conversation. You will have to be the one who can start start and manage difficult conversations with the community. Guess who gets the write the blog post criticizing the new expense reporting policy?
• Cheerleader – When community members use the platform in the right way and/or contributes something really valuable, you need to be the first one to share it as far and wide as possible. You need to be the person putting that community member’s face on the front page and tell everyone else what he did and how others can be like him. You need to be the one cheering people on to give them the positive reinforcement they need.
• Project Manager – These communities don’t build themselves. You’re going to be responsible for creating and delivering all kinds of reports, briefings, fact sheets, and metrics and you’re going to need a plan for how to meet those deadlines and still engage with the community itself.
• Writer - Every community platform has some sort of front page along with some static “About this community” type of content. You need to be able to write that content in a way that’s professional yet informal enough that people will still read it.
• Janitor - When you open up your local shared drive, you’re likely to see 47 different version of the same document, hopefully, with one of those containing a big FINAL in the filename. The old version are good to keep around just in case, but all they’re really doing is cluttering up the folder and making it difficult to find anything. The same thing happens in an online community. People post things in the wrong forums, they accidentally publish half-written blog posts, they upload documents without tagging them, etc. You get to go in and clean up these messes!

Wow – when you spell all out like that, maybe being an internal community manager isn’t such a great position after all. Seems like it’s a lot more difficult than simply blogging, managing user accounts, and coordinating change requests! Before you grab that one guy on your team who has some extra time on his hands and volunteer him for your new community management role, you might want to think about these other hats he’s going to have to wear and really ask yourself if Johnny, your social media intern, is really the right man for the job or if you should hire an experienced community manager.

Stop worrying about hitting the big drive and concentrate on the fundamentals

Ever hear the phrase “Drive for Show, Putt for Dough?”  It’s  time-honored sports cliche that refers to the oohs and ahhs that a huge golf drive off the tee will elicit from the crowd. However, despite all the attention a big drive gets and hundreds of dollars a good driver costs, that shot is used maybe 12 times each round. The real money is made on the green where an average player will take almost 3 times as many strokes. You can make all the highlight reels you want with your 350 yard drives, but if you can’t make a 10 foot putt consistently, you’ll be in the same place I am on Sunday….on the couch watching someone else who CAN make those putts.

I bring this up because I’ve seen one too many Enterprise 2.0 implementation – be it a wiki, a blogging platform, discussion forums, microblogging, or Sharepoint – fail miserably because they forgot to focus on the fundamentals.  They end up being too concerned with the big drive off the tee that they forget to practice the short putts that are needed to truly succeed. Nearly every Enterprise 2.0 vendor out there offers a similar set of features – blogging, microblogging, wiki functionality, profiles, tagging, search, etc. – they all hype up the fact that THEIR platform is the one that can do X or can do Y, that they have this one unique feature that puts them out in front of the competition. Likewise, once these platforms are purchased and installed, the client teams responsible for customization and integration get enamored with all of these features as well. I’ve seen way too many internal launch emails that sound something like this:

“Visit our new website, the one-stop shop for all your collaboration needs. This new website offers all of the Web 2.0 functionality that you have on the Internet, here in a safe, secure, professional environment – blogs to share your expertise, a wiki that anyone can edit, profiles so that you can connect with your colleagues!”

Seeing all this empty promotional language makes me think of my friend who absolutely crushes the ball of the tee. After another monster shot from the fairway, he’s now gone 524 yards in two shots and the crowd is loving it. He then proceeds to take three putts to go the final 10 yards because he spent all of his money on a new driver and practice time on perfecting the big drive.

Unfortunately, Enterprise 2.0 implementations are suffering from this same, all too common problem.

Day 1: After being enticed by the blogs, the wikis, the microblogging, and the rest of the features, you visit the site, you poke around a little bit – so far so good.  Everything looks great.  The design is eye-catching, there’s a lot of great content up already, some of my peers have friended me, and I already found a blog post relevant to my job. This is the best site ever! Enterprise 2.0 FTW!

Day 2: I visit the site again and invite a few of my managers to join as well…well, I tried to invite them to join, but the invite a friend button wasn’t quite working. That’s ok – I’ll try again tomorrow – must be a bug.  I can’t wait to get them using all of these cool tools too!

Day 3: Well, that invite-a-friend bug still isn’t fixed, but everything else is going pretty smoothly…other than the fact that the blogs don’t seem to work in Firefox. I guess I’ll have to use Internet Explorer for those, but that’s ok.

Day 7:  I’ve got a big meeting today with the new VP at this conference we’re both attending – I’ll demo all these new social media tools for him and show him how he can start a blog too!

Day 7 (later on): Damnit! I didn’t realize that I wouldn’t be able to access the site unless I was behind the firewall in one our corporate offices

Day 14: On my way to a meeting, I was checking out my co-worker’s Facebook page on my iPhone when I saw his latest status update – “OMG – I can’t believe that someone said that about our new HR policy on our corporate blog!!” Intrigued by what was said on the new blog, I try to navigate to our blogs…foiled again!!!  No mobile support….I guess I’ll check it later tonight.

Day 17: Working late on a report again – luckily, I’ve been posting all of my findings to our new wiki so that when I leave for my vacation tomorrow, everyone will have easy access to the latest and greatest data.

Day 18: Disappointed to receive an email on my way to the airport that our Enterprise 2.0 site is down for maintenance for the rest of the day, rendering all of my data unusable to the rest of my team. They can’t wait a day for the wiki to come back up so it looks like they’ll be working extra hard to recreate everything I did last night.

Day 19: &*%$ I’m DONE!!!  Why is this thing so slow?  What does Facebook have 500 million users yet is always up?  Why can I download a movie from iTunes in 3 minutes, but it takes me 25 minutes to download a Powerpoint presentation?  Why can I read Deadspin from my phone no matter where I’m at in world, but can’t access the blog I’m supposed to be using for work?

Sound familiar to anyone? This is what happens when Enterprise 2.0 is too focused on the teeshot, and not enough on the fundamentals of the rest of the game. Features galore that will get people ooohhing and aahhhing, but lacking the fundamentals of speed, accessibility, and reliability that will keep people coming back. If you’re talking about implementing an Enterprise 2.0 platform, before you start talking about all of the bells and whistles you want, make sure that you take care of three very fundamental issues.

Make it Fast – People have to expect anything online to be fast. If I click something, it should take me there immediately. There are no exceptions. Load times for simple html pages (we’ll give multimedia an exception here) should be almost non-existent. I don’t care if I’m behind a corporate firewall or not – if it takes 4-5 seconds to load a page, that’s going to severely limit how often I can use it. If my bank’s site can be secure and fast, why can’t my Intranet sites?

Make it Accessible – Laptops, desktops, iPads, iPhones, Android devices, my old school flip phone, hell, even my TV all allow me to get online now.  I can access Pandora, Facebook, Twitter, and a whole host of other sites from a dozen different devices while on the subway, in my house, in a rain forest, or in my office.  But, you’re telling me that I can only access my work from one kind of computer that’s located in one place? Doesn’t seem to make much sense.

Make it Reliable – There shouldn’t be a fail-whale on your internal work systems. If I need to access some information to do my job – be it a blog post, a wiki page, or a file – I need to be able to access it, with 100% certainty.  If I need access to some data for an important meeting, and I can’t access it because our site is “down for maintenance” or it was accidentally deleted in some sort of data migration error, that’s a serious breach of trust that is going to make me question whether I should be using the site at all.

Concentrate on perfecting the fundamentals before you start getting into the fancy stuff – practice your putting before your driving, learn to dribble with both hands before entering a dunk contest, practice catching the ball before you choreograph your touchdown dance, and make the wiki work in Firefox before you start working on some drag and drop home page modules.

Photo courtesy Flickr user Stev.ie