This post originated from an RSS feed registered with Agile Buzz by Keith Ray. Original Post: Feedback Feed Title: MemoRanda Feed URL: http://homepage.mac.com/1/homepage404ErrorPage.html Feed Description: Keith Ray's notes to be remembered on agile software development, project management, oo programming, and other topics. Latest Agile Buzz Posts Latest Agile Buzz Posts by Keith Ray Latest Posts From MemoRanda

Matt Heusser writes on StickyMinds:

In less-healthy organizations, feedback may be viewed as criticism or personal attack. When this happens, the organization cuts off its own ability to react and respond to change. ...[feedback] must be positioned so the recipient does not feel insulted or drawn into a spitting contest.... Another way to foul up the works is to point out problems without offering solutions. ... try asking simple, open-ended questions. ... "What are the issues I'm forgetting?" "What does success mean?" ... Even if your feedback is well received, and you find or fix what would otherwise have become a major fly in the ointment, you run the risk of being perceived as the "Savior" who will "put the project back on track." There is another name for a Savior whose project fails: scapegoat.