Open Source thinking and design

By Andy Scheurer
March 8, 2009

This was an inspirational weekend for me.

I stumbled upon www.ted.com and started watching some videos. In fact, I couldn't stop watching - it was addictive. The number and variety of innovative people who are doing things for humanity was astounding to me, and it also showed me that open source thinking is prevalent not just for software, but for nearly everything that impacts us today.

Open source architecture was presented by Cameron Sinclair, founder of Architecture for Humanity. In his 2006 talk, when he accepted the TED Wish, he shows examples of this open source concept and tells the story of how it has created and will create solutions. He then presents the Open Architecture Network, a hub for designers of all sorts, from all nations, beliefs, schools, and specialties to collaborate on global design opportunities and challenges.

First was Jose Antonio Abreu talking about "El Sistema" and the Venezuelan youth orchestras that he has had a hand in creating. Then there's Dave Eggers talking about an approach to tutoring and education that works, as can be seen from his 826 Velencia (and other) projects. Both gentlemen have inspired me to approach this week (at school) with vigor and a dedication to trying to get the old ways of K-12 public education in America to budge. Their work has helped kids be successful and has brought about cohesion, involvement, and excitement in their communities. I can hope and also act to make sure it does the same in mine.

The most important part for me is that both are open source ideas. They bring together volunteers who have diverse talents and passions, and their work creates outstanding results. They rely on each other for expertise and ideas, and the sum is a meaningful and effective solution.

Those and other videos, from Al Gore to Tony Robbins who were also inspirational, have convinced me of two concepts.

1. Open source thinking is going to save the world.

In fact, I am starting to believe that if businesses, schools, and organizations don't start adopting open source principles their growth will slow down and, ultimately, they will cease to exist. Well, at least as viable institutions (see GM, Ford, and Chrysler). Users will start to see that they can create their own product, and those around them will collaborate, improve, and share it.

2. Of all the challenges and opportunities that we have in this world, more than ever (and perhaps it was this way "before") design will be the solution.

I've never really appreciated the value of good design until I started to see how many problems are solved, or could be solved, just by creative, innovative, and solid fundamental design. Companies like Ideo are consulting on good design and solving problems in a number of industries and have also stretched the boundaries of just physical design and have consulted with the Kellogg Foundation to create designs for effective schools. Sinclair's foundation, as well as the Open Architecture Network, focus on design to solve problems.

Previously, I had never really thought about what design meant. I guess if you asked me to define it, just a few weeks ago, I would have said architecture and material engineering. To designers and innovative companies, however, it means something much greater. It means the high-level plan for not only physical objects, but knowing or anticipating how they will be perceived and used in a particular setting. No one person can know or anticipate all of this. Instead, it must come from people with difference experiences and backgrounds that can collaborate.

You might think that most businesses and educational institutions function this way anyway; however, I disagree. Business and managers (and schools and their administrators) are too busy trying to meet benchmarks, complete tasks, and finish out the day with a profit (or with passing standardized test scores). They don't pause to design solutions and collaborate on those designs. Often just one project manager will assess risks, create goals, and distribute tasks. A meeting may occur, but is collaboration happening? More importantly, are those meetings producing designs that solve problems?

In an open-source culture, these collaborate meetings happen naturally because people understand that they are the sum of their parts. They are not managers or distributors. They aren't trying to check tasks off the list and just meet a benchmark. They are designing solutions.