How to tell your friend he's wrong and keep the friend

Quick answer: Check the original source before you say a word. Correct him in private, with a question instead of a verdict. Concede whatever part is true, and let him save face.

The group chat has an unwritten rule: whoever corrects the post pays for it. You know the feeling. A buddy forwards a chart or a screenshot, three guys react with a thumbs-up, and you're the one holding the correction like a dead fish at a cookout.

You can be right and still lose. Plenty of guys do it every week. Winning the fact and losing the friend isn't a win, and the friend is the person you were trying to help.

Pin down what was actually said

Half of all arguments are about a paraphrase. Your friend says "they're hiring an army of IRS agents." You say that's false. He means the broad point, you mean the exact number, and now you're fighting different fights.

Before you correct anything, restate the claim in one sentence and get him to agree it's what he meant. "So the claim is that the new law adds 87,000 IRS agents. That the one?" Now you both know the target.

It takes thirty seconds. It also shows him you listened, which matters later.

Sort the claim before you check it

Not everything can be fact-checked. Know which kind you're holding.

• A fact: a thing happened or it didn't.
• A number: how big, how many, compared to what.
• A cause: this happened because of that.
• A prediction: this will happen. You can't check it yet, only judge the reasoning.
• A value: this is right, or wrong, or too much.

"Taxes are too high" is a value. You can't fact-check a conviction, and you shouldn't try. You can check "taxes went up forty percent last year." Most bad arguments come from treating a value like a fact, or sneaking a value in under a number.

Causes are where people get burned most. Two things happening at once is a clue, not a finding.

Go to the source, then one step past it

The article about the study isn't the study. The post about the quote isn't the quote. Find the document, the transcript, the full video, the actual table. Then ask who made it and what they'd gain if you believed it.

Take the 87,000 figure that circulated after the 2022 IRS funding bill. It traces to a Treasury Department document about hiring over a decade. Read that document and two things change the picture. A lot of that hiring replaces people who retire, and many of the jobs are in taxpayer service and support, not enforcement. The number isn't invented. The frame around it's a stretch. Both of those can be true, and the honest version of the argument against that funding doesn't need the stretch. You can oppose a bigger IRS on its merits and still say the claim got inflated in the retelling.

Run the same test on your own side first

If you only check claims you dislike, you're not fact-checking. You're doing opposition research.

"Hands up, don't shoot" became a rallying cry after the 2014 shooting in Ferguson, Missouri. The Justice Department's 2015 report on the shooting found no credible evidence that Michael Brown had his hands up in surrender, and it didn't bring charges against the officer. Plenty of people repeated the slogan as fact long after the report came out. The same department's separate report on the Ferguson police department found real problems with how the city policed and fined its residents. Both findings came from the same agency, and both were true. You can only hold both if you read the whole thing.

The test cuts every direction. Even the apolitical stuff fails it. The "eight glasses of water a day" rule gets traced back to a 1945 federal nutrition recommendation, which also said most of that water already comes in prepared food. Somebody dropped the second half of the sentence, and the rule outlived it.

A good habit: before you correct a friend, ask yourself when you last corrected someone on your own side. If the answer is never, check your own shelf first.

How to say it

Pick the channel before the words. Don't do it in the group chat unless the post is harmful and spreading. A correction in front of an audience is a performance, and he'll defend himself against the audience instead of the facts.

Send him a message. Or say it in the truck.

Then use a question, not a verdict.

• "Where'd you see that? I went looking for the original and couldn't find the number."
• "I think the source changes the picture a little. Want to look at it together?"
• "I used to think that too until I read the actual report."

Lead with what's right. If his instinct is sound and his number is off, say so first: "You're right that the cost is going up. The 87,000 piece I'd handle carefully." You're not flattering him. You're being accurate about the whole claim, and he can hear the second half because you were fair about the first.

Send one correction, not five. Pick the point that matters most. A guy who gets buried in rebuttals doesn't update. He retreats.

When he digs in

Some guys will. Say it clearly once, give him the link, and stop. You're not required to win by Sunday. People rarely change their minds in the moment, and often do it quietly a week later when nobody's watching.

But a good friend isn't a doormat either. If he keeps passing along something you've shown him is false, you're allowed to say so plainly, and in the chat if need be: "I checked this and it doesn't hold up, so I'm not going to pass it on." Firm on the claim, warm to the man. Don't call him a name, don't question his character, and don't dig up the last time he was wrong.

There's a difference between a friend who's mistaken and one who doesn't care if he's mistaken. The first is worth patience. The second is worth a boundary.

Be quick to be wrong

This is the part that earns you the right to do any of the rest. When you get it wrong, and you will, say it fast and say it flat. "I had that wrong. Thanks for catching it." No paragraph, no excuse.

Outlets that handle this well tend to be the ones worth trusting, and it's a good standard to hold yourself to (how to tell which outlets actually own their mistakes). The same questions editors ask before a story runs work just as well on a screenshot your buddy sends (the four questions an editor asks). And if the fight is at the dinner table instead of the chat, this piece on keeping it civil covers that ground.

Be the guy people send things to when they want to know if it's true. That takes years of being right, and about two seconds of saying "I was wrong" when you aren't.