Respond without winning on technicalities

You will be able to answer a fallacy in a way that moves the discussion forward.

Farhan, who you met in Lesson 2.1, "Attacking the person, the straw man and the false choice", is on a video call with six people, an example scenario. A senior colleague dismisses the idea of a four-day week by describing one pilot that failed at a previous company, so one story is standing in for evidence.

Farhan has two obvious options. He can stay quiet and let the idea die, or he can say "that's anecdotal" in front of the group, which would make the call tense and kill the idea anyway. The reply you'll practise here sits between staying silent and calling out the fallacy.

What happens when you name a fallacy

Naming a fallacy feels satisfying, but it almost never changes anyone's mind. The other person hears a public accusation of bad thinking and switches to defending themselves. Everyone else on the call sees a point-scoring contest. Even when you're right, the discussion ends up further from the evidence than it was before you spoke.

Your aim is to bring the group back to the question that matters while the other person is still willing to take part, rather than to win the exchange.

The three moves in every reply

Every reply uses three moves. They build on Lesson 5.3, "Disagree without making it personal", in the course "Communicate at work".

The first move is a fair restatement of the other person's position. This is the straw man test from Lesson 2.1 turned into a habit: checking that the other person would agree with your summary of their position before you answer it. If they wouldn't agree with your summary, you aren't ready to answer. A fair restatement also shows you were listening, and it lowers the temperature immediately. For the four-day week, Farhan's restatement is: the pilot you saw went badly and you think ours would too.

The second move is to accept whatever is true in what they said. This costs you nothing and makes your next sentence easier to hear. The colleague's story is real experience, and something did go wrong at that company.

The third move is a question that redirects the group to the evidence, and the reply ends on that question. A question invites the other person to think with you, while a correction asks them to back down. Two questions that work in many situations are "What would we expect to see if that were true?" and "What would tell us whether it applies here?"

Keep the whole reply to about ten seconds when spoken, or two lines in a chat. Anything longer sounds like a lecture, and people stop listening before they reach your question. Farhan's reply on the call fits inside that limit: "That's useful to know. What went wrong there, and do you think the same thing would happen with our team's workload?"

Farhan's five replies

Farhan took one week to collect five fallacies and write a reply to each. The first was the four-day week story above. The other four were these:

In a chat about hybrid work, someone wrote "So you want everyone working from home forever?" when the proposal was two fixed office days a week. That's a straw man. Farhan replied: "Not quite, I'm suggesting two fixed office days. Which days would matter most for the work you do with the client team?" A manager said "The consultants recommended the new CRM, so let's not reopen it." That's an appeal to authority. Farhan's restatement was that the decision was made with expert input and the manager doesn't want to spend time on it again. His reply: "Fair. Did their recommendation look at teams our size? If so, I'm happy to go with it." Someone said of the year-end event, "Either we do the full dinner or we cancel." That's a false dilemma. Farhan replied: "Both are options. Is there something in between, like a lunch, that would fit the budget?" Farhan's own team said "We've spent too much on the rewards feature to stop now." That's sunk cost. He replied: "I get that it's been a big effort. If we were starting today with the test results we have, would we fund three more months?"

None of the five replies names a fallacy. Each one accepts something, every one ends on a question pointing to evidence or options, and several show that Farhan understood the other view before answering it.

Deciding when to reply, and how it will sound

Not every fallacy needs a reply. Leave it if the stakes are low, if the comment is a joke, or if the person is clearly venting. In a large meeting it's sometimes better to follow up one to one afterwards. Save the effort for when a fallacy is steering a real decision.

Tone matters as much as wording. A reply can be technically fair and still read as point-scoring, and a sentence that's fine face to face can feel cold in a chat. Lesson 2.3 of "Communicate at work", "Why your message sounded ruder than you meant", covers how tone, especially in chat, makes fair replies read this way.

Collecting and answering your own five

Collect five fallacies from real discussions: meetings, work chats, family group chats or comment sections. Aim for a mix of the types in this module, which are ad hominem, straw man, false dilemma, appeal to authority or popularity, slippery slope, sunk cost and post hoc.

For each one, write four things in a row. First, the original line; if it came from a private chat, use a close paraphrase instead of copying it. Second, the name of the fallacy, which goes in your own notes only and never in the reply. Third, a one-sentence fair restatement of the other person's view. Fourth, your reply, ending with a question about evidence.

Then read each reply aloud. If it sounds sarcastic, defensive or like a lecture, rewrite it. A reply is ready when it would make sense to someone who has never heard of fallacies.

Your five examples are probably already in your chats from the past week. In the activity below you will gather them and write a calm one-line reply for each.

Take five fallacies from real discussions and write a calm one-line reply to each. End every reply with a question about the evidence.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).