« Tech Republic recently posted on 10 things you should cover in your social networking policy. There has been a lot of discussion on this topic, including my prior post, Social Media Policy Outside and Inside the Enterprise. Like most policy discussions I have seen, this one focuses on social software use on the Web. However, it remains no less importance to have guidelines that also cover usage inside the enterprise. I think the ten points are very useful and eight apply to internal use, some more than others.
I am listing the points but reflecting on internal issues, rather than the external issues that Tech Republic focused on. I think that 8 of the 10 points are still relevant. «
- The company should encourage the use of social media for business within the enterprise but it needs to convey that in the policy. It still needs to define how it is best used and why it should be used, as well as the benefits.
- “It may seem obvious, but it is important that your policy define what is meant by “social networking” or “social media,” since the term means different things to different people.”
- This remains an issue inside the enterprise. These policies should not be oppressive and should not discourage use
« In the recent Gartner Social Software Hype Cycle, analyst Anthony Bradley introduced a new category, Activity-Specific Social Applications:
“As social software implementations mature, application patterns are evolving, and the software industry is responding with activity-centric social application offerings rather than with generic social software capability suites. Delivering a targeted social solution with a general purpose social tool (such as wikis and blogs) can involve significant development, configuration, and templating effort.” »
- Bradley has identified the next opportunity in enterprise social social software. Integrating the valuable characteristics of social software into the in-the-flow activities that make up our days.
- People [who fail] don’t integrate CRM into the other parts of their business or implement CRM as a stand-alone and don’t have it communicate with core systems. A bigger and more frequent stumbling block is forgetting to address the people issues around a CRM implementation. In almost all of the cases we described earlier, CRM is a behavior modification tool.