<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>Rypple &#187; Pixar</title>
	<atom:link href="http://rypple.com/blog/tag/pixar/feed/" rel="self" type="application/rss+xml" />
	<link>http://rypple.com/blog</link>
	<description>Feedback is fundamental.</description>
	<lastBuildDate>Tue, 07 Sep 2010 14:50:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Ready for the feedback journey?</title>
		<link>http://rypple.com/blog/ready-for-the-feedback-journey/</link>
		<comments>http://rypple.com/blog/ready-for-the-feedback-journey/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 20:23:46 +0000</pubDate>
		<dc:creator>Jesse Goldman</dc:creator>
				<category><![CDATA[Feedback]]></category>
		<category><![CDATA[business development]]></category>
		<category><![CDATA[constructive feedback]]></category>
		<category><![CDATA[continuous feedback]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[feedback is fundamental]]></category>
		<category><![CDATA[ideo]]></category>
		<category><![CDATA[John Foster]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[performance review]]></category>
		<category><![CDATA[Performance Reviews]]></category>
		<category><![CDATA[Pixar]]></category>
		<category><![CDATA[professional development]]></category>
		<category><![CDATA[Rypple]]></category>
		<category><![CDATA[self-improvement]]></category>
		<category><![CDATA[Stanford University]]></category>

		<guid isPermaLink="false">http://rypple.com/?p=3441</guid>
		<description><![CDATA[Last week we hosted the second meeting of the Rypple Learning Collaborative. Spearheaded by John Foster, IDEO’s Head of Talent and Organization, we spent an exciting afternoon at Pixar’s headquarters together with nearly 40 innovators and thought leaders from top organizations and academic institutions, including Mozilla, Facebook, and Stanford University.

One topic that resonated with me [...]]]></description>
			<content:encoded><![CDATA[<p>Last week we hosted the second meeting of the <a title="Rypple Learning Collaborative" href="http://lc.rypple.com/" target="_self">Rypple Learning Collaborative</a>. Spearheaded by <a title="John Foster" href="http://www.ideo.com/thinking/voice/john-foster" target="_self">John Foster</a>, <a title="IDEO" href="http://www.ideo.com/" target="_self">IDEO</a>’s <a href="http://www.ideo.com/thinking/voice/john-foster" target="_self">Head of Talent and Organization</a>, we spent an exciting afternoon at <a title="Pixar" href="http://pixar.com" target="_self">Pixar’s</a> headquarters together with nearly 40 innovators and thought leaders from top organizations and academic institutions, including <a title="Mozilla" href="http://www.mozilla.org/" target="_self">Mozilla</a>, <a title="Facebook" href="http://www.facebook.com/index.php?lh=b8d53daede0960e3f2b6d6684cacbba9&amp;" target="_self">Facebook</a>, and <a title="Stanford University" href="http://www.stanford.edu/" target="_self">Stanford University</a>.</p>
<div id="attachment_3451" class="wp-caption aligncenter" style="width: 510px"><a href="http://rypple.com/wp-content/uploads/2009/11/guys_at_pixar1.png"><img class="size-full wp-image-3451" title="guys_at_pixar1" src="http://rypple.com/wp-content/uploads/2009/11/guys_at_pixar1.png" alt="guys_at_pixar1" width="500" height="375" /></a><p class="wp-caption-text">From left to right: Jesse Goldman, Daniel Debow, Sully, David Stein, David Priemer, Mike, Jay Goldman</p></div>
<p style="text-align: center;">
<p>One topic that resonated with me was the idea that feedback is a journey, not a specific event. The feedback we ask for, and get, will evolve as we develop and as our priorities change.</p>
<p><strong>My insight: people are more effective in reaching their objectives when they get ongoing feedback based on their work and goals.</strong></p>
<p>Why? Because when feedback is part of our day-to-day lives, we get used to receiving it. This puts us in a better position to act on the feedback because we become less distracted by its implications.</p>
<p>Most of us are constantly on the look-out for indicators to let us know how we’re doing at work. If we’re not used to regularly getting feedback from our peers, bosses, etc., we’re more likely to think to deeply about the meaning of each piece of feedback we get. We end up spending more time interpreting the input, discussing with our friends, etc., than we do actually acting on it and using it to get better and help drive results.</p>
<p><strong>Infrequent feedback is a big distraction</strong>. Consider the annual performance review, for example. Why is it so stressful for so many of us? Because annual appraisals force us to squeeze as much information as we can remember into a single event each year. Due to its infrequency, the appraisal event becomes the indicator of our value to the company. That’s challenging to take in all at once, and particularly unpleasant if we disagree with the assessment. We’ve got to break this habit – we’ll all be better, and happier, if we do.</p>
<p>Fostering a journey of continuous feedback requires an understanding that each piece of feedback received is not in itself the sole reflection of how good or bad you are. That’s a big step for most (myself included), but we need to do our best to keep this rule in mind: creating a habit of regular feedback will make us more receptive to feedback. This is how to start a journey that will be more fruitful for you, your team, and your organization.</p>
]]></content:encoded>
			<wfw:commentRss>http://rypple.com/blog/ready-for-the-feedback-journey/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ready for some feedback?</title>
		<link>http://rypple.com/blog/rypple-ideo-learning-collaborative-kickoff/</link>
		<comments>http://rypple.com/blog/rypple-ideo-learning-collaborative-kickoff/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 14:40:12 +0000</pubDate>
		<dc:creator>John Foster</dc:creator>
				<category><![CDATA[Rypple]]></category>
		<category><![CDATA[The Learning Collaborative]]></category>
		<category><![CDATA[Electronic Arts]]></category>
		<category><![CDATA[Experiments]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[Feedback]]></category>
		<category><![CDATA[ideo]]></category>
		<category><![CDATA[Kiva]]></category>
		<category><![CDATA[Learning Collaborative]]></category>
		<category><![CDATA[Littler Mendelson]]></category>
		<category><![CDATA[Method Home]]></category>
		<category><![CDATA[organizational development]]></category>
		<category><![CDATA[Pixar]]></category>
		<category><![CDATA[stanford]]></category>
		<category><![CDATA[The Federal Reserve Bank]]></category>

		<guid isPermaLink="false">http://rypple.com/?p=2188</guid>
		<description><![CDATA[In August, we held the first session of the Rypple Learning Collaborative at Mozilla’s new HQ in Mountain View.  In addition to Mozilla, we had participants from Method Home, Pixar, The Federal Reserve Bank, Kiva, Littler Mendelson, Electronic Arts, the Stanford d.School, Facebook, and IDEO.
We hope this collaborative learning effort generates some new insights and [...]]]></description>
			<content:encoded><![CDATA[<p>In August, we held the first session of the Rypple Learning Collaborative at Mozilla’s new HQ in Mountain View.  In addition to Mozilla, we had participants from Method Home, Pixar, The Federal Reserve Bank, Kiva, Littler Mendelson, Electronic Arts, the Stanford d.School, Facebook, and IDEO.</p>
<p>We hope this collaborative learning effort generates some new insights and ideas that help people do a better job asking for and giving feedback.  So, we spent much of our first time together  sharing our direct experiences with people giving and receiving feedback and generating a list of observations about what seems to work and what doesn&#8217;t.</p>
<p>We framed our discussions with the idea that feedback involves not only the person asking/receiving and the person giving/providing, but a &#8220;crowd&#8221; of people around that pair.  Traditionally, much of the attention given to this topic is on the mechanics of the interaction between the two obvious players.  We included the third role to push our assumptions with a social systems view.</p>
<div id="attachment_2189" class="wp-caption aligncenter" style="width: 438px"><img class="size-full wp-image-2189" title="Feedback System" src="http://rypple.com/wp-content/uploads/2009/09/Feedback-System.jpg" alt="Feedback involves 3 roles, not just 2" width="428" height="409" /><p class="wp-caption-text">Feedback involves 3 roles, not just 2</p></div>
<p>We all shared stories describing real feedback situations to help us recognize some patterns in real behavior.  Once we get a good picture of how people actually behave (not how they should behave), we will try to uncover what works well and what causes people problems.</p>
<p>An early insight from our shared stories is that it makes a positive impact on a feedback exchange when a person is ready for it.  That is, when a person is asking for feedback, they seem to be more able to handle it well than when a person gives it.  So this prompts the question, &#8220;What makes someone ready for feedback?&#8221;</p>
<p>Our next step is for LC members to begin conducting feedback experiments within their organizations.  From these experiments, we will expand our observations and gather more ideas to push our thinking.   We&#8217;ll start posting them in a few weeks.</p>
]]></content:encoded>
			<wfw:commentRss>http://rypple.com/blog/rypple-ideo-learning-collaborative-kickoff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
