Acknowledge the Problem Before You Explain It

When someone brings you a legitimate complaint about how your unit treated them, the explanation of why it happened is usually true, usually relevant, and exactly the wrong thing to say first.

Someone is sitting across from you, or writing to you, because something your unit did went wrong for them. They were told one thing by one person and another thing by someone else. A deadline they were promised passed without a word. A request they made three times was lost each time. They are not being unreasonable, and you know it, because as they talk you can already see how it happened.

So you tell them. You explain that two offices were working from different versions of the policy, that the person who usually handles these requests was out for a month, that a system change in the spring moved things around. Every word of it is accurate. You are trying to be transparent, and you believe that if they understood how it happened, they would feel better about it. They do not. By the end of the conversation they are more frustrated than when they arrived, and you leave wondering what more you could have said.

The mechanism is the order, not the content

When a person has been let down, they arrive with one question underneath everything else: does the person I am talking to agree that this should not have happened to me? Until that question has an answer, everything else they hear gets sorted by how it bears on it.

An explanation offered first gets sorted as a case for the defense. You meant it as context. They hear it as a list of reasons the problem was understandable, and something understandable sounds a great deal like something nobody needs to fix. The more thorough and reasonable your account, the stronger that impression becomes, because a detailed explanation delivered before any acknowledgment sounds prepared, and a prepared answer sounds like one you have given before.

The same explanation, offered after you have plainly said that they were treated badly and that it should not have happened, does different work. It is no longer an argument about whether the problem is real. It has become an account of what went wrong, which is what the person needs if they are going to believe you can keep it from happening again. The content did not change. What it was for did.

This is also why the pattern is so hard to catch in yourself. Leaders who explain first are rarely being defensive on purpose. Most of them are being honest in the way they were trained to be, by giving people the full picture as quickly as they can. The trouble is that the person across from you did not come for the full picture. They came to find out whether anyone on your side of the table thinks they were wronged, and the full picture, however complete, does not answer that.

What explaining first costs

The person leaves believing nothing will change. Someone who hears the reasons before they hear the admission reasonably concludes that the reasons are the point. If the causes were a staffing gap and a policy mismatch, and nobody has said those causes were a problem, the person assumes both will still be there next month. They are usually right.

The complaint moves somewhere you cannot see it. People who feel unheard in the first conversation rarely stop there. They tell colleagues, go over your head, or write to someone with more authority and less context. The next version of the story will not include your explanation, because by then it has become part of the grievance, remembered as the moment you defended the unit instead of listening.

Your staff learns what you will say for them. The people in your unit watch how you handle a complaint about their work. When your first move is to explain the conditions that made the mistake likely, some of them hear support, and some of them hear that the mistake is acceptable as long as the conditions are hard. Neither lesson helps them fix the thing that went wrong, and the second one makes it more likely to happen again.

Three moves

Say what happened to them before you say why it happened. Name the specific failure in plain terms: they were given two different answers, they waited without hearing anything, the request was dropped. Say that it should not have happened. Then stop long enough for them to respond. This is not a technique for lowering the temperature. It is a statement of fact that you agree with, and if you do not agree with it, you are not ready to have this conversation yet.

Then give the explanation in service of the fix. Once the acknowledgment has been made, the account of what went wrong becomes useful to both of you. Keep it short, tie each cause to what you are going to do about it, and leave out the parts that only exist to show the situation was difficult. If the explanation contains no cause you intend to address, it is not an explanation yet. It is an account of why you are not going to do anything.

Commit to one change you can actually make, and tell them when they will see it. An acknowledgment with no change behind it is worse than none, because the person will eventually notice that nothing happened, and the next time you say you are sorry, they will remember that too. Pick something within your authority, give it a date, and follow up yourself. If the right fix is outside your authority, say so and tell them who you are taking it to.

The part that is about you

Leading with the explanation is often an act of loyalty. You know the people in your unit, you know how hard the last few months have been, and you do not want someone outside the unit to walk away thinking your staff is careless. Explaining first feels like protecting them.

It is worth noticing that the person in front of you does not need to think your staff is careless in order to be right. Both things can be true: your people were working under real constraints, and someone was still treated in a way you would not accept for yourself. Saying the second thing first does not betray the first. It makes room for the person to hear it.

Three questions

In the last complaint your unit received, what was the first thing anyone said back to the person who raised it?

When you explain a failure to someone outside your unit, which of the causes you name are you actually planning to change?

Is there someone who brought you a problem in the last few months, heard your explanation, and never raised it again, and do you know whether that was because it got fixed?