Wednesday, October 6, 2010

Failure and collaboration

      Here is a link to a video I watched this week. Pixar's Randy Nelson
     Since I was sent this video, I have watched it several times, getting a new piece of information each time.
Nelson's speech discusses many of the concepts we value as a system and a school.  One of the key components in our framework is protection from adverse consequences from initial failures.  This protection is important for both our students and our co-workers.  As we have discussed before, without the understanding that failures should be seen as learning opportunities, people will never venture outside their comfort zone.  Innovation can never occur where failure is feared. 
      Another idea that was meaningful to me was his idea of collaboration.  As we continue to focus on student work and begin to look at using protocols to discuss the work we design, this idea should be in the back of our minds.  When we work together, are we dividing up the work tasks to speed up our completion, or do we work together to make the finished product better?  Cooperation is not bad.  The assembly line revolutionized industry, and there are many times that dividing and conquering is necessary to do. However, that should not be the final goal when working together.  Innovation (often through collaboration) must always occur before the routine cooperation occurs.
      Is there anything else that stood out in the article?  What methods should we implement to ensure that students (and adults) feel comfortable venturing outside of their comfort zone?  If collaboration is meaningful, how do we guarantee that there is time for it to occur?  

2 comments:

  1. Additional things that stood out to me when I watched the clip were numerous:
    1) Accept every offer-Often times, in a "collaborative setting" things can turn interrogative and this is what takes a situation and turns it from collaboration to defense, explaination or "light battle," if you will. Time is probably the main reason that things go arwy. The listener(s) in a said situation can be in a hurry and wanting to cut to the chase, or, even less recognized, a presenter becomes "let down" if their "idea" is tinkered with. Both time and the lack of a collaborative culture can lend to "accepting every offer" as a more difficult feat than it should be. I really liked "accept every offer". It reminded me of the first time you get an "atta boy" on something. That first time someone accepts something you've done and works with you to enhance it can be a great beginning to confidence, not only in yourself, but in the power of "two heads are better than one". Of course, without collaboration, two heads can butt and become dangerous. :) "Make your partner look good" was an awesome concept. What if that was a norm? I can think of a great scenerio to illustrate this that would be metaphoric, but powerful.

    2) Resumes-Resumes don't show innovation, you have to be "deep" in something to be innovative. This reminds me of how cool it is to "see big picture," but be able to fine tune the picture so that others can see the big picture, too. Seeing the big picture when it's fuzzy is kind of like having vision and fine tuning it can come from innovation. The NASA example was great because you really need someone who can recover from failures in that field.

    3) No judging-I like the "How do I plus this?" mentality.

    4) Resumes-Proof vs. Promise--wow--loved that point, too.

    5) Getting out of Comfort Zone: Be interested in your colleagues. Solicit their ideas. Hold forth the promise that you can help others succeed.

    Methods to Implement Innovation-Have a protocol that lends itself to a culture of "How can I plus this?", being interested and offering promise.

    Great clip. Thought provoking. Pardon editing needs--

    ReplyDelete
  2. You are exactly right about how difficult it is to accept suggestions. I have seen many people become defensive when having their work examined, even when the best protocols are used. It requires trust and the belief that quality work is the end goal, not getting credit for a great lesson.

    ReplyDelete