January 26, 2012 at 4:37 pm #150992
In preparation for my next blog post it would be great to hear some of the biggest challenges with adopting Gov 2.0 technologies (Open311, Open Innovation, etc.) tools within government. What are your experiences?
January 26, 2012 at 5:05 pm #151004
This might be a bit shocking, but having been involved in change initiatives, both as a leader and observer, the BIGGEST challenge is that those involved in leading and implementing the changes (trying to get buyin) don’t LISTEN.
If you don’t listen to the people who need to buy-in, and I mean really listen, rather than complain, “they don’t get it”, you’ll probably do more damage than good.
January 26, 2012 at 5:29 pm #151002
Robert, great point! From my own experience, I’ve seen time and time again that listening is one of the most important skills to have with getting buy-in.
January 26, 2012 at 6:48 pm #151000
Procurement rules – It’s hard to use opensource/civic developer tools if the legal roadblocks are put up
January 26, 2012 at 6:51 pm #150998
My response could be voluminous, but I’ll keep it brief and just shed light on the idea. I have been a big proponent that Gov 2.0 and its fraternal twin, Open Government needed a happy medium between data and dialog to be successful. Unfortunately, data has received the most attention and the biggest challenge of the two, dialog, has lessened its importance in this discussion. Data is static. It’s easier to tackle. Dialog is dynamic. And there is a history of challenges surrounding dialog that precedes the web.
So you stated it appropriately: “technologies.” The main challenge will be government’s ability and effectiveness to provide the required data for those third party facilitators of the public dialog that will return informed verdicts to the policy makers on how to vote on public issues.
January 26, 2012 at 8:18 pm #150996
My experience – it has to clearly solve a problem where the pain is there.
We could have a debate on definition of Gov 2.0 but I think the most successful ones have that:
-Open source CMS (Drupal/wordpress) – all agencies need a CMS. Most don’t like their current one and have looked to change them. So change there
-SaaS email (often Google or Microsoft) – all agencies have email for their staff. Most don’t like their current one as the storage is low and takes a lot of resources. Plus people often have better experiences in personal email accounts. So you’ve seen a lot of adoption of Microsoft cloud email and Google apps for gov
The ones where it is simply nice to have (we should collaborate more internal for example), I think is just a harder change as no impetus to move tomorrow.
January 27, 2012 at 6:32 pm #150994
You must be logged in to reply to this topic.