About 10 years ago, NASA Ames was heavily invested in things like IBM and Sun enterprise software solutions for its web stac.Advocating for open source software using the “its free” tactic“Free” is a myth. It’s not freeThe true value of open source software is in the communities
In evaluating, an open source solution: The question was always “OK, hows the community? It is sustaianable? Vibrant? Do they welcome newbies or it full of trolls?Have they produced a vast amount of resources?Do they continue to produce product? Whats the mechanism for contributing code? Is there a release schedule?
Open source communities exist within in software development to provide innovative, high quality software productsIsn’t that exactly what we want from our organizations? Innovative, high quality products and servicehttp://www.flickr.com/photos/mojodenbowsphotostudio/2408750389/
Fast Forward to today. Gov 2.0 has tons of momentum…If for no other reason, because the white house issued an open gov directive on his first day of office and lent support to the concepts and usage of things like social media (after all, it helped get him elected)Executive management support has never been higher. Understand that technology is an enabler of something different, but not exactly sure what that is.And whatever it is, are probably pretty hopeless when it comes to knowing how to get it done
Almost all org charts can be simplified like this.Sr. management is on board, but not quite sure how to proceed with social media (and gov 2.0 and opengov)Have tons of support at the groundswell lower levels of an organization. (where people are younger)Who are gen y digital nativesWho are increasingly impatientBut in the middle. It’s a mess. It usually is quite honestly. Major culture changes needed in the middle. Some disruption needs to happen.
So how can what we know about succuessful open source communities disrupt the middle?What are the attributes of an open source community that we can adopt within our offices and internal networks?Although we’re not necessarily trying to create a software product. In fact, some of us aren’t in IT organizations at allBut open source community practices can facilitate change regardless of whether you are part of an organizations whose output is a product, service, or just knowledge and information in general.
This will scare the hell out of many management typesBut give up to gain more…leads to innovation
Use of I.T. solutions. Wikis, etc.Keep lots and lots of records. Use tags to bind it all togetherSeek out the trends
There are avenues or mechanisms that allow anyone to initiate thought, provide feedback, or share opinionsIt doesn’t matter what silo you’re in. or what your skill set is. Your perspective is important. This participation moves from backroom old boys club networks and meeting rooms and out into the open where it is completely visible and available to allIdeally people will participate in things that they have the greatest expertise or stake inWhat exactly are we hiding from each other? Is it really just an issue of mechanisms to enable that opennessnot any more, not with today’s tools
No more backroom dealings. Kill the old boys networkDecision making process is informed and done in the open where all can see
By holding conversations and decision making in the open, everyone acts like an adult
All documents materials should be available for anyone to review or make use of. Centralized information repositories facilate this
If the raw materials are available, you should be able to do something with it.Most organizations aren’t against this, they just don’t do it very efficiently
This is the most controversial oneAnil dash wrote a recent post…“see it, make your own version, and then get to work”“moving away from the need for a forced consensus can be great for innovation, while also reducing social tensions. “
“moving away from the need for a forced consensus can be great for innovation, while also reducing social tensions.
Often you need to build the community first around a concept or disciplineUse basic community building practices. Events. Guest speakers. “Salons” . Free pizza. Or better yet free beer. Bring them together. Out of their foxholes. Then activate them to do something. Its almost like you’re creating an organization sleeper cell. (this is what im doing)
How To Use Open Source Techniques For Your Project Management Needs: Achieving Organizational Culture Change And Breaking Down Barriers Through Social Media Participation
How To Use Open Source Techniques For Your Project Management Needs: <br />Achieving Organizational Culture Change And Breaking Down Barriers Through Social Media Participation<br />J.J. Toothman<br />Web Strategist<br />NASA Ames Research Center<br />1<br />
email@example.com<br />http://nasawebdude.com | http://gov20.tumblr.com<br />Twitter: @jjtoothman<br />Dell Federal Government Services<br />NASA Ames Research Center (2001-2007; 2010 – present)<br />2<br />