InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Giving and Receiving Effective Feedback

Posted by Mark Levison on Aug 25, 2009

Sections
Process & Practices,
Architecture & Design,
Enterprise Architecture
Topics
Careers ,
Human Resources ,
Agile
Tags
Agile2009 ,
Feedback

On Monday the first day of Agile 2009, Liz Keogh, gave session Giving and receiving effective feedback. The session was based around the different kinds of feedback that a fictional character George receives:

  • A glowing report of praise
  • A balanced report with some suggestions for the future
  • An unconstructive and possibly unfair review
  • The same review, rewritten after attending this feedback workshop.

Liz guided the audience in discussions around the feedback. She explained that feedback that is only full of praise doesn’t help the recipient learn anything new or grow. It encourages a person to say in the same position for ever. On the other hand when the person moves to a new position they’re likely to receive less happy feedback at first as they learn the new skills for the role. In this case its important that the feedback include the positive things that the person shouldn’t change and not just the negative. In George’s case the negative feedback was so poisonous it was clear that the person providing it was trying to push George out of the way and take his job. It really spoke more about the person giving the feedback than it did about George.

The group had a lively discussion around the samples:

  • Feedback should be given directly and not via a manager.
  • Talking Face to Face is safer for both parties than providing feedback in writing

Several strategies were suggested if you’re giving feedback to someone who is in position above you or has been in conflict with you. Ask for their help, saying “I need your help, we’re struggling with …”, take ownership of the problem, make it about the problem and not the parties. Finally a strategy that can weaken a person if overused – Admit fault publicly. 

Qualities of Good Feedback

  • Is about the recipient and not the person giving feedback
  • Is only from the point of the person giving feedback and not any third parties
  • Addressed directly to the recipient
  • Includes the things that the person giving the feedback values and not just areas for improvement
  • Makes suggestions and doesn’t just complain
  • Uses examples and doesn’t speak about generalities
  • Talks about things you’ve seen and heard i.e. instead of saying “the whole team was happy with your presentation”, say “the whole team smiled after your presentation”
  • Talks about the impact on you
  • Asks the recipient for help in making any changes that need to be made
  • End with a bright future, the positive goal that everyone is working towards
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?