Open data has been my life.
For a good number of years, open data has been my life: first at Code for America, where number of datasets opened and data portals launched annually were two of core metrics, and later at the City of Los Angeles, where managing, growing, and evangelizing open data was my stated top priority. Indeed, some of my most visible accomplishments have been publishing a book on open data, redesigning Los Angeles’ open data portal, and taking that city to #1 on the Open Data Census. I say all this in part just to emphasize that open data and open data portals, specifically, have been central to my career for some time.
You may then think this will all be about open data portals, what they are, why we need them, and how to make them better. In fact, that’s not at all what I’m about to do.
I actually think it’s time we abandon data portals altogether.
Why? Because I think there’s a couple of key trends, certain profound shifts happening in the tech industry in general and in government technology in particular that force us to rethink the way we approach data, and that’s what I want to talk to you about today.
Trend one. We’re moving from data to delivery.
Let’s step back to about 2008. Many good government organizations were working on opening up data: lot’s of FOIA requests (which now I’ve had to deal with…), data scraping, etc. The premise: more data and more transparency, and so better accountability and better governance.
That was 2008. Things started to change a little bit. Then we started to move into this idea of civic engagement, using technology for engagement. I’ll be honest: I haven’t seen too many of these platforms — Change by Us, IdeaScale, or even Google Moderator , etc — succeed; most have failed.
That was step two. Now I think we’re finally moving into this area of digital transformation, of using technology to actually change the way we do service delivery. Taking processes that were before offline and information that was before on paper, online and machine readable.
The interesting thing about that is actually that leads to better data.
Right now it takes 16 months to get official police records from the state — 16 months — because we have to send paper forms to the state, they transcribe them and then send them back. The backlog is mind-numbing.
That’s not the right way to handle data — open or otherwise. Instead, a digital first strategy — eg no paper forms, just iPhones or iPads in the field — would lead to immediately accessible and usable (and hopefully open) data.
That’s trend one, is this movement from data to services.
Trend two is from one app to many apps
A rather perceptive venture capitalist named Mary Meeker pens a must-read every year on internet trends. Recently, she noted that “the web is splintering.” Instead of just having one app to do everything, you in fact have multiple apps.
A good example of this is Foursquare. Beforehand you’d do everything in one app. Now there’s Foursquare and Swarm. Facebook has Messenger as a separate app. Google has like 17 different apps. You’re seeing this shift from just one specific application that does everything to many different applications designed for a particular experience.
That’s trend two: Focus on a single, specific, and meaningful user experience, and build a beautiful interface simply for that.
Trend three is this notion of an architecture participation.
What I like about this idea is that when you create web applications and create user experiences, you build the opportunity to get people to do more. You can up-sell them. We all know this. You see it every day when you go to Amazon or in a grocery store. Either when you’re checking out online or offline, you’re asked to pick up some else: a related book or a little bit of candy or a magazine (that you probably don’t need). They’re up-selling you. They’re asking you to do more.
There’s no reason we couldn’t apply this same strategy to government engagement and services. Indeed it’s already happening. What this requires, though, is thinking less about a specific, sole engagement with an user, but instead about a string of related, though distinct interactions, architected to maximize participation. It’s about erecting architectures of participation.
Bringing it together
- You’re seeing a movement from data to delivery.
- You’re seeing the web start to splinter towards single-purpose apps.
- You’re starting to see levels of engagement increasing through architectures of participation.
Now you’re thinking, “Abhi, weren’t you going to be tell me that we should abandon data portals? Services, splintering apps, architectures…? What gives?”
At the core of all three trends is one basic notion: the web is moving away from building for one-size-fits-all towards designing for to-each-his/her-own — towards user-centric design. And we must do so for open data.
That’s the core notion here: a shift away from building portals towards designing for people, away from unified platforms and more towards user-centric design.
Then what do we do with data?
First and foremost I think you have to go where people are.
If you’ve every been to LA before — or even not — you may know that traffic is a little bit of a problem there. Just a bit. (That’s why I gave up my car.)
The city, as we all know, has information about street closures, public events — all the planned activities that’ll likely gum traffic. Well, beforehand we kept all the data to ourselves. Indeed, all this data was available on our GIS Hub, but sadly most of the city staff didn’t even know that — let alone the regular citizen. Fortunately, we eventually found it…
Now we actually give that directly to Waze, so they can reroute people dynamically. Indeed, this is a good open data story — taking the data to where people are —but there’s something more interesting: it’s a two-way street.
Not only does Waze now share pothole and road condition data it collects regularly through its app, they went one step further. They began to proactively collect and share data in the interest public safety.
Waze is giving the city data in return. Any time there’s a kidnapping or a hit and run, Waze will tell the users, saying, “This just happened. Do you have any intel/info?” Any time that there’s a kidnapping on Wilshire, Waze will actually ping you and say, “Hey, do you know what’s going on? Have you seen anybody? Do you know what’s happening?” Users can, in-app, report sightings directly, and immediately that data is sent to the LAPD. The news reported it as, “A Gift for Law Enforcement.”
Two, I think we have to start thinking about data as content.
Anyone want to guess what the most popular data set for the City of Los Angeles is?
We collected information on accredited immigration workshops, and published it on the data portal; then we embedded that data on the mayor’s website — a website far, far more popular than data.lacity.org.
That’s moving data from the fringes into the center, from a niche site to the homepage. Naturally, there are political and organizational dynamics to work through — the IT or data organization often does not control digital content or strategy. But it’s a fight worth having. If we say as cities that open data matters, then it should matter enough to be featured across the city’s digital presence. Open data ought to merit a few pixels off the portal.
Finally you have to take data offline.
An interesting thing that I learned when I was in LA is that there was a lot of interesting groups doing interesting work, but separately, even though they shared a common goal: using technology to serve the city they all loved. And to do so, using open civic data. But these efforts were too often disconnected. (Indeed, I found myself having the same conversation with different community leaders multiple times a week.)
What we decided to do there was very deeply commit to actually bringing these groups together, having them all start to talk to each other. We launched a program called #TechLA. We’ve had the biggest hackathon, two years in a row. The idea was that actually just by building a brand, just this identity, #TechLA, it actually helped these different groups come together in a way that they couldn’t have done on their own. That’s one of the core responsibilities and opportunities that we have as government officials, is that we actually can build a tent, we can actually have people come together.
And you can then take the data off of the portal, and put it directly into the hands of developers.
Here’s an example from the #TechLA event last year:
They built an app that helped people find homeless shelters, and all the kids were in high school. You’re seeing people do really remarkable and special things.
I’m sure we can talk on and on about hackathons and app competitions and how to make those great. Those aren’t sustainable. You can have one great event. You can have another great event. Then what happens after that? People go home. They go back to their lives. The hard question is, how do you create staying power? How do you get people to come together on and on? How do you create infrastructure that lets people actually do meaningful work in an ongoing way?
We built an organization specifically designed for this purpose in LA. It’s called Compiler.LA, a for-profit that actually works on civic issues, but t_hey commit a percentage of all of their revenue back to the community to build the civic tech ecosystem._ They’ll get contracts from foundations, from cities, and then they use part of that money to then go back and help build the civic tech community. That to me is the kind of staying power that we need to have.
In closing, there’s a great book called Small Pieces, Loosely Joined. It’s about the web, and it’s about how the web is, by David Weinberger, who wrote this phrase, “the web is perfectly broken,” which I think is an interesting phrase, “perfectly broken,” because it’s messy deliberately. It’s not meant to be simple or easy; uniform and centralize. It’s supposed to be hacked together, distributed, customized, and remixed. It’s supposed to be human.
Bringing this all back then to data and open data portals: We too often think about building that one great portal, one great experience, for everyone, but what we learn from the web is that actually we should be listening more than we are building, be understanding user needs and habits more than presuming them, and be going to where they are instead of asking them to come to us.
We should do lots of different, small things — not just build one, big thing — and instead think about crafting the ideal experiences for the wonderfully diverse users you have: be it the mayor, city staff, or even your boss; be it the researcher, the entrepreneur, or the regular citizen; be it the person you hadn’t thought of until you meet them randomly at the library. Be it anyone.
This essay is based on an edited transcript from my keynote address at the 2015 National Association of Government Webmasters 2015 (NAGW); video is below.