3 popular ways to screw up enterprise social

3100602594_8506e805bb

Enterprise social networking may still be in its infancy when it comes to widespread adoption, but its popularity as a buzzword could hardly be hotter. What’s the result? A lot of folks with little experience of how to best use enterprise social tools rushing to introduce them. That’s not a recipe for a flawless roll out of new ways of working and sharing.

So what usually goes wrong? At Net:Work 2011 Podio CEO Tommy Ahlers suggested  companies often make things too complicated, complaining about “Swiss army knives” that try to solve every problem and end up failing users. When I spoke with Yammer CEO David Sacks a few weeks ago, he suggested that companies often go wrong by “trying to bolt that on to some existing tool, because if the tool isn’t built from the ground up to be social, it’s not going to have the level of usability that’s required.”

Now David Lavenda, VP of marketing at social email company harmon.ie, has gotten into the act, offering up common ways that well intentioned companies muck up the roll out of social tools and suggesting better ways to bring these tools to your team. “Simply throwing out social tools isn’t going to work,” he says, pointing to recent Forrester research that found widespread under-utilization of social tools. The study shows that even though companies have invested in an average of five or more tools, 64 percent realized few, if any, benefits from that investment. Only 8 percent actually use social collaboration software once a week.

So what should you do if you want your company or team’s move to social to go as poorly as some of the roll-outs documented by Forrester?

Imagine your team loves change. Some people like nothing better than to shake things up and try something new, but you can be pretty sure that’s not everyone on your team. So when you’re thinking about rolling out a tool to make your organization more social, keep in mind the howls of complaint that greet even the smallest changes to social networks in the consumer space.

“People are naturally reluctant to change,” says Lavenda. “Enterprise 2.0 author Andrew McAfee warns organizations to, ‘never underestimate the fondness of people and organizations for the status quo.’ When transitioning to a social model, it’s imperative to understand exactly how users work. Then, build a strategy and toolset that integrates with these practices in a way that makes sense with their current workflow, rather than asking users to make a dramatic change in their behavior.”

Rip and replace. If the wheel is turning along with just a bit of a creak or wobble, it’s not a good idea to try and entirely reinvent it. “People are often lured into thinking they need something entirely new to solve a problem. Instead of a D-Day approach that flips the switch on relatively unproven technologies like blogs, wikis and allied next-gen tools—essentially asking employees to immediately abandon existing tools like email and documents—plan for a gradual introduction that allows users to get up to speed with new functionality and capabilities at a comfortable pace,” recommends Lavenda, adding, “the idea is to improve productivity, not hinder it.”

The more the merrier. More may be better when it comes to chocolate cake or vacation days, but not when it comes to tools for the social enterprise. Rather than asking your team to log in to six different things, try to find solutions that allow them one go-to place for many needs. “An effective social strategy must start in a familiar environment and then aggregate all other pieces into the users’ base of operations. The goal is to eliminate steps, not add more. Bundling collaboration tools together in a common context and shared window drives faster, more widespread adoption and delivers the promised benefits of social enterprise integration much quicker,” says Lavenda.

Have you experienced any serious screw ups in the real of enterprise social that you’d like to warn others to avoid?

Image courtesy of Flickr user markomni.

loading

Comments have been disabled for this post