Should developers Criticize Publicly in the team?
Praise in public and critique in private when working as a team can help you to show your support, your consideration as well as your respect toward your teammate. However, direct feedback can allow you to teach, to show, or to remind your teammate what the code of conduct says and what you tolerate in the workplace.
Constructive feedback is as important as the willing to give the feedback. I want to focus not on the critics we have to give but on how much we should consider the structure of our feedback because the form of giving feedback can hurt, if they are given in a wrong way.
If you want to learn more about constructive feedback click here
Criticizing or giving feedback is the way we can use to show to your team members what is acceptable for you, what you can tolerate, what you don’t. However, we have to consider certain things before giving feedback. A feedback should include the professional progress of the person we are giving the feedback to, if not I must suggest you to ask these five questions:
- What is the outcome you are looking for?
- Are you trying to help your team members?
- Do care about them?
- Can They trust you?
- Do you want to create more rowers or sinkers?
The desire to give feedback can never be higher than the desire to see the progress of the team you are working with. Focus deeply on the outcome you want.
Critiques can help your teammates grow and improve. But a public critique that is given at a bad moment can look disrespectful and impolite. So we have to consider the income and outcome that will be involved before criticizing in public.