For nine years, they had built a professional bond rooted in trust and mutual respect, but lately, cracks began to show. The mistakes weren’t minor slips but glaring errors that threatened not only the work’s integrity but the reputation of their entire team. The weight of disappointment hovered silently between them as one struggled to reconcile the friend they knew with the colleague whose work was now under scrutiny.
In a private, heartfelt message, the concern was laid bare—not with judgment, but with an urgent plea for reflection. The relentless pace had taken its toll, and the hurried efforts left a trail of oversights that others outside their circle could see all too clearly. It was a moment heavy with unspoken hopes: that the bond forged over nearly a decade could endure this storm, and that the mistakes might soon be replaced with renewed care and precision.
Coached a co-worker for making mistakes
According to organizational psychologist Dr. Amy Edmondson, psychological safety—the belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes—is crucial for high-performing teams, especially in error-prone environments. In this scenario, the writer attempted to create safety through peer review, but the friend perceived the subsequent documentation of errors as a threat, leading to defensive aggression.
The friend’s reaction, characterized by extreme hostility and profanity, strongly suggests that the feedback attacked his professional identity, triggering a ‘fight or flight’ response. The fact that the friend was possibly intoxicated and responded via text outside of work hours complicates the interpretation, but does not excuse the unprofessional behavior. The writer’s initial email, while factually correct and aimed at being non-judgmental (“just to the point, not judging or blaming”), was perceived as accusatory because it detailed how the errors occurred (“copy/pasting at a million miles an hour”). In highly stressed environments, even necessary constructive criticism can be misinterpreted when delivered without sufficient cushioning or validation of the effort expended.
The writer’s final attempt to defer the conversation (“Dude. Enjoy your vacation time with the family. We’ll talk next week.”) was the correct de-escalation tactic, buying time for emotions to cool. However, for future interactions, the writer should prioritize framing feedback around processes and outcomes rather than perceived effort or speed (e.g., instead of citing ‘whipping thru them,’ focus solely on the documented errors and the potential impact on cutovers). In a government-regulated, safety-driven environment, documentation of performance issues is mandatory; the challenge lies in delivering that documentation in a manner that protects the professional relationship, likely requiring a shift from written documentation to a private, face-to-face conversation where tone and intent are clearer.
REDDIT USERS WERE STUNNED – YOU WON’T BELIEVE SOME OF THESE REACTIONS.
The writer acted based on a professional duty to maintain quality and safety in a high-stakes environment, which led to a direct confrontation with a long-term work friend. The conflict centers on the friend’s intense negative reaction to receiving necessary, albeit blunt, performance feedback, revealing a breakdown in their professional and personal boundaries.
Given the severity of potential errors in their regulated field, was the writer justified in delivering direct, written feedback, even if it triggered such a hostile response, or should the friendship have mandated a more indirect, private approach? This situation forces a debate between rigorous professional accountability and preserving workplace relationships.
