It’s time for open data on open data
Recent conversations I’ve had with municipal executives managing open data programs indicate that traction around open data platform usage isn’t meeting their personal expectations.
The looming fear for some is that, as more and more resources are allocated for open data initiatives, there is going be more of a need to justify the return on investment. If these efforts aren’t meeting that return, the best case scenario is that they’ll receive less funding or simply stagnate as a priority, especially when there are more immediate, pressing IT issues senior-level executives face.
In some cases, some are already asking how to frame the justification.
Two questions to ask if your platform isn’t getting the usage traction you expect:
- Is it the data platform’s user interface/experience and general product design?
- Are you effectively developing holistic open data communications strategies to communicate the availability?
The first question is the most important, because without an analytical understanding of usage, the answer to the second is moot.
The appropriate, “open” solution is for governments is to start publicly releasing analytics data on their open data platforms. Given that “open by default” is ingrained in the culture of the open data community, this should be a no-brainer and easy goal to accomplish.
If the numbers are dismal, we can look for the reasons why together and address this as a community.
Let’s start sharing open data platform analytics.
Let’s get this right together.
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.