Weekly Roundup: October 16-20, 2017

John Kamensky

Creating a Problem-Solving Network (Part II)

There have been a series of studies providing lessons on how to effectively create a collaborative community. For example, having a catalyst (like Lucas) and have a convening place to share (like the OpenGovPlaybook wiki), are great starting points. Russ Linden, an author who is an astute observer of collaborative approaches, recently wrote about the importance of a collaborative mindset. And being passionate and motivated matter too, as this Dan Pink video playfully demonstrates:

Creating a Problem-Solving Network (Part I)

The Obama Administration says it wants to create “problem solving networks” across the government. Well, yesterday a group of like-minded people from across the government convened to discuss creating just such a network around the implementation of agencies’ Open Government Plans.
 
While there is a formal cross-agency Open Government Working Group, many people at the staff level seem to feel excluded and see a need to develop their own network. Many say their agency’s Open

Amending GPRA to Track Performance

Legislation proposed by Cong.

A City App I’d Pay For (But May Not Have to)

Like many other gov/tech enthusiasts, I’ve found this cartoon deeply relevant:

Crowdsourcing the BP Oil Spill

The Gulf BP oil spill in the Gulf of Mexico has spawned more than oil. There are all sorts of efforts to track what is going on, from the Coast Guard, to NASA, to the Weather Service.  These efforts are from the beaches to the skies to under the ocean.
 
 

GSA's FedSpace Collaboration Platform

The President’s budget for fiscal year 2011 promises two interesting steps toward cross-government collaboration.

Defense Contract Reform: Recommendations

 As noted in yesterday’s blog on Defense contracting reform, The House Armed Services panel on Defense acquisition reform offered a series of recommendations in five areas in

Pages