Search form

Main menu

Nick Grossman is a technologist & entrepreneur focused on the intersection of the web and urban, social, and civic systems. For the past 10 years, he has developed software and media products, advocacy efforts and internet-based businesses that help cities and the internet work better together.

He is currently the “Activist in Residence” at Union Square Ventures, where he works on public policy and regulatory issues facing “peer networks” on the web, and leads advocacy initiatives that support web-based innovation.

Previously, Nick led an incubator for technology & media initiatives at OpenPlans -- producing advocacy media properties focused on urban policy, building web applications to spark engagement in local civic issues, and building open source and open data businesses serving the public sector. He is also an advisor to Code for America.

My favorite story from this era is the story of how transit agencies came to adopt open data. Now, in 2013, it seems obvious that transit agencies would publish schedule, route, and real-time data in a machine-readable format for developers to build apps with. But back in 2008 & 2009, it was actually a huge struggle. There were two prevailing forces: 1) agencies not wanting to publish data at all, and going after developers who were scraping / using it anyway and 2) very slow-moving internal discussions around the development of an industry-led standard.

Those two forces were enough to basically keep the open transit data movement grounded. A little known fact outside the civic data world is that what made open transit data work was an outside force: Google. When Google Transit launched in 2005, they worked with Portland’s TriMet to design a new, lightweight, web-friendly open transit data spec: GTFS. That data was not only available to Google Transit, but also to anyone else who wanted to build with it.

Over time, more and more agencies began publishing their data in GTFS, drawn by the traffic that Google Transit saw. In effect, Google had created a “data magnet” — powered by their audience and by a lightweight web standard:

This was a tough lesson to learn but eventually more and more agencies got it: it was more powerful to have their data in Google’s app than to have visitors to their website. Or, as Steven Van Roekel, then US CIO and former FCC managing director said in 2011: “In a perfect world, no one should have to visit the FCC website.”

The big idea in all of this is that through open data and standards & api-based interoperability, it’s possible not just to build more “civic apps”, but to make all apps more civic:

So in a perfect world, I’d not only be able to get my transit information from anywhere (say, Citymapper), I’d be able to read restaurant inspection data from anywhere (say, Foursquare), be able to submit a 311 request from anywhere (say, Twitter), etc.

These examples only scratch the surface of how apps can “become more civic” (i.e., integrate with government / civic information & services). And that’s only really describing one direction: apps tapping into government information and services.

Another, even more powerful direction is the reverse: helping government tap into the people-power in web networks. In fact, I heard an amazing stat earlier this year: