<!--
/* Font Definitions */
@font-face
@font-face
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
span.GramE
@page Section1
div.Section1
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
</style>
<Unable to render embedded object: File ([endif]--><) not found.--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050"/>
</xml><Unable to render embedded object: File ([endif]--><) not found.--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1"/>
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US style='tab-interval:.5in'>
<div class=Section1>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><a
name="OLE_LINK4"></a><a name="OLE_LINK3"><span style='mso-bookmark:OLE_LINK4'><span
style='font-size:16.0pt;font-family:"Eras Demi ITC","sans-serif";color:blue'>Attributes
of effective feedback<o></o></span></span></a></p>
<p class=MsoNormal align=right style='text-align:right'><span style='mso-bookmark:
OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><i style='mso-bidi-font-style:
normal'><span style='font-size:10.0pt;mso-bidi-font-size:12.0pt'>Anjali Sastry,
Kara Penn<o></o></span></i></span></span></p>
<p class=MsoNormal align=right style='text-align:right'><span style='mso-bookmark:
OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><i style='mso-bidi-font-style:
normal'><span style='font-size:10.0pt;mso-bidi-font-size:12.0pt'>Practicing
Management<o></o></span></i></span></span></p>
<p class=MsoNormal align=right style='text-align:right'><span style='mso-bookmark:
OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><i style='mso-bidi-font-style:
normal'><span style='font-size:10.0pt;mso-bidi-font-size:12.0pt'>September 2007
DRAFT<o></o></span></i></span></span></p>
<p class=MsoNormal align=right style='text-align:right'><span style='mso-bookmark:
OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><span class=GramE><b
style='mso-bidi-font-weight:normal'><i style='mso-bidi-font-style:normal'><span
style='font-size:10.0pt;mso-bidi-font-size:12.0pt'>do</span></i></b></span></span></span><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><b
style='mso-bidi-font-weight:normal'><i style='mso-bidi-font-style:normal'><span
style='font-size:10.0pt;mso-bidi-font-size:12.0pt'> not copy or share<o></o></span></i></b></span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><o> </o></span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>1. It is <i>descriptive
</i>rather than evaluative. It is important to focus on what the individual did
rather than to translate behavior into what he or she is. This is harder than
it appears at first glance! An example of describing versus evaluating is when
we might say that a person "talked more than anyone else in the meeting" rather
than that he is a "loudmouth" or a "terrible listener." Avoiding evaluative
language reduces the need for the individual to respond defensively.</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>2. It is <i>specific
</i>rather than general. To be told that one is "controlling" will probably not
be as useful as to be told that "in the project that just took place, you had
prominent opinions about how I should do my part, and I felt forced to accept
your methods because alternatives were not acknowledged by you." Or, rather
than saying "good job" after a team member's contribution, one might say, "Good
job. Your position was well-researched. I liked the way you integrated information
from past projects with your own research."</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>3. It is <i>directed
toward behavior that the receiver can do something about. </i>Frustration is
increased when a person is reminded of some shortcoming over which he has no control.
What might qualify as something that the person may have little control over?
Telling someone that they need to speak up at meetings when you know they've
had a throat injury might be one example. As an alternative, try "I know you
have difficulty speaking out in meetings due to the strain on your throat, but
your team would still love to hear your opinions. What are some ways you would
feel comfortable in expressing your opinions during these times and how can we
best support you to do those things?"</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>4. It is <i>well-timed</i>.
In general, feedback is most useful at its earliest opportunity after the given
behavior (depending, of course, on the person's readiness to hear it, support available
from others, etc.). The reception and use of feedback involves many possible emotional
reactions. Excellent feedback presented at an "inappropriate time" may do more
harm than good.</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>5. It
involves the <i>amount of information the receiver can use </i>rather than the
amount we would like to give. To overload people with feedback is to reduce the
possibility that they may be able to use effectively what they receive. This
holds true for both positive and negative feedback. Sometimes we get nervous
giving feedback and talk so much the message gets lost, or fail to focus on a
couple of key important points. When setting goals for a session think about
what's most important in your message—are there one or two behaviors that you
would like to see more of, or would like to see changed? Prioritize!</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>6. It involves
<i>sharing of information </i>rather than giving advice. By sharing
information, we leave people free to decide for themselves, in accordance with
their own goals and needs. When we give advice we tell them what to do, and to
some degree take away their freedom to decide for themselves. Compare the
following: "Your expectations of the team for this project weren't clear. You
should give them a written list during the meeting and reinforce with e-mail
later." Seems reasonable, right? But what about: "I wasn't clear about the team
expectations for that project, and it's possible others weren't either—what are
some ways expectations could be clarified in the future?" The feedback
recipient may still ask you for your ideas, but this allows her to take ownership
over the options.</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>7. It is <i>solicited
</i>rather than imposed. Feedback is most useful when receivers themselves have
formulated the kinds of questions that those observing them can answer or when
they actively seek feedback. Think about when you have received feedback in the
past—approaching your teammates or boss and asking for specific feedback on a
presentation. "Was my message about which vendor to hire and why clear? Why or
why not?"</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>8. It takes
into account the <i>needs of both the receiver and giver of feedback. </i>Feedback
can be<i> </i>destructive when it serves only our needs<i> </i>and fails to
consider the needs of the person on the receiving end. It should be given to
help, not to hurt. In an attempt to look good in front of a boss, a team member
might decide to offer negative feedback to another member about a bungled sales
call in the middle of a team meeting.<span style='mso-spacerun:yes'> </span></span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>9. It
concerns <i>what is said and done </i>and does not ask "why?" The "why" takes
us from the observable to the inferred and involves assumptions regarding motive
or intent. It is dangerous to assume that we know why a person says or does
something, or what he</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'><span
class=GramE>or</span> she "really" means or is "really" trying to accomplish.
Consider the following scenario: A coworker at the office has been unusually
quiet over the past week at a time when her opinions would have really
mattered. Approaching her with "You've been unusually quiet this week—are you
withholding your opinion because you didn't want to be on this assignment in
the first place?" may be way off base, and can put her on the defensive.</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>10. It is <i>checked
to insure clear communication. </i>One way to do this is to have the receiver try
to paraphrase the feedback he or she has received to see if it corresponds to what
the sender had in mind. One way might be: "I want to make sure that I've
communicated clearly—what <span class=GramE>do you</span> see as the primary
issues I've brought up today?" </span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>11. It is <i>checked
to determine degree of agreement from others. </i>When feedback is given in<i> </i>the
presence of other people, both giver and receiver have an opportunity to check
with<i> </i>others in the group about the accuracy of the feedback. This
validation is of value to both the sender and the receiver. This one can be
tricky—and considerations about openness to feedback, the dynamic of the group
present, and other factors may matter before checking for agreement. If there
is a power difference between giver and recipient, and others in the room, it
may be difficult to elicit hones opinions. However, this is especially
effective if a recipient has solicited the feedback, and by doing so indicated
openness to receiving.</span></span></p>
<p class=MsoNormal><span style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:
OLE_LINK4'>12. It is followed by attention to the consequences of the feedback.
People who are giving feedback may greatly improve their helping skills by
becoming acutely aware of the effects of their feedback. They can also be of
continuing help to the recipient of the feedback.</span></span></p>
<p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span
style='mso-bookmark:OLE_LINK3'><span style='mso-bookmark:OLE_LINK4'>13. It is
an important step toward <i>authenticity. </i>Constructive feedback given with
both giver and receiver's needs in mind can contribute to a<i> </i>relationship
that is built on trust, honesty, and genuine concern. Such a relationship<i> </i>can
open the door to personal learning and growth, and an ongoing feedback process.<i><o></o></i></span></span></p>
</div>
</body>