Changes

== Handling Counterarguments ==

== Handling Counterarguments ==

A structured argument that only builds the affirmative case is vulnerable to the strongest objection the reader can think of but the writer never addressed. Legal briefs, academic papers, and apologetics all typically require the writer to anticipate opposing points and answer them directly rather than ignore them, since an unaddressed objection can undermine an otherwise well-organized argument in the reader's mind even when every stated reason is sound.

A structured argument that only builds the affirmative case is vulnerable to the strongest objection the reader can think of but the writer never addressed. Legal briefs, academic papers, and apologetics all typically require the writer to anticipate opposing points and answer them directly rather than ignore them, since an unaddressed objection can undermine an otherwise well-organized argument in the reader's mind even when every stated reason is sound.

A common approach is to state the strongest form of the opposing argument (sometimes called "steelmanning," in contrast to a weaker "strawman" version), then show specifically why it fails or why the main claim survives it. This can be done reason-by-reason, addressing objections as they arise within the flow of the argument, or gathered into a dedicated section near the end, after the affirmative case has been fully built. Writers should generally avoid citing the mere existence of disagreement as though it were itself an objection; a structured response engages with the substance of the opposing reasoning, not just its presence.

A common approach is to state the strongest form of the opposing argument (sometimes called "steelmanning," in contrast to a weaker "[[Straw man fallacy|strawman]]" version), then show specifically why it fails or why the main claim survives it. This can be done reason-by-reason, addressing objections as they arise within the flow of the argument, or gathered into a dedicated section near the end, after the affirmative case has been fully built. Writers should generally avoid citing the mere existence of disagreement as though it were itself an objection; a structured response engages with the substance of the opposing reasoning, not just its presence.

Failing to address counterarguments is a distinct weakness from the [[#Common Pitfalls|pitfalls]] described above: a piece can have valid, well-evidenced reasoning for its own claim and still fail to persuade a critical reader if it never engages with the best case against it.

Failing to address counterarguments is a distinct weakness from the [[#Common Pitfalls|pitfalls]] described above: a piece can have valid, well-evidenced reasoning for its own claim and still fail to persuade a critical reader if it never engages with the best case against it.

== Deductive vs. Cumulative Structures ==

== Deductive vs. Cumulative Structures ==

''See also:'' [[Inductive reasoning]] and [[Principle of induction]] and [[Deduction]] and [[Deductive reasoning]] and [[Fallacy of exclusion]]

''See also:'' [[Inductive reasoning]] and [[Principle of induction]] and [[Deduction]] and [[Deductive reasoning]]  

Structured logic writing can follow either a [[Deduction|deductive]] or a cumulative ([[Inductive reasoning|inductive]]) structure, and the two make different kinds of promises to the reader.

Structured logic writing can follow either a [[Deduction|deductive]] or a cumulative ([[Inductive reasoning|inductive]]) structure, and the two make different kinds of promises to the reader.