Good Communication Is a Form of Risk Management

When something goes wrong, people don't respond only to the event. They respond to how they're treated afterward, and that response often decides whether a difficult problem stays a problem or becomes a conflict.

When something goes wrong, people are reading you. Were they taken seriously? Did someone listen? Did anyone explain what happened? Did the person responsible get defensive, disappear, or blame the person already dealing with the consequences? Did anyone acknowledge the impact? Those questions matter more than most organizations realize, because the answers to them frequently determine what the problem becomes.

Medicine has studied this for decades, because the stakes there are unusually visible. A small number of physicians accumulate a disproportionate share of malpractice claims, and the difference isn't explained by technical competence alone. In a large longitudinal study, physicians who accumulated more unsolicited patient complaints, about communication, access, respect, and interpersonal treatment, had significantly more malpractice claims and risk-management events, even after accounting for how much clinical work they did (Hickson et al., 2002). Patients of frequently-sued physicians were more likely to say the physician didn't listen, didn't return calls, was rude, or failed to show respect.

That doesn't mean good manners buy immunity from legitimate liability. It means something more useful. How a person behaves when there's a problem can decide whether a difficult event stays a solvable problem or hardens into a conflict. The skill involved isn't charm. It's relational judgment, the capacity to manage the human side of a bad situation without making it worse, and it's as useful for a landlord facing water damage, a manager handling a serious complaint, a contractor fixing defective work, or an executive dealing with a harmed customer as it is for a physician. When something has gone wrong, the quality of your response becomes part of the event itself.

People often escalate because they want an explanation

One of the more counterintuitive findings in the malpractice literature is that money isn't always the main driver of legal action. Families who pursued claims have described wanting information, wanting an explanation, and believing that things had been concealed or that they'd been misled (Hickson et al., 1992). Reviews of medical-error disclosure research find similar patterns, with a large majority of people pursuing claims reporting that they wanted an explanation, and a meaningful share saying that a fuller explanation or an apology might have changed their decision to pursue it.

This doesn't prove that an apology makes lawsuits vanish. The evidence on apology laws is genuinely mixed, and expressing regret without meaningful disclosure hasn't reliably changed outcomes. But it tells us something that generalizes well past medicine. People don't experience silence as neutral. They interpret it, and they interpret defensiveness, evasiveness, minimization, delay, and blame right alongside it. An absence of communication is not an absence of message.

Defensiveness creates a second injury

Something has already gone wrong. A patient has a complication, a tenant finds moisture damage, a customer loses money to an error, an employee reports conduct that should have been handled sooner. There is already a first problem. Then the person responsible says some version of that couldn't have happened, no one else has complained, you must have caused it, you're overreacting, we followed procedure, there's nothing wrong here. Now there are two problems. There's the original event, and there's the experience of being dismissed while trying to deal with it, and the second one was usually avoidable.

This is why defensiveness is so expensive. It converts a practical problem into a relational one. Once someone starts to believe you care more about protecting yourself than understanding what happened, the question in their mind changes. They stop asking only "how do we fix this?" and start asking "do I need to protect myself from you?" That is a very different, and much more adversarial, psychological position, and you put them in it.

Defensiveness also tends to produce blame, which is more combustible still. If accepting that we may have caused harm threatens our identity, status, finances, or sense of competence, the mind has ready ways to protect itself. We minimize the problem, question the person's credibility, hunt for alternative causes, emphasize everything we did right, and become unusually interested in the other person's mistakes. Sometimes those questions are legitimate, because causation does matter. But there's a large difference between investigating causation and reflexively building a case against the person who raised the problem, and people can feel which one is happening. The defense that makes you feel safer internally is often the move that creates the greater risk externally. The landlord who instantly decides the tenant is exaggerating, the manager who attacks the credibility of an employee raising a concern, each is managing their own shame or fear in a way that makes sense internally and can be disastrous in its result.

Responsibility is not self-condemnation

Part of why people get defensive is that they confuse taking responsibility with declaring themselves guilty of everything. Those aren't the same. Responsibility can be precise. We should have responded sooner. We don't yet know the cause, but this needs investigation. You shouldn't have had to make five calls to get an answer. That communication was poor. We made an error here. None of those statements requires accepting claims the evidence doesn't support. What they demonstrate is something more basic, which is the ability to stay psychologically present when the information is uncomfortable.

That's an executive skill as much as an interpersonal one. Weaker leadership tends to assume strength means defending the position. Stronger judgment often means identifying exactly what is yours, owning it early, and declining to defend what shouldn't be defended. Precise ownership is not weakness. It's the thing that keeps a problem from metastasizing.

Competence is experienced through a relationship

The classic communication research is more nuanced than the popular summary. In a study comparing physicians with and without malpractice claims, the no-claims primary care physicians used more orienting statements about what to expect, facilitated conversation more, used more humor, and spent modestly longer in routine visits, 18.3 minutes against 15.0 (Levinson et al., 1997). The same differences did not show up among surgeons, so this cannot be reduced to "bad manner gets you sued." But the direction is consistent. The interpersonal relationship matters, and poor explanations are a recurring source of the dissatisfaction that precedes escalation.

The lesson isn't that likability substitutes for competence. It's that competence is experienced through a relationship. People judge whether you're trustworthy partly by how you behave when the stakes rise, which means your technical skill is only as visible as your conduct lets it be.

The highest-risk moment is often after the mistake

Most organizations pour effort into preventing problems and spend far less teaching people how to behave once one has occurred, which is a mistake, because that's exactly the moment people are gathering information about who you are. After an adverse event they want to know several things at once. What happened. Whether you're taking it seriously. What happens next. And, underneath all of it, what kind of person or organization they're dealing with. Will you investigate honestly? Will you tell them what you find? Will you disappear when the information gets inconvenient? Will you make them fight for every answer, or punish them for raising the issue at all? Those judgments accumulate fast, and once someone concludes the system itself can't be trusted, escalation stops being emotional and becomes rational.

When something goes wrong, a useful response has roughly five moves. Listen before defending, finding out what happened from the other person's view before you build your rebuttal, which you can do without conceding facts you don't yet know. Acknowledge what's already clear, because if the communication was poor or there was a delay, you don't need full causal certainty to name the impact. Separate facts from questions, saying what you know, what you don't, and what needs investigating, since false certainty destroys credibility later. Own what's yours precisely, without overconfessing and without hiding behind ambiguity when something plainly failed. And explain what happens next, because uncertainty gets much easier to tolerate when people know there's a process, someone owns it, and they won't have to chase you. None of this is groveling. It's competence under interpersonal pressure.

Don't manufacture an adversary

Some people will stay angry. Some disputes are legitimate, some claims should be pursued, and some parties will act opportunistically no matter how well they're treated. Good communication is not a legal shield, and it shouldn't be used as a tactic to talk people out of asserting real rights. The principle is more basic than any of that. Don't create an avoidable adversary out of someone who came to you with a solvable problem.

Organizations do this constantly, and the sequence is almost always the same. Someone raises a concern. The organization feels accused. The organization protects itself. The person experiences that protection as dismissal. They escalate. The organization reads the escalation as proof the person was unreasonable from the start. Now both sides are defending themselves and the original problem is nearly beside the point. What could have been a repair has become a contest, and the contest was self-inflicted.

This is where relational judgment does its real work, because how you respond is itself part of the evidence people use to decide what to do. A company can say it values customers, a leader can say people should speak up, but the real test arrives when someone brings information you don't want to hear. Do you get curious or defensive? Investigate or discredit? Communicate or disappear? Take appropriate responsibility or immediately look for someone else to blame? That response shapes more than reputation. It tells the other person whether cooperating with you is likely to work, and if cooperation looks unlikely, seeking leverage elsewhere becomes the reasonable move, whether that's a formal complaint, a regulator, an attorney, or simply a customer, tenant, employee, or partner who quietly never works with you again. Relational judgment doesn't eliminate conflict. It keeps preventable conflict from becoming the price you pay for protecting your ego.

References

Hickson, G. B., Clayton, E. W., Githens, P. B., & Sloan, F. A. (1992). Factors that prompted families to file medical malpractice claims following perinatal injuries. JAMA, 267(10), 1359–1363.

Hickson, G. B., Federspiel, C. F., Pichert, J. W., Miller, C. S., Gauld-Jaeger, J., & Bost, P. (2002). Patient complaints and malpractice risk. JAMA, 287(22), 2951–2957.

Levinson, W., Roter, D. L., Mullooly, J. P., Dull, V. T., & Frankel, R. M. (1997). Physician-patient communication: The relationship with malpractice claims among primary care physicians and surgeons. JAMA, 277(7), 553–559.