March 6, 2011
Ten Principles for Designing Open Government Institutions
The below tweets are @ThomKearney‘s attempt to share part of @BethNoveck‘s testimony to Cdn Parliament http://ow.ly/48GeM #w2p #goc on March 2nd, 2011
1. Go Open – Government should work in the open. contracts, grants, legislation, regulation and policies should be transparent #w2p #goc
2. Open Gov Includes Open Access – After the public has paid once, it shouldn’t have to pay again. #w2p #goc
3. Make Open Gov Productive Not Adversarial –Gov”t shld invest in providing the data that people really want and will use. #w2p #goc
4. Be Collaborative – Rulemaking should be open to public early to allow for constructive alternative proposals. #w2p #goc
5. Love Data – Design policies informed by real-time data. Release data for economic benefit. See http://ow.ly/48Ga7 for more #w2p #goc
6. Be Nimble – Forcing organizations to act quickly discourages bureaucracy and encourages creative brainstorming and innovation. #goc #w2p
7. Do More, Spend Less – Design solutions that do more with less. Instead of cutting… ask if there is another way…#w2p #goc
8. Invest in Platforms – … Focus on going forward practices of creating raw data and real engagement. #w2p #goc
9. Invest in People – Changing the culture of government will not happen through statements of policy alone…. #w2p #goc
10. Design for Democracy..ask if legislation enables engagement that uses people’s abilities and enthusiasm for the collective. #w2p #goc
Ten Principles from Beth Noveck @BethNoveck related via Twitter by @ThomKearney
The social media enthusiast that I am, I started wondering about how to continue improving constituent connections over the next five years here in wild, wonderful West Virginia. Yes, Facebook, Twitter, Tumblr, Foursquare, MeetUp, etc… all play a significant role, but there is something even bigger I believe we need to focus more efforts on: mobile government.
The Government of Canada is currently reliant on proprietary file formats and proprietary software applications, which lock it into a licensing bind with a single software manufacturer — Microsoft. There is not only a question of cost — as we pay a monopoly corporation for per-seat licenses to run software that already dominates the market — but more importantly, there is the question of future access to our own data. In this post, I’d like to share my thoughts on both issues.
This was the initial visualization graphic I developed quite awhile ago when I was first aligning types of Web 2.0 according to roles in Government.
