Communicating and leading, one lesson a day

Imagine you lead a volunteer search-and-rescue team. During a navigation exercise, a new map reader questions the route you chose. Rain is moving in, daylight is fading, and you answer in front of the group: “If you knew the terrain, you would understand why this is the route.” The volunteer goes quiet. Ten minutes later, you notice that the contour line was easy to misread and the question was reasonable.

You still believe the route is correct. You also know your answer made it harder for anyone else to question you. That is today's lesson: what to do after a sharp moment, while it is still small enough to repair.

The goal in a working relationship is not to reach zero conflict or zero mistakes. That standard is impossible, and chasing it can make people hide what happened. The useful standard is a short distance between harm and repair.

John Gottman's lab spent decades observing couples in conflict. Gottman became famous for predicting which relationships would last, and people often assume the strongest relationships were the ones with the least anger. They were not. Stable couples could disagree intensely. What mattered was their use of repair attempts: small moves during or after conflict that restored the sense that both people were still on the same side.

A repair attempt could be humor, a softer restart, or a simple acknowledgment that something came out wrong. Relationships suffered when those attempts were absent, missed, or rejected. Work relationships are not marriages, but this mechanism travels. A team does not need a leader who never has a bad moment. It needs a leader who notices the moment and reliably crosses the distance back.

Research on apologies helps define what that crossing should contain. Roy Lewicki, Beth Polin, and Robert Lount tested apologies made from different combinations of six parts: regret, explanation, acknowledgment of responsibility, a promise to change, an offer of repair, and a request for forgiveness. Two parts carried much of the weight. The person needed to take responsibility and offer a concrete repair.

Aaron Lazare's work on apology reaches a similar conclusion. A useful apology names the offense clearly. “Sorry things got tense” describes the atmosphere. It does not show that you understand what you did. “I dismissed your question in front of the team” names the behavior. Specificity is evidence that you saw the same event the other person experienced.

This can be difficult when you were right about the underlying issue. The rescue leader may still know that the western route is safer. The restaurant owner may still need the kitchen closed properly. The editor may still need the facts checked. When your point is valid, an apology for your delivery can feel like surrendering the point.

Separate the two objects. One is the standard or decision. The other is the way you treated someone while protecting it. Repairing the second does not erase the first. In fact, a clean repair can make the first easier to discuss because the other person no longer has to defend their dignity before they can hear your reasoning.

For the rescue leader, a repair might sound like this: “I dismissed your route question in front of everyone. That was mine, and it made it harder to raise a safety concern. Next time I will ask you to show me the feature you are reading before I answer. For this route, I still want us on the western ridge because the creek crossing rises quickly in rain.”

The standard remains. The contempt leaves.

A strong repair has four moves. First, make it soon and use the channel where the harm happened. If the comment was public, correct it publicly enough that the people who learned the wrong lesson also hear the repair. A private follow-up may still be appropriate, but it should not leave the group believing that questions are punished.

Second, name the specific behavior and its effect. Do not use “if” to make the injured person prove that harm occurred. “If that sounded dismissive” means you are apologizing for their interpretation. Say what you did: “I answered your safety question with a put-down.”

Third, own it without attaching a counterattack. The word “but” often deletes the sentence before it. Explanation can help when it gives context, but context belongs in a separate sentence and must not transfer blame. “I was watching the weather and rushing” is context. “You challenged me in front of everyone” is a charge wearing an apology's coat.

Fourth, name one small behavior that will change. The promise should be observable and realistic. “I will become a more patient person” is too large to verify. “When someone questions a route, I will ask them to point to the map before I answer” is a practice. An apology becomes more credible when it changes the next scene.

Then stop. Do not ask the other person to reassure you. A request for forgiveness gives them a new task: manage your discomfort and declare the matter closed. Offer the repair and let their response belong to them.

Amy Edmondson's work on psychological safety explains why this is leadership, not just good manners. Teams learn whether it is safe to report a concern by watching what happens to the first person who does it. A leader who repairs openly demonstrates fallibility without giving up authority. That lowers the social cost of speaking up.

In search and rescue, that can be a safety issue. If volunteers learn that a question earns humiliation, the next person may stay quiet about a washed-out trail or a wrong bearing. The damage from one sharp answer is not only how one person feels. It is the information the whole group may withhold later.

Visible repair also teaches a repeatable norm. It says a mistake in this team does not require denial, disappearance, or a week of tension. It requires honest naming and a credible next move. People with less power are more likely to repair their own mistakes when they have seen someone with more power do it without collapsing.

One caution: do not apologize for every firm decision simply because someone dislikes it. Repair is not retreat. If the team must leave the trail, say so. If a safety rule was broken, address it. The apology is for mockery, interruption, accusation, or disrespect, not for holding a necessary boundary. Confusing those things produces weak leadership because you either defend bad behavior or abandon good standards.

Here is the practice. Think over the last week and identify one exchange you would handle differently. Write four sentences. Name the exact behavior. Take responsibility without “but.” Name its effect. Promise one small action for next time.

Send or say the repair in the channel closest to the original event. If other people witnessed the behavior, let them witness the ownership. Do not add a request to be forgiven. Then notice the next exchange. Is the person quicker to raise a concern? Are you less defensive hearing it? That ease is part of what the repair purchases.

If no moment comes to mind, practice with the rescue scenario. Say the repair aloud until it takes less than a minute. Speed matters because shame will try to turn a simple repair into a long delay. A clumsy repair today is usually more useful than an elegant one after everyone has learned to work around you.

Sources today: John Gottman and Robert Levenson, “Marital Processes Predictive of Later Dissolution,” Journal of Personality and Social Psychology, nineteen ninety-two, and Gottman's later work on repair attempts. Roy Lewicki, Beth Polin, and Robert Lount, “An Exploration of the Structure of Effective Apologies,” Negotiation and Conflict Management Research, two thousand sixteen. Aaron Lazare, On Apology. Amy Edmondson, The Fearless Organization.

That is lesson forty three. Keep the standard, repair the disrespect, and make the distance between the moment and the return as short as you can.