What does your first response teach the team after a mistake?

Early in my career, I made a mistake while communicating a billing estimate to a client.

I intended to send the revised commercial figures. Instead, I forwarded the message with the internal email trail still attached. By the time I realized what had happened, there was no way to recall it.

I remember walking towards my manager's desk convinced that I had caused serious damage and that the conversation might end very badly for me.

I told him exactly what I had done.

He did not raise his voice or humiliate me. He calmly reminded me to be more careful and then dealt with the situation. The standard remained clear, but so did my dignity.

I have carried that response with me for more than two decades.

Project leaders often say they want risks and mistakes reported early. But I suspect the team decides whether that is truly safe by watching what happens to the first person who brings difficult news.

If the immediate response is anger or public embarrassment, people may become more careful about what they reveal. The next issue might be softened, delayed or handled quietly until it has grown much harder to contain.

Calmness does not mean overlooking the mistake. The consequences still need to be understood, the immediate risk contained and the learning made clear. But accountability does not become stronger merely because the person feels smaller.

I have not always responded as calmly as my manager did that day. Pressure can make grace difficult. Yet his example still reminds me that our first reaction is not only about the problem in front of us. It is also teaching the team how honestly they can speak to us the next time something goes wrong.

How do you balance accountability with a response that keeps honest communication possible?