"Why should every city government treat the same issues as unique barriers? If one has pushed through a solution, why would we try to face the issue as a barrier? If we change our mode of thinking we are now viewing this issue simply as a process to follow. I’m not trying to simplify complex scenarios nor to undervalue thoughtful planning, but I don’t see how we can view the same problems as unique, over and over again. Take the hard work others have done before us, leverage it for our city and residents benefit, and do the same with out struggles and wins- publish our process successes and our common software solutions and share in the efficiencies and collaborations that can strengthen our governments and improve their operation.
To wit, this is exactly how I’m approaching our efforts to implement opendata in both the City of Oakland and the County of Alameda. San Francisco, New York and Chicago have done the hard work blazing a trail, now we have a great process to follow so we don’t have to do the same hard work as they did.
* Identify problem
* Search for existing solution
* Plug and play.
And I think that the more we talk about the processes and struggles to change, the more we all gain."
—
Steve Spiker: Barriers or Processes?
Steve Spiker writes a great post about the potential to open-source our processes, not just our code. Hear hear.