Skip to main content

Various ways to react to a mistake

When a person makes a mistake it is fascinating to see how they respond. Based on the situation and nature of the person who makes the mistake there are various ways one can react. I tried to broadly divide the reactions into following 7 categories:
  1. No I didn't make a mistake – I never do any! 
    This is the kind of response we give when we don’t want to agrees to the mistakes we do. Even the mistakes of worst nature i.e. blunders would not deter us from self-protection. This behaviour could be because the person really believes that it isn't their mistake or it could be that the person knows it but isn't brave enough to accept the mistake. The problem with this behaviour is that the person doesn't learn from the mistakes and keep making them again and again.  
  2. It’s not my mistake, I did it because...
    Most of us use this in scenarios where we try to find excuses for our short comings. The hard core section of this group of people try to find a reason and believe that is unavoidable and not in one’s control. Sometimes the reasons are so bizarre that the believing in the reason itself becomes a mistake.This behaviour helps in reducing any sadness caused due to the mistake as finding the reason, however absurd the reason might be, gives the person a chance to be relieved of any guilt.
  3. It’s others fault
    This kind of behaviour is almost similar to the one above but it is different in a way that the reason we find is always other people rather than things. At times the blame can be moved from one person to other based on who is readily available to blame on
  4. Who are you to point out my mistakes!
    This is the reaction you get from people who are either arrogant or really crossed about their mistake. The only problem is that this leads to confrontation with the person who pointed out the mistake unless the other person is composed
  5. Yeah I made a mistake so what?
    When the person “thinks” that the mistake is very small then one gives this response. But this thinking might irritate others who bear the brunt of the mistake. So it’s better to be humble to every mistake done and try to think from others perspective.
  6. Oh sorry I made a mistake – will try not to repeat
    This is probably the ideal response. As some famous person said – one who doesn’t make any mistakes is not human – it is impossible to lead a life without mistakes so the best thing to do is to not repeat the same mistakes but try doing brand new ones. This is only possible if we learn from the mistakes we make
  7. I made a mistake – I should make others life hell with my apologies
When people think that their mistake is so naïve and/or horrible they try to undo the mistake by apologising very hard. But this makes apologising itself a bigger mistake than the original one. Yes one should apologise to mistakes but should not go overboard. If the mistake is so bad that it caused irreversible damage then it is better to show that you are sorry in action rather than just by words which after some time becomes useless.

Though some of reactions are mistakes themselves every person must have used almost all the kinds of reactions in various situations. If making mistake is bad, not reacting appropriately is a blunder. As we keep growing up we need to learn how to not repeat a mistake and this learning starts from our response to mistakes.

Ideally we should all be humble to every mistake we make but as we are human it is not possible, so the best we can do is to learn from them and make learning a habit.

Comments

Popular posts from this blog

Development Process

I worked in different roles for different companies and in each role there was some talk about reviewing and optimizing development process as it was thought that the current process is either too laborious or too simplistic, yes too simplistic processes aren’t too good either. You might think that simple process is the way to go but not always. Let me explain. If the team is working on a green field project, the development team is aware of the business domain, are technically capable of producing good code and detailed coding standards are defined at team or company level then simple process of [design-> develop->test->deploy] will work. But if this team has been working on this project for some time say 6 months and a new developer joins the team then this simple process will start to fail. By the time this developer joins the team there is already some code in place that is developed to certain standard and this developer doesn’t have any knowledge of the application tha...

Time for a United Telugu Front

Past few years have been stressful for a person of Telugu origin, be it a supporter of separate state or in favour of a unified state. The agitations had a bad impact on the economy of the state, which at one point, not distant past, has been the most talked about for its booming economy. People in favour of a separate state for Telangana should not misunderstand ‘United Telugu Front’ to a ‘Unified State’. Regardless of Telangana state being formed or not it is apparent that a deep division has been created between Telugu people from Telangana and Non-Telangana region because of vested interests of Politicians and so called well-wishers. This division should be cured with utmost urgency and care, otherwise Telugu people will only have failed state(s). Idea behind ‘United Telugu Front’ is to have a common organisation for Telugu people which is non-political and which helps us fight as a single force. It is very clear, after the issue of bail to a political leader, that centra...

Agile Scrum Estimation

In this article I will try to explain the estimation process in Agile Scrum methodologies. Before going into details here is just an advice: As the team has to estimate for every sprint it is a good practice to follow same principles right from the first sprint and keep improving or modifying the process as you progress through the project, but never completely ditch the process and start afresh, unless every member of the team is completely at ease with the new process changing to a brand new process will cause confusion above the team and all the lessons learned in all previous sprints will be lost. While using Scrum each item chosen to be developed in the sprint have to be estimated. Now this estimation process is drastically different to the old practices like single person estimating for the whole work and on behalf of the entire team or each developer estimating their own work in isolation. Estimation process in Scrum helps to bring the whole team work as a single...