ALGIM 2009: Gov 2.0

1,237 views

Published on

I wrote and presented this talk to the 2009 conference of Association of Local Government IT Managers (ALGIM) in November 2009. I attempted to move from specific examples of Gov 2.0 in action to a wider view of what it all means in the bigger picture.

Published in: Technology, Business
1 Comment
2 Likes
Statistics
Notes
  • Video of this talk is available here http://www.slideshare.net/gnat/algim-2009-gov-20
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,237
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

ALGIM 2009: Gov 2.0

  1. 1. Gov 2.0 Roundup Nat Torkington ALGIM 2009 talk about me: decade in US, emerging technology, open source, telephony, bioinformatics, GPS. now returned to NZ and up to elbows in getting people in technology to think beyond their immediate problems Kiwi Foo Camp, Open New Zealand
  2. 2. The Brief Learn how Governments around the world are using the Internet to better reach citizens and partners to lower costs, collaborate, and create better outcomes for citizens and government.  Nat will cover social networking, collaborative Web 2.0 tools, open data, APIs, and citizen journalism, and won't try to sell you anything. big picture
  3. 3. Gov 2.0 • e-government • digital democracy • government 2.0 many names, same damn thing
  4. 4. Gov 2.0 Using modern Web/Internet tools and thinking to do things better. Web 2.0 systems that get better the more you use them
  5. 5. The Web ... • ... brings people together despite distance and time, • ... to collaborate, learn, and contribute, • ... in their own way and (often) in their own time. what the web does well
  6. 6. Government as a platform Tim O'Reilly's phrase
  7. 7. “shared services”
  8. 8. data.gov
  9. 9. 728 “raw” data sets catalog, not a warehouse
  10. 10. 353 web tools provided by agencies, not by externals this is where web mapping crap goes
  11. 11. 110k geodata layers zips and tars some directories
  12. 12. State Data Sites local govts following suit DC early leader here (the DC IT dir => white house)
  13. 13. data.govt.nz Now we have our own DIA Open New Zealand
  14. 14. Successful Data Sharing • Machine-readable • Open standards where possible • Legally reusable • Documented • Pre-approved "Pre-approved" = no manual intervention to get access to the data
  15. 15. Do it once and reuse! no need to reinvent licenses, standards, tar vs zip, etc. each time. Well-oiled machine!
  16. 16. Why Share Data? • Ecosystem • “Not all the smart people work here” • “Not all the passionate people work here” • Cheaper in the long run • Sunlight • Create more value than you capture • Fact-based policy and commentary web map site vs web map data sunlight = can't sweep your crappy data under the rug, so you're doing it right create value = don't charge for it these are true for every piece of gov 2.0
  17. 17. Technology isn’t the answer Open up, reach beyond the org, involve others, think broader to be better Tech is means, not end
  18. 18. Audience • Partners • Local businesses • Constituents • Globals globals = people who arenʼt in your area, but can consume your data/APIs and deliver services google prime example adrian holovatyʼs
  19. 19. “grow the pie” in business we talk about growing the pie -- making the market bigger so everyone wins, including us.
  20. 20. apps.gov this is where the 3rd parties get PR give them some love, too example of growing the pie of love
  21. 21. enable self-service government is a platform for collective action but not every collective action should require the time of a paid government employee open systems are important here: low barriers
  22. 22. The Pillars • Government-to-Government • Citizen-to-Government • Government-to-Citizen • Citizen-to-Citizen
  23. 23. Food Safety FoodSafety New South Wales 3rd party app built using public-released data
  24. 24. zillow valuation info zoodle.co.nz trying to do this too
  25. 25. everyblock building permits in Chicago “citizen journalism” Adrian Holovaty
  26. 26. Wellibus app bundled database, so works offline and with iPod Touch TMRO kiwi-made
  27. 27. dataTO.org
  28. 28. Bi-directional so far itʼs govt-to-citizen how do we get the other flow? build a web site with a form? yes ... and no
  29. 29. Every web site is a compliance cost. Rod Drury
  30. 30. Government should make web services, not web sites. Rod Drury
  31. 31. Cons • Dependence • Bigger build • Ongoing operations • More complex than data tarball
  32. 32. Pros • Bidirectional • Live • Integrate into your workflow • “Automatic bizdev” aka magic integration • Integrated means automated
  33. 33. Amazon franchises their entire operation through APIs product catalog purchasing listing products infrastructure healthy ecosystem with Amazon in the center >1M affiliates, 180k API developers, total > 200M in revenue [next = ebay]
  34. 34. listing then selling after they maxed out listers >60% of items listed through API [next = google maps mobile]
  35. 35. Google Maps Mobile using local Wellington mobile technology! uses the API to access the servers The difference between Google and eBay is that eBay made money, Google lost it but Google plans to use the maps and eyeballs for local advertising
  36. 36. Ideas • FixMyStreet.com • Transportation • Permits transportation = payments toll road mumble grumble permits = beyond form, tracking process through system, updating. reducing workflow to state machine
  37. 37. Push and Pull • Apps already exist • You want apps to exist
  38. 38. Community this word already has meaning for you
  39. 39. Community • Must be nurtured • Who is good at this? • Code doesn’t make it happen you'd think local government would know how to make and run communities, but not necessarily a core strength -- your community always exists and is well defined. developers, you have to woo community manager role
  40. 40. Community Manager • CRM • bizdev • tech support • Camp Mother can learn from open source projects data.gov and others realising this
  41. 41. Social Media
  42. 42. Secrets to Success • Conversation • Real person • Augment, not Create • Public resolution don't just blurt out PR headlines into people's ears take the opportunity to put a professional yet human face on the organisation. doesn't have to be wacky piggyback on existing tech support or whatever. work with, not against. be seen to be engaging and doing good, get the thanks and love
  43. 43. The Golden Rule: Be Useful PR comes from doing good online, not from saying you're good
  44. 44. Managed Engagement What would happen if council staff engaged in the Facebook group discussions about their communities?
  45. 45. Customer Service • Telecom New Zealand • Vodafone New Zealand • Comcast (US)
  46. 46. Collaboration A different style of citizen-to-government
  47. 47. it.usaspending.gov can drill down into individual projects framed as “tell us where weʼre wasting money”
  48. 48. Sharedbook annotations to bills discussions another way to get feedback from citizens
  49. 49. gather the knowledge from your partners, suppliers, customers, employees
  50. 50. “Experience is a hard teacher, but a fool will have no other.” Going to crib from Tim OʼReilly and point out some things that have worked before.
  51. 51. Build open, extensible systems IBM PC took off because everyone could build compatible hardware Web took off because anyone could use code and build their own website, and they interoperated
  52. 52. Build simple systems, and let them evolve Twitterʼs original design doc was 1/2 a page of paper, and there are now 11,000 applications built on top of it (written by third parties). The hourglass model: run on many systems, support many applications, but connected by a common protocol. “Complex systems built from scratch never work. You need to build a simple system and let it grow… Complex problems paradoxically require simple answers.”
  53. 53. Design for cooperation Small systems loosely joined DNS is federated, not centralised
  54. 54. Learn from your users Google maps (used by 45% of all online mashups) hired the first guy to make a mashup fedspending.org used to be run by OMBwatch
  55. 55. Lower the barriers to experimentation Failure should be an option. Edison: “I didnʼt fail ten thousand times. I successfully eliminated, ten thousand times, materials and combinations that did not work.” Much innovation comes from a single engineer within an entity like the New York Times, putting archives up on an inexpensive, rented server from Amazon. The low cost of failure made it easier to experiment.
  56. 56. Build a culture of measurement Amazon driven by numbers Need good metrics! You are what you measure. theyworkforyou
  57. 57. Build a community You want this to succeed. You also want to get credit. (“Why do we need NOAA when we have weather.com?”)
  58. 58. Thank You Nathan Torkington nathan@torkington.com

×