Government 2.0: architecting for collaboration

52
government 2.0 architecting for collaboration by tara ‘missrogue’ hunt citizen agency

description

Unfortunately, the video won't embed this way. :( And it makes it soooo awesome. So, here is where to find them: 1. The Day of the Longtail By Michael Markman, Peter Hirshberg, Bob Kalsey; Produced for The Computer History Museum http://www.youtube.com/watch?v=7xAA71Ssids 2. What the Heck is BarCamp? by Ryanne Hodson & Jay Dedman http://ryanedit.blogspot.com/2006/06/barcampsf.html 3. Transit Camp on CityTV http://www.youtube.com/watch?v=PDkEPvIwarI

Transcript of Government 2.0: architecting for collaboration

Page 1: Government 2.0: architecting for collaboration

government 2.0architecting for collaboration

bytara ‘missrogue’ hunt

citizen agency

Page 2: Government 2.0: architecting for collaboration

Tēnā koutou katoa

Page 3: Government 2.0: architecting for collaboration

who am I?

Page 4: Government 2.0: architecting for collaboration

the framework:web 2.0

Page 5: Government 2.0: architecting for collaboration

“... far from having “crashed”, the web was more important than ever, with exciting new applications

and sites popping up with surprising regularity ... Could it be that the dot-com collapse marked some kind of turning point for the web, such that a call to

action such as “Web 2.0” might make sense?”

Tim O’Reilly on the birth of Web 2.0

Page 6: Government 2.0: architecting for collaboration

web 1.0 web 2.0

read only read/write

top down bottom up

Page 7: Government 2.0: architecting for collaboration

1. the web as a platform

2. the long tail

3. data is the next intel inside

4. users add value

5. network effects by default

6. some rights reserved

7. the perpetual beta

8. cooperate, don’t control

9. software above the level of a single device

core tenets of web 2.0

Page 8: Government 2.0: architecting for collaboration

the road to government 2.0

Page 9: Government 2.0: architecting for collaboration

core tenets of government 2.01. the government is my springboard

2. the long, diverse tail of citizens

3. data is...tricky

4. going to the edges for feedback

5. the citizen community: it’s about relationships

6. some rights reserved

7. evolution is an ongoing process

8. trust is the truest way to empowerment

9. government on-the-go

Page 10: Government 2.0: architecting for collaboration

#1. the government is my springboard“government services as a platform”

Page 11: Government 2.0: architecting for collaboration

platforms are enablers between:

• two parties

• the user and her experience

Page 12: Government 2.0: architecting for collaboration

the government is an enabler between:

• individual citizens

• a citizen and a service provider

• a researcher and information

• a citizen and a public servant

• a citizen and her information

• a citizen and her experience with the gov’t

• etc.

Page 13: Government 2.0: architecting for collaboration

the best platforms are:

1. modular & extensible (i.e. Firefox, Wordpress]

2. add a secure layer [i.e. Paypal, Verisign]

3. leverage the network to create promotional opportunities for users [i.e. eBay, Craigslist, Trademe]

4. create interoperability & accessibility [i.e. HTML, Microformats]

5. enable symbiotic relationships [i.e. P2P networks]

more...

Page 14: Government 2.0: architecting for collaboration

the best platforms are:

6. have multiple data on/offramps [i.e. Flickr, Twitter]

7. use the data to enhance user experience [i.e. Amazon, last.fm]

8. spawn or boost new industries [i.e. Blogger & YouTube]

9. do one thing extremely well and invisibly [i.e. Google]

Page 15: Government 2.0: architecting for collaboration

homework

• how can your organization be a platform?

• how can you enable/ignite industries to be built?

• are you enabling or controlling?

Page 16: Government 2.0: architecting for collaboration

#2. the long, diverse tail of citizens“the long tail of government services”

Page 17: Government 2.0: architecting for collaboration

the audience is...

Peter Hirshberg - “The Day of the Longtail”

Page 18: Government 2.0: architecting for collaboration

the forces of the long tail

1. democratize the tools of production

2. democratize the means of distribution

3. connect supply and demand

Chris Anderson [the Long Tail]

Page 19: Government 2.0: architecting for collaboration

the forces of the long tail

force business example

nodemocratize production

long tail toolmakers, producers

Digital videocameras, desktop music and video editing software, blogging

tools

okdemocratize distribution

long tail aggregators Amazon, eBay, iTunes, etc

bestconnect supply &

demandlong tail filters

Google, Technorati, Rhapsody, recommendations,

etc.

Page 20: Government 2.0: architecting for collaboration

case study: the citizen archivist

Page 21: Government 2.0: architecting for collaboration
Page 22: Government 2.0: architecting for collaboration

#3. data is...tricky“government holds the ultimate ‘intel inside’...whatcha gonna do with it?”

Page 23: Government 2.0: architecting for collaboration

all your base are belong to us

Page 24: Government 2.0: architecting for collaboration

knowledge is power

data in the hands of a few makes for order; but data in the hands of many makes for

endless possibilities

Page 25: Government 2.0: architecting for collaboration

case study: health records

Page 26: Government 2.0: architecting for collaboration

#4. going to the edges for feedback“people’s voices add value and they are talking”

Page 27: Government 2.0: architecting for collaboration

feedback 1.0asking people to fill out surveys and questionnaires& collecting census data (still important, but not everything)

Page 28: Government 2.0: architecting for collaboration

feedback 2.0Listening & Learning

Page 29: Government 2.0: architecting for collaboration

how to go to the edges 101

1. bring anecdotes and feedback from customer service to everyone’s attention

2. fill your RSS readers with blogs you find by a NZ citizen & listen to what they are thinking about

3. start collecting attention data

4. involve the public (not focus groups) in planning: be open, transparent and ask for feedback

5. learn how to respond to feedback productively

Page 30: Government 2.0: architecting for collaboration

#5. the citizen community“there is already a network, build relationships”

Page 31: Government 2.0: architecting for collaboration

He aha te mea nui o te ao? He tangata! He tangata! He

tangata!

Page 32: Government 2.0: architecting for collaboration

Ryanne Hodsen - “What the heck is Barcamp?”

Page 33: Government 2.0: architecting for collaboration

where gov’t services fits in

We need to change the way we approach service, viewing the public not as a recipient, but as more of a partner. And government

services are the platform that enables more of these projects to grow and be born in a

country as forward thinking as New Zealand.

Page 34: Government 2.0: architecting for collaboration

case study:Toronto Transit Camp

Page 35: Government 2.0: architecting for collaboration

toronto transitcamp in the news

http://transitcamp.org/

Page 36: Government 2.0: architecting for collaboration

#6. some rights reserved“what Larry said...”

Page 37: Government 2.0: architecting for collaboration

nine inch nails

Page 38: Government 2.0: architecting for collaboration

#7. evolution is an ongoing process“government as a perpetual beta”

Page 39: Government 2.0: architecting for collaboration

ha-ha study: the paperwork reduction project

Page 40: Government 2.0: architecting for collaboration

Burden Estimate Statement“The estimated average burden associated with this collection of information is 15 minutes per respondent or recordkeeper, depending on individual circumstances. Comments concerning

the accuracy of this burden estimate and suggestions for reducing this burden should be directed to the Financial

Management Service, Facilities Management Division, Property and Supply Branch, Room B-101, 3700 East West Highway, Hyattsville, MD 20782 and the Office of Management and

Budget, Paperwork Reduction Project (1510-0056), Washington, DC 20503.”

Page 41: Government 2.0: architecting for collaboration
Page 42: Government 2.0: architecting for collaboration
Page 43: Government 2.0: architecting for collaboration
Page 44: Government 2.0: architecting for collaboration
Page 45: Government 2.0: architecting for collaboration
Page 46: Government 2.0: architecting for collaboration

#8. trust is the truest way to empowerment“cooperate with, don’t control your citizens”

Page 47: Government 2.0: architecting for collaboration

“Virtually every commercial transaction has within itself an element of trust, certainly any

transaction conducted over a period of time. It can be plausibly argued that much of the

economic backwardness in the world can be explained by the lack of mutual confidence.”

- K. Arrow (1972) -

on trust

Page 48: Government 2.0: architecting for collaboration

#9. government on-the-go“the multiple ways to access government services”

Page 49: Government 2.0: architecting for collaboration

imagining the possibilities...

Page 50: Government 2.0: architecting for collaboration

licensing:

http://www.slideshare.net/missrogue

Page 51: Government 2.0: architecting for collaboration

about those rockin’ images:• Most are from iStockphoto.com (totally cool site)

• except for:

• me [on Flickr.com/photos/missrogue) p.3

• video of “The Day of the Longtail” by Peter Hirshberg p.17

• screenshot of NZ History online by Skitch (Plasq) p. 21

• image of “All Your Data Are Belong to Us” from ? p.23

• video of “What is BarCamp?” by Ryanne Hodsen p.32

• toronto transit camp buttons by Tom Purves on Flickr p.34

• toronto transit camp video from CityTV.ca p. 35

• images icanhascheezburger.com p.41-45

Page 52: Government 2.0: architecting for collaboration

Tara Hunt

[email protected]

skype: tarahunt747

www.citizenagency.comwww.horsepigcow.com