Tell when a claim states its limits, and explain why that should raise your trust in it.
Marcus tells a director that the new onboarding video will cut support calls, and says nothing more. In the same week Aisha presents to the same director (both are invented examples). She says the video will probably cut calls about account setup, that billing questions are unlikely to change much, and that the team should drop it if call volumes have not fallen within two months.
Marcus sounds more certain, yet most people in the room trust Aisha more without being able to say why. The reason lies in two parts of Stephen Toulmin's model of argument. Lesson 1.1, "Claim, evidence and the link nobody says out loud", used three of its parts: claim, evidence and warrant. Toulmin added a few more, and two of them, the qualifier and the rebuttal, change how much you should trust a claim.
A qualifier is the word or phrase that says how strongly a claim is meant: "probably", "in most cases", "for customers on the basic plan", "usually within a week". Toulmin counted it as part of the argument because the same evidence can support a strong claim or only a modest one, and the qualifier tells you which one the speaker is making. A good qualifier narrows a claim to what the evidence can support.
Aisha's qualifiers are "probably" and "about account setup". Her evidence was perhaps last quarter's support tickets, showing that setup questions were the largest group and the kind a video could answer. That evidence fits her narrow claim. It would not support "the video will cut all support calls", and she never says so.
Marcus gives no qualifier, which leaves two possibilities. His evidence may be strong enough to need no limit, which is rare for a prediction about customer behaviour, or he may not have thought about where his claim stops being true.
In Toulmin's sense, a rebuttal is the speaker's own statement of the conditions under which the claim would fail. It does not mean someone else attacking the argument.
Aisha offers two. Billing questions are unlikely to change, and if calls have not fallen in two months, the idea has not worked. The second states a failure condition, so her claim is testable and anyone can check later whether it held. A speaker who invites checking in this way suggests they have done their homework.
A rebuttal can also show that the speaker has considered other explanations, meaning other factors that might move the numbers. Aisha could have added "unless the price change in March drives a spike in billing calls that swamps the setup savings". That would tell the director she knows the video is not the only thing affecting call figures. Module 4 shows how often a second factor explains a pattern people credit to the first.
Many people read an unqualified claim as the stronger one, because it sounds more decisive and confident speakers often get more airtime at work. Almost nothing at work holds in every case, though. Customers differ, markets shift, and projects hit problems nobody planned for. When a claim admits no exceptions, the speaker has usually not looked for any.
When you hear a claim, check first for a qualifier. If there isn't one, ask whether the evidence really needs no limit or whether the speaker hasn't considered where the claim stops being true. Then check for a rebuttal, the speaker's own condition for failure.
In a meeting, one question does most of the work: "Is there any situation where that would not be true?" Someone who has thought it through will answer quickly. Someone who hasn't may hesitate and then find a limit, which is useful too. In both cases the claim gets more precise and the room learns how much to rely on it.
Reading works the same way. A vendor deck promising results "for every business", or a forwarded message saying a supplement "works for everyone", tells you something about the writer. The stronger the wording, the more you should ask what has been left out.
Suppose you want to replace your team's weekly status meeting with a shared written update. The weak version is "Written updates will save everyone time." A stronger version names who benefits, by how much, and what result would make you give up: for the six of us, a written update would probably save about thirty minutes each a week, mainly for people whose work does not depend on the others; the thirty minutes is an estimate; and if after a month people still message each other for the same information, we bring the meeting back.
If a colleague then objects that the meeting is where dependencies get sorted out, you have nothing to take back, since your claim already limited the saving to people without dependencies. Objections that your qualifier already covers do not force a retreat, so qualified claims are easier to defend. Your manager also gets a clear way to judge the trial, which makes approval easier to give.
When you build a claim of your own, go through these steps:
Narrow it with a qualifier to what your evidence supports: the scope, the likelihood, or who it applies to. Say when a number is an estimate, since that is part of qualifying the claim. Add a rebuttal naming a result that would show you were wrong, with a timeframe if you can. Check that you haven't hedged so far that the claim can never be wrong.
The last step guards against a common trap. Qualifiers are there to show the real limits of your evidence, and piling them up so that you can never be pinned down is a misuse. "This might possibly help in some cases" can never be wrong, so nobody learns anything from it. Aim for a qualifier that narrows the claim to what you can support and a rebuttal that names a result that would show you were wrong.
For now, words such as "probably", "likely" and "in most cases" are enough. Lesson 7.1, "Decisions are bets", takes the next step and asks you to put a number on how sure you are.
Look back at the last week of your messages and meetings. Find two places where you stated something as simply true, perhaps a forecast for a project, a view on why a client went quiet, or a reason a process is slow. In the activity below you will rewrite each one with an honest qualifier and a condition that would prove it wrong.
Take two claims you made at work recently. Rewrite each one with a qualifier and a condition under which it would be wrong.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).