Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Neuroscience of Feedback: Bypassing 'Fight or Flight' to Build a Non-Toxic Engineering Culture

When you deliver unfiltered criticism, you are not engaging an engineer's logic. You are triggering their mammalian threat response. Poorly calibrated feedback registers in the human brain as a physical attack. The recipient immediately shifts from problem-solving to self-preservation. To orchestrate a non-toxic engineering culture, leaders must understand how to bypass the amygdala and…

The article discusses the neuroscience behind feedback and how to deliver it in a way that prevents an "fight or flight" response in engineers, which can lead to a toxic engineering culture. When engineers receive unfiltered criticism, their brains interpret it as a physical attack, shifting their focus from problem-solving to self-preservation.

The author outlines an operational framework for delivering uncompromising feedback without triggering a negative response. The first step is to establish a positive baseline. This means reinforcing correct execution and creating a culture where engineers feel safe and confident in their abilities. The second step is to decouple the artifact from the architect, meaning that failures should be addressed without attaching a failure to an individual's identity.

The third step is to deploy a psychological safety anchor, which involves stating that you are sharing feedback because you have high standards and confidence in the individual's abilities. This helps the recipient view the feedback as an opportunity for growth rather than an attack on their worth. The fourth step is to control the timing and seek permission before delivering feedback. This helps to prevent the nervous system from being "jump scared" and allows the engineer to mentally prepare for the critique.

The author also emphasizes the importance of leaders mastering receiving feedback themselves without triggering a defensive spiral. This can be achieved by reminding oneself of their technical competence and past successes, treating incoming notes as data about a specific project, and maintaining the separation between the work and one's career. By following these steps, leaders can create a non-toxic engineering culture that fosters collaboration, innovation, and continuous improvement.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Callback That Kept Rendering Data From Twenty Minutes Ago

A closure doesn't capture the one variable you meant to use; it captures a strong reference to its entire outer lexical environment. Left unmanaged, that environment never leaves memory.

  • Asynchronous function fetched updates for dashboard grid
  • Closure captured entire outer lexical environment
  • Stale data and memory usage increased

More from Thursday 3 September →