Open Sourced Bright Ideas and Micro Support

EyeBeam CFL CoverVia Emily Gertz’s tweet of a recent blog post of hers, I was led to Bright Idea Shade on mandiberg.com.

From Eyebeam OpenLab comes and open source idea for making a cover for those glare-y compact fluorescent lightbulbs (CFLs) we are all installing to save energy. But the bare bulbs are, well, unbearable. I’ll embed the video below, because it is wonderful, but I want to add some additional observations about process and values here. The light bulb information is practical and usable, but what is going on with EyeBeam OpenLabs work is what I’m focused on.

What is going on here?

  1. A problem or need is identified
  2. A solution is created (in this case, building upon a previous product)
  3. The idea is opened up an shared and…
  4. an invitation is made to offer that idea to a manufacturer to reproduce it! (Eyebeam apparently also plans to produce a DIY kit but that is not yet on their site.)

The question that then surface include:

  1. What is in this for Eyebeam? (Beyond possible sales of a DIY kit which any other manufacturer could also create) What values are being expressed – beyond valuing open source. That part is already clear. Eyebeam’s “about” page gives a 404 error, so it is hard to fully discern by just looking at their web site. It looks like a non profit organization. So I’ll make some guesses that this organization is about the application of design in support of some greater good. Thus they find willing funders to fund their work and they “give away” their ideas as the result of that work. The additional benefit is the support of the designers and artists in doing their work and advancing their own practice. Hopefully the open source values continue past their participation in Eyebeam work. As a result, Eyebeam builds a good reputation and attracts more funding. So doing good does good for the existence of the organization. Does this apply only to non profits? As a small business person, I’d say no, it applies more widely. But is it practiced? Have businesses seen the strategic value of a triple bottom line that includes public good?
  2. What motivates people to solve problems and give away the answers? Is there a certain set of characteristics that motivate people to do this? My personal guess is yes – thinks like a perspective of abundance (as in good ideas) rather than scarcity, belief in the existence of many possibilities, and some sense of optimism. But I think it is bigger than that. What else?
  3. Why aren’t more people doing this? Or are they, and it is just invisible? (And if it is too invisible, what might we do to make it visible?) What can we be doing as individuals, groups, organizations and networks to amplify the positive effects of acts like Eyebeam’s which offer solutions to us? Can we encourage this beyond a lightbulb cover to things like improving girl’s education in an African nation, or improved health practices in Palestine?

OK, so bear with me. Here is the next leap in my thinking today. Is there a link between the work of organizations like EyeBeam and the idea of micro-lending. Kiva.org has opened a window of possibility on how an ordinary person in the US can support an individual entrepreneur in a country half way around the world who would otherwise not be able to start or continue their small business which supports their family. Tune Your World is trying to support musicians in countries without the economies to support their work by getting support from people like me who can support them.

Can we micro-finance and encourage ideas that solve all sorts of problems? Is there a non-financial element of micro-support? What would it look like? Is that kind of support useful or destructive? (maybe both!)

What do you think? What do you know of going on like this that might help us explore these ideas? I ask, because I know from my experience that top down, large organization-driven solutions are not going to work for all the needs in the world. We need to identify, understand and expand other options and approaches. I want to learn more.

Now, the video, in case you have a bare CFL that is glaring you down:

CFL Cover from Eyebeam OpenLab

Production by Simon Jolly

Soundtrack by I Am Jen (iamjen.com)
SteveTouch(TM) by Steve Lambert
Project by Michael Mandiberg and the Eyebeam OpenLab
http://www.eyebeam.org/project/cfl

Flickr Photo credit:

Now, I also have a problem I just discovered. and I’m looking for some bright ideas. I got home from a three week trip to find large-ish animal doo doo in my basement and now I don’t even want to go down there to find out what left the doo doo, how it got in and how to make sure it (they) are out. Anyone in Seattle wanna come help me? Signed – chicken Nancy

Talking and Walking Collaboration

Big A Moleskine Exchange, Big A's book, part 1
Creative Commons License photo credit: steev-o
A bit ago Shawn Callahan of Anecdote (friend and collaborator!) wrote an interesting blog post about people who write about collaboration – by themselves. Anecdote: What do you notice about these recent books on collaboration?. This triggered some reflections in the comments about the process of writing collaboratively.

Recently, more of my writing has been collaborative than solo (as evidenced by my paucity of blog posts!) I have written 3 articles collaboratively (more on those later, one of which was with Shawn and his biz partner Mark Schenk), one in the works and have been co-writing workshop documentation with our team. And of course…. THE BOOK.

As I responded to Shawn’s post, I realize that in reflecting on the collaborative writing process of the book, there is a point where it is impossible to separate the talking about collaboration with the walking the collaboration talk for me. That is because collaboration requires reflection, which is a sort of “talk,” no?

Here is what I wrote on Shawn’s blog:

As I’m just on the (hopefully) finishing edge of very collaboratively co-writing a book with John Smith and Etienne Wenger, I feel fully able to comment on the experience.

First, it takes a lot more work to write WITH others. And I’m not talking about pasting chapters together, each written by an individual. Truly co-writing and co-editing is both an amazing act of commitment to each other, learning and love.

The first year, when we thought it was “just an update to a report” collaboration was difficult for me. I did not know how to negotiate meaning. I was impatient. I alternately felt guilty or impatient with my collaborators. I was a lousy co-writer.

In the second year (yes, second year) we learned to listen to each other. We dealt with things we did not speak about in year one, like being heard, or feeling less for some reason or another. I learned to understand my strengths and weaknesses as a writer and a thinker, and to appreciate the strengths and weaknesses of my cowriters.

In the third year (yes, the THIRD year) I was enlivened by the learning. I was applying what we were writing/making sense of so there was an electricity. But slow electricity.

The fourth year (this year) IMPATIENCE to finish. Tired. Worried that our slow place was great for our learning and personal application in our practices, but too slow for usefulness in the world. I became impatient with the finishing process. Yet I’m so glad we revised and revised. It got better.

Am I happy with the final book? Well, I’ll confess, I have to wait until the world tells us if they find it useful. But I’m 100% happy we took the time, the practice, and the patience to write together. I’d equate this with a PhD course of study. It is irreplaceable.

And it is ENTIRELY DIFFERENT than writing on my own.

How do you reflect on your collaborative experiences so that you can do it even better the next time? Do you reflect alone? With your collaborators?

Seeking to work without pretension

From my friend Philip…

Thus when we used to make our constructions, we produced “pure truth” without pretensions, without tricks, without malice. What we did then had never been done before; we did it disinterestedly, and if is worth anything it is because we did it without expecting to profit from it. We sought to express reality with materials we did not know how to handle and which we prized precisely because we know that their help was not indispensable to use, that they were neither the best nor the most adequate. We put enthusiasm into the work, and, this alone, even if that were all that there were in it, would be enough: and much more than is usually put into an effort — for we surrendered ourselves to it completely, body and soul. We departed so far from the modes of expression then known and appreciated that we felt save from any suspicion of mercenary aims.

Pablo Picasso, reported by Jaime Sabartes in, Picasso: An Intimate Portrait, New York 1948

Good food for thought, especially when working hard and fast…

Aristotle helps me distill this visual thinking stuff…

The soul never thinks without a picture.

Aristotle

Aristotle (384-322 BCE): General Introduction [Internet Encyclopedia of Philosophy]

What I missed at Northern Voice

The challenge of parallel sessions is you have to miss something, particularly if you are playing a lead role in your own session. Makes it hard to skip out. There were two sesssions I really wish I had not missed. One was Dave Olson‘s F*ck Stats, Make Art Dossier.

Apparently, Dave was on the same stream as our “Writing on Walls” session – tapping into our creativity. I’m glad the session was recorded and blogged. It was interesting to see that there were quite a few sessions that pinged on a central core of creativity.

I also missed Alan “cogdog” Levine’s preso on 50 Ways to Tell a Story. I’ve been following the evolution of this presentation since last summer and was looking forward to the “live” version, but I was deep in a conversation with Dave Pollard and one does not drop the chance for a great conversation. So Alan, know I was beaming you and I’ll look for Injenuity’s video.  (And I’m glad, Alan, you caught Scott Leslie’sTrackback Love“. Geek poetry!)

(Photo by Robert Scales )