{"id":12067,"date":"2014-03-16T23:09:58","date_gmt":"2014-03-16T21:09:58","guid":{"rendered":"http:\/\/mozaicworks.com\/?p=6380"},"modified":"2023-09-15T15:06:54","modified_gmt":"2023-09-15T12:06:54","slug":"give-feedback-for-performance","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/give-feedback-for-performance","title":{"rendered":"Give feedback for performance"},"content":{"rendered":"
Feedback is one of the most powerful tools a manager, developer or HR professional can use to\u00a0reduce mistakes\u00a0<\/strong>and\u00a0increase performance<\/strong>. It is a key practice in Agile and Lean and, although it sounds easy it is quite hard. Read this post for a more detailed description of good practices for feedback inside a development team.<\/em><\/p>\n Feedback loops are everywhere<\/strong>. They exist between people, between developers and code and between the product you\u2019re creating and its users. The question is:\u00a0do you take advantage of feedback? Or do you just ignore it?<\/strong><\/p>\n In engineering,\u00a0feedback cycles are used for reducing errors<\/strong>.\u00a0Flying space shuttles, modern cars cruise control or increased sound quality<\/a>\u00a0are only few of the modern successes that wouldn\u2019t have been possible without feedback. Inside a\u00a0 software development team or when managing such teams, feedback can be used for improving the results by catching mistakes early.<\/p>\n Let\u2019s take as example code review. Code review is the practice for one developer to read the code written by another developer and give feedback in order to eliminate potential programming problems. This simple practice applied on all production code has been shown to catch as much as 60% from total bugs, in some cases\u00a0reducing maintenance expenses by hundreds of thousands of dollars.\u00a0Yet, code review is nothing more than feedback on code from a colleague.<\/p>\n Two things differentiate useful from useless feedback:<\/p>\n Let\u2019s take as example performance reviews. Most companies since do yearly reviews, which means that each year you meet with your manager and she lets you know what you did well and what you didn\u2019t do well the past year. There are multiple problems with this approach, including that none of you will remember exactly what happened 6 months before. Moreover, how often can you change your behavior based on the feedback, if you only get feedback once a year?<\/p>\n Reducing the feedback cycle for performance\u00a0reviews ultimately turns them into\u00a0bi-monthly one-to-one meetings<\/strong>. Managers would meet with each employee and discuss based on recent events, allowing both of them to adjust their behavior and strategy.<\/p>\n Early feedback is not enough if you can\u2019t\u00a0act on it<\/strong>. A typical example is a manager telling a team that \u201cthey must do better\u201d without\u00a0clarifying:\u00a0what needs to improve, who will improve it and how.<\/p>\n Giving feedback to another person is difficult<\/strong>, especially for introvert personalities like most developers.Good feedback is based on facts, future-oriented and impersonal<\/strong>\u00a0(related to an action\/behaviour and not to a person). Starting with a simple feedback template and practicing it makes wonders and helps increase the quality of feedback inside a team. Here\u2019s the template we usually use:<\/p>\n When you [Past Action], [Result of the Action]. What could we do to prevent it from happening again?<\/em><\/strong><\/p>\n For example, using this template:<\/p>\n Agile, Lean and Software Craft practices are all about reducing feedback time and improving feedback quality.<\/p>\n For example:<\/p>\n and so on.<\/p>\n In a later post we\u2019ll cover feedback from a managerial perspective.<\/p>\n How helpful is feedback for you? Let us know in the comments!<\/em><\/p>\n If you want to better understand the performance for development teams, we can help you with:<\/em><\/p>\nConsider the following:<\/h2>\n
\n
The difference between flying a space shuttle and a big BOOM!<\/h2>\n
Not all feedback is equal<\/h2>\n
\n
How to give feedback to your team mates<\/h2>\n
\n
How to get better feedback from the code<\/h2>\n
\n
\n\n