Burden Reversal

One-liner: Disguised as a clarifying question, it forces the critic to prove the problem exists.

Also known as / related terms: Burden-of-proof shifting, “prove it” gaslighting, evidentiary reversal, sealioning (adjacent).

What it is

Suddenly you’re the one on trial.

Normally the person who took an action or made a claim carries the burden of justifying it. Burden Reversal inverts that. The person being questioned answers with an ostensibly reasonable clarifying request that in practice shifts the entire evidentiary burden onto the person raising the concern, and does it in front of others, framing the critic as vague, unprepared, or unreasonable if they cannot immediately produce a fully formed case.

The move hijacks a real conversational obligation. Philosopher H. P. Grice’s cooperative principle (“Logic and Conversation,” 1975) describes a normal expectation built into conversation itself: when someone asks a direct question, refusing to answer reads as uncooperative, even rude. Burden Reversal exploits exactly that obligation. The question sounds like ordinary due diligence, so declining to answer it on the spot feels like a social violation, even when the question is actually an unreasonable demand dressed up as one. Psychological literature on gaslighting identifies burden-of-proof reversal as one of its strongest levers for this reason: once the person raising the concern becomes the one who has to explain and defend, the frame has already shifted in the other person’s favor, regardless of what is eventually proven.

What it looks like (workplace)

In a team meeting, in front of the wider group, someone raises: “I think the way this metric was reported to the client was misleading.” The reply comes back immediately, calm and unhurried: “Okay. Which number, which sentence, which call, and what’s your basis for ‘misleading’? Because from where I’m sitting, you’re making a serious accusation with nothing behind it.” The person who came with a concern is now the one being cross-examined, in front of the same team, for having raised it at all.

How it actually unfolds when confronted

1. Confrontation. A reasonable but not-yet-exhaustive concern is raised, the way real first-pass concerns actually arrive, a pattern noticed, not yet a fully documented case.
2. The reversal. “Can you show me exactly which number, which sentence, and why?” arrives in the tone of fair-minded rigor. The roles silently swap: the person who raised the concern is now the one being examined. This is Position Inversion executed through a single question.
3. The moving standard. Each piece of evidence the confronter produces is met with a narrower demand, a named pattern in its own right, Moving the Goalposts. The escalating-specificity loop this creates is structurally the same move Wikipedia’s entry on sealioning describes: persistent, ostensibly civil demands for proof, used to exhaust and delegitimize rather than to actually engage. Each round costs the confronter more time and standing than the last.
4. Outcome. The issue gets tabled “until you have something concrete.” If the confronter does the work and comes back with a full dossier, the greeting is rarely engagement: it’s Premature Finality Framing (“we’ve moved on from that”) or “Just Sentiment” Reframing (“you’ve been pretty fixated on this, haven’t you”).

Why they do it

Making the critic do the evidentiary work stalls the conversation and exhausts them. It also recasts a legitimate concern as an unfounded accusation, and it works because refusing to answer a direct question, even an unreasonable one, violates the basic cooperative expectation Grice described, which is exactly the discomfort this tactic is built to trigger in the confronter, not in the person asking.

How to protect yourself

Your concern stands even before you’ve built the full case.

• Don’t accept the reversed burden on the spot. Name it: “I’ll get you specifics, but the concern stands regardless, let’s not make this only about my documentation.”
• Put the original concern in writing before the conversation, so it can’t be characterized as vague after the fact.
• Ask a bounded, fair question back: “What would you consider sufficient evidence, and by when can I follow up?”, this keeps the process visible rather than open-ended and makes stage 3’s moving standard harder to disguise.
• Recognize repeated demands for escalating specificity as a stalling pattern, not a good-faith request, the same discipline described in JADE-avoidance: you don’t have to justify, argue, defend, or explain past the point where the demand has stopped being about the facts.

Cross-links: Position Inversion (the who-is-on-trial swap this move executes); Moving the Goalposts (the escalating-specificity loop in stage 3); Displacement of Action (the sibling move that reverses the burden of proposing a solution instead of the burden of proof); JADE-avoidance (the defense discipline that resists the loop); Gaslighting (the ambient self-doubt this tactic feeds).

Sources:

Label note: Descriptive-original coining. The underlying mechanism draws on Grice’s cooperative principle and a well-documented feature of gaslighting dynamics (burden-of-proof reversal), and shares structure with sealioning.