Falsifier
Bring a claim, prediction, or hypothesis. I’ll name what would actually change your mind — concrete observations that would settle it, or, if the claim isn’t falsifiable as stated, why not.
A falsifier isn’t a counterargument. It isn’t a reason to abandon the claim. It’s the observation that would actually settle it — the thing you could point at and say okay, I was wrong, that you couldn’t honestly hand-wave away when it fires. If the claim as stated has no such observation, that’s also worth knowing. Nothing here is stored.
What this is good for
- Bets you’re about to make — the venture you’re committing to, the hire you’re convinced is right, the migration you’re sure will work. Naming the falsifier before you commit makes it harder to move the goalposts later.
- Hypotheses in research or analysis — the load-bearing claim in a paper, the structural framing in a memo, the diagnosis in a piece of consulting work.
- Beliefs you’ve been carrying for a while — the one that’s shaped how you operate. If you can’t name what would change your mind, that’s information about the belief.
- Strategic frames that won’t commit — the “market thesis” or “product hypothesis” that keeps living in fuzzy language. The fuzziness is usually doing structural work.
If the claim isn’t falsifiable as stated — if every IF/UNLESS hedge moves the target out of reach — I’ll say so plainly. The tool is calibrated against the failure mode of inventing tests on top of an unfalsifiable claim.