Skip to main content

Absorbing Feedback


We all want to improve, absorbing feedback is the most important step in the process of improvement. Even when we get feedback, we don't know how to act on it.

We have good techniques for giving feedback like SBI (Situation, Behavior, Impact) however, it took me some time to develop a good framework to absorb and act on feedback. Let me start with a real-life situation:

A couple of years back, I received feedback, however incapable of acting on it. I was struggling to make any improvement. During this phase, I developed the framework which helped me. 

This framework has two attributes "Understand Deeply" and "Act Swiftly". 

Understand Deeply is about understanding the feedback and situations where behaviour is depicted so that you can relate to the situation. Some situations bring out the same undesired behaviour. It is also very important to understand the intent of the feedback. 

Act Swiftly talks about acting on feedback, taking steps to implement the feedback and correct the behaviour. It is really important to act promptly on feedback, people are more likely to give feedback if they see action on it.





These behaviours don't work in isolation but rather has an amplifier impact when combined together.

Let's start with the first quadrant on the top left corner and go anti-clockwise.

Insincere quadrant, in this quadrant feedback, is well understood however not ready to act. There could be multiple reasons for not acting on a feedback example it requires some fundamental behaviour change, requires too much effort etc. One way to change is to try to divide the feedback into smaller pieces and tackle a piece at a time.

 Indifferent quadrant this is the hardest quarter to be in where you don't (want to) understand the feedback because the intent to act on the feedback is missing. Change needed in this situation is fundamental. Burnout, de-motivation or lack of interest could be some of the reasons. Taking a break sometimes help, if its a team, work or manager related issue changing the team or even the company might also help.

Next comes Frustrated quadrant where feedback is being acted upon is not getting addressed and all the is going waste. It's best to take a step back to try and understand the feedback more deeply. Same feedback in a different situation could have very different meanings.

True and lasting change happens when we understand the feedback and act upon it promptly to go through change-learn-improve cycles. Remember when the feedback is well understood it becomes easy to incrementally improve.

Hope this helps.

Comments

Popular posts from this blog

Master Detail

Master-Detail Eclipse Forms I just finished working on the editor which uses the Master-Detail pattern of the eclipse forms. During which I faced several problems like: In my master block, when the size of table-viewer increased, the master block shows the scrollbar instead of table-viewer. Also, it made the length of the detail and master parts equal which made my editor unusable Detail part having scroll problems like the one mentioned above Setting the details part data-dynamically was yet another area where I faced a lot of problem In this blog, I will be giving a brief introduction about the master-detail pattern and will be addressing the problems mentioned above. The article by Dejan Glozic is really helpful and explains the basics of the eclipse forms. I’ll be explaining the stuff using FUSE Integration Designer(FID) which is an open source and available for download . And the screen-shots will be from the Messaging module of the FID using the example of JMS Messages . In

Interview at Progress Software

I have given a lot of interviews before however, this one was special. Let me start from the beginning. I got a call from Progress Software and was scheduled for the first telephonic discussion. Next day, I got a call from HR and she asked me questions on Java and a few basic puzzles.  After clearing the previous round, I got scheduled for the second telephonic interview. This interview covered Java, design-related problems and algorithms. After a week, I got a call from the HR for the onsite interviews in Hyderabad. This is the first time I googled about Progress Software. I said yes for the onsite interviews. Journey to onsite started not as planned after my flight got delayed. Because of fog-related delay in Delhi, I reached the PSI (Progress Software India) office couple of hours late.  HR introduced me to the first interviewer. The interviewer explained the first round. It was a coding round (I am not a big fan of coding rounds), the problem was well expl

java.net.SocketException: Connection reset

I am able to fix the problem via setting the following params on the HTTPClient class... client.getParams().setParameter("http.socket.timeout", new Integer(0)); client.getParams().setParameter("http.connection.stalecheck", new Boolean(true)); java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77) at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105) at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115) at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832) at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590) at org.apache.commons.httpclient.HttpMethodBase.execute(