What an Argument Actually Is — and Isn't

Two people are shouting at each other across a kitchen table. Their faces are red, the volume is rising, and someone watching might say they are having a heated argument. But listen to the actual sentences and you may notice something strange: nobody is offering a reason for anything. They are expressing displeasure, repeating their positions louder, and accusing each other of being unreasonable. In the technical sense that critical thinking cares about, no argument is taking place at all.

An argument, in this technical sense, is a set of statements in which one or more — the premises — are offered as reasons to accept another — the conclusion. That is the whole structure. A claim by itself is not an argument. A claim repeated three times is not an argument. A claim shouted with confidence is not an argument. The defining move is the offering of support: here is what I want you to believe, and here is why you should believe it.

This sounds obvious, but the consequences are sharp. Consider an explanation. If someone says, "The bread didn't rise because the yeast was dead," they are not arguing that the bread didn't rise — both speakers already accept that. They are explaining why a shared fact occurred. Explanations and arguments share a surface grammar ("because," "since," "therefore"), but they answer different questions. An argument answers "why should I believe this?" An explanation answers "why did this happen?" Mistaking one for the other leads to wasted disputes, where someone tries to refute an explanation as if it were a contested claim.

Description is another impostor. A vivid passage about how a factory closure devastated a town may move you, but description is not argument. It can be material that an argument later draws on, but until someone actually claims something and offers the description as support for that claim, no inference has been made. Reporting also belongs here — a news account telling you what happened is not, by itself, telling you what to conclude from it.

A third lookalike is the assertion cluster: a string of confident claims with no inferential link between them. "The economy is fragile. Inflation hurts working families. We need new leadership." Each sentence is a position. None is offered as a reason for the next. A reader sympathetic to the speaker may supply the missing connections in their own head, but the speaker has not actually argued for anything. They have staked out territory.

Why does this distinction matter for honest thinking? Because the first move in evaluating someone's reasoning — including your own — is locating the argument. If there is no argument, there is nothing to evaluate as reasoning; there may still be a position to consider, an explanation to weigh, or a feeling to acknowledge, but the tools of logical assessment do not apply. And if there is an argument, you cannot fairly assess it without first stating it clearly: what is the conclusion, and what premises are being offered to support it?

This is harder than it looks. Real speech is messy. Premises go unstated because the speaker assumes you share them. Conclusions are buried mid-paragraph or implied rather than declared. Rhetorical questions stand in for assertions. Part of the discipline of argument analysis is reconstructing what someone is actually claiming and what they are offering in support, in a form charitable enough that the speaker would recognize it as their own view.

Notice what this discipline is not. It is not a way to win disputes by catching people in technicalities. It is a way to make sure that when you agree or disagree with someone, you are agreeing or disagreeing with what they actually said, supported in the way they actually supported it. The shouting match at the kitchen table is not an argument in our sense — but if either party paused, named a conclusion, and gave a reason for it, an argument could begin. That is usually when the volume drops.