One of the realities of being a Chief Data Officer is that your day is often filled with meetings where you are the least popular person in the room.
Working with government agencies to release data – particularly if agencies are new to the open data process, or if the data in question has not been released before – can be challenging. Releasing open data can invite scrutiny of agency operations from the public and the media. Agencies may view releasing open data as falling outside of their core mission, particularly if their plate is already full and there is little or no funding to support the work that needs to be done to make data available.
Working with agencies to release data can be a lonely job.
Some people are taking a rather pessimistic view – or at least a “glass half full” view – of a recent study from the Pew Research Center.
A new study from Pew – entitled “American’s Views on Open Government Data” – looks at the general public’s perception of open data efforts at all levels of government. The highlighted findings suggest a somewhat muted enthusiasm among the general public on the benefits of open data programs:
Americans have mixed hopes about government data initiatives. People see the potential in these initiatives as a force to improve government accountability. However, the jury is still out for many Americans as to whether government data initiatives will improve government performance.
It’s an interesting study, well worth a full read. And for advocates of civic hacking and engaging with groups outside of government to use open data, I think there is some good news tucked away in the body of the full report.
A new focus on the user
These days, in the world of civic technology, it’s all about the user.
Digital government service redesign, with an enhanced focus on a higher quality user experience, is being institutionalized in the federal governments of the U.K., U.S and Australia. The civic technology community is rallying around a new focus on building solutions that are needs-responsive and community-driven.
“Build with, not for” became the unofficial theme of last year’s Code for America Summit, and the upcoming Personal Democracy Forum in New York will feature a similar theme with talks and panels focused on broader engagement and inclusiveness in the development of civic technology.
Organizations like Code for America have long been focusing on redesigning government service interfaces, but this idea now seems to have permeated every corner of the civic technology movement. This wider embrace of the need to enhance the user experience with government is coupled with a recognition that civic tech solutions are most effective when developed with the full participation of those that they are meant to benefit from them.
Well, not really – But I do dislike certain things about most open data portals. Even the ones that I work with every day or that I have been involved with in the past.
Don’t get me wrong – I’m a true believer in the power of open data. I love that every day there are more and more governments posting open data to specialized sites meant to make their data available to external (and, increasingly, internal) users. But there are things about the way that most open data portals are structured and used that bother me – I think we can do better. And I think a lot of people will agree with me.
Uber is not generally characterized as “civic technology” company. But the recent announcement their request API seems like a real game changer to me.
Today, the Uber API team is excited to announce the public release of our Request endpoint. With the Uber API’s initial launch last August, we made it easy to surface information about Uber products within third party applications, but getting a ride always required deep-linking to the Uber app. With the Request endpoint, you can now build applications that incorporate the entire Uber experience.
There are a number of very practical applications that can be built on the Uber platform which have a clear civic value that are now within easy reach of developers.
Its not often that I run across posts about enterprise architecture that get me excited. This one – by Tariq Rashid – did. Very much so.
This issue interests me because its one that, as a former state IT executive and policy advisor, I have personal history with. I also believe its an issue that will have great impact on how successful governments are at redesigning services around users, and embracing civic technology and open data.
If you want to learn more about how design thinking is changing the way that digital public services are being built, you’d be wise to check out the latest issue of Civic Quarterly. It’s full of great insights from some of the best thinkers on this topic.
The idea of building civic technology “with, not for” was a prominent and consistent theme at last year’s Code for America Summit. I think this is a natural evolution in the way we build civic applications and how we can make them more effective. As groundbreaking and revelatory as the first generation of civic apps was, we now have insight into how we can build better, more inclusive civic tech solutions. This is exciting to see.
But as our thinking on civic technology evolves and as we develop new ways to collaborate with governments to build civic tech solutions, it is more important than ever that we pay attention to the fundamentals.
When it comes to deriving useful results about the operation of government from open data sets, we have an enormous array of tools at our disposal that we can make use of. Often, we do not need sophisticated or expensive tools to produce useful results.
In this post, I want to use command line tools that are available on most laptops, and others that can be downloaded for free, to derive meaningful insights from a real government open data set. The following examples will leverage *nix-based tools like
sed as well as open source tools that can be invoked from the command line like
The data used in this post is from the NY State Open Data Portal for traffic tickets issued in New York State from 2008 – 2012.
The recent crash of a quadcopter drone on the grounds of the White House has drawn attention to the absence of final rules from the FAA governing unmanned aircraft – rules that have now been in the works for years.
This one incident almost perfectly encapsulates the difficulty that governments have with keeping pace with changes in technology. Technology can change in a matter of months or even weeks, quickly making it easy and affordable for almost anyone to buy a drone. The process that the government uses to adopt new rules and regulations, that can govern how these newly affordable drones may be used, can take years to become final.
Interesting story in the Washington Post describing a survey of federal government technology managers.
The big takeaway from this survey seems to be that the majority of IT managers are enthusiastic about new technology and can see how it helps them do their jobs more effectively, but they question the government’s ability to keep pace with the private sector.