Oct 1st, 2009 |
Eric Sauve, TomoyeGovernment 2.0: Communities & Social Networking for Sharepoint - Part 3
Governments are looking for ways to leverage Web 2.0 communities and social networking within their organizations, many looking to do so based on their commitment and interest in Microsoft SharePoint. Based on nine years of experience working in this field, there are a number of principles organizations can apply to successfully deploy communities in social networking. In this three part series, I will outline 11 principles for social networking on the SharePoint platform, or more generally.
This week, I’m going to tackle the final three principles for government 2.0 – the importance of design, status updates and follow the data
Principle #9 – Design Can Make a Big Difference
While in theory, this principle may seem like a no-brainer, it is important when it comes to government 2.0 to keep in mind that small design changes can make a big difference. Taking the time to understand the positioning of the community, along with how exactly people use different features, is key to the success or failure of a government 2.0 strategy. For example, a community deployment within the US military made a number of fairly minor design changes, and they were able to dramatically increase the number of views, visits, comments, blogs, bookmarks and question replies with very little growth in the total number of community members. A small change to the commenting feature resulted in a more than 350% increase in the number of comments being made within the community.
Principle #10 – Status Updates
Consumer social networking has driven the status update phenomenon, with most services including function so we can see what our friends, family, coworkers and other associates are up to. While it may seem that the status update is too frivolous or fun for the enterprise, it offers a powerful tool to engage users within communities.

Within a social learning community, setting the status update to what are you learning provides a relatively simple, yet robust way to communicate with and engage others in the community. Status updates are particularly interesting as they have proven very effective within consumer social networking sites and now users are comfortable with communicating in this manner. They provide an easy way to engage users that may be hesitant to participate as the approach closely mirrors something they are likely doing on a personal level. As these users visit the site to do status updates they are apt to become engaged in other activities over time.
Principle #11 – Follow the Data
In the enterprise there are multiple technology products and solutions to support a wide variety of essential business process needs. Government 2.0 applications are not intended to replace these approaches but to take their data and make them relevant to a broader audience and contextualize them with the wisdom of the crowds. One example is at the Defense Acquisition University in the United States where they produce guidance for military acquisitions. In this context, producing documents are highly structured and require multiple levels of sign-off before the document is complete. In this case they use SharePoint for document routing. However, at inflection points in the process and at the end, this document needs to be disseminated and used by a broad community in a Web 2.0 style context. The key is to make it easy for data in these workflow driven systems like SharePoint to become visible and usable by a broad enterprise audience.
Government 2.0 offers organizations a new and tangible way to drive business results using proven technologies and approaches from social networking. Applying the above principles can enable organizations across the public and private sector to make Government 2.0 and communities a success.


Last week I joined 70 of my GC colleagues at the first 
