Most conversations about Government 2.0 assume that:
- Government provides data to citizens to provide openness and transparency
- Citizens engage with government to improve policy-making and service delivery
This approach implies that data flows from government to citizens and engagement flows from citizen to government. This is what I call the asymmetry of Government 2.0, since flows appear to be somewhat mono-directional, or very biased in a single direction. But these capture only one part of the story.
What about case managers who access to external communities rating government as well as non government care facilities to make a decision about where to place a case subject depending on a combination of financial constraints and customer ratings? What about a procurement officer looking at communities discussing prospective suppliers’ performances? Or HR professionals looking for information about candidates LinkedIn or Facebook? What about citizens tagging pictures put by museums and cultural heritage organizations on Flickr, so that they help the museum describe and organize their collections?
There are plenty of examples where data goes the other way around, from citizens to government, and government can use it in combination with data it owns (such as financial, HR, case-related ones, as well as taxonomies) in order to improve the way it deliver services or to initiate policy changes. A prediction we are about to publish says that by 2012 up to one in five government processes will be based on crowdsourced (i.e. external) data.
The assumption that citizens are mostly on the receiving end of open data and mashups needs to be changed. While the idea of citizens as application developers and data mashers is great, those who are most likely to benefit from all this are governments themselves, once they empower their employees to access, assess and use data outside their own perimeter.
Government 2.0 implies a bidirectional flow of information and services. It will require business intelligence suites that integrate data analytics with social networking analysis to help identify patterns revealing future behaviors; case management tools that give case managers the ability to alter case processing on the basis of data from external communities; online citizen services that can be integrated with third party portals; and indeed open data repositories that allow citizens to develop value added mashups and new applications.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.