Question
Why does falsification fail?
Quick Answer
Performing a half-hearted search for disconfirming evidence, finding nothing convincing, and using that failure as additional confirmation. This is the most common way people co-opt this practice: 'I looked for reasons I was wrong and couldn't find any — so I must be even more right.' The test is.
The most common reason falsification fails: Performing a half-hearted search for disconfirming evidence, finding nothing convincing, and using that failure as additional confirmation. This is the most common way people co-opt this practice: 'I looked for reasons I was wrong and couldn't find any — so I must be even more right.' The test is whether your search could actually have changed your mind. If the answer is no, you did not seek disconfirmation. You performed a ritual.
The fix: Pick one belief you currently hold with high confidence — about your work, your skills, your team, or your market. Write it as a clear statement. Now spend 15 minutes searching exclusively for evidence that would prove it wrong. Talk to someone who disagrees with you, read the strongest critique, or look at data you have been avoiding. Write down what you find. If you cannot find any disconfirming evidence after a genuine search, your belief is either well-calibrated or unfalsifiable — and you should know which.
The underlying principle is straightforward: Actively looking for evidence against your current belief is the fastest path to calibration.
Learn more in these lessons
- Seek disconfirming evidence
Actively looking for evidence against your current belief is the fastest path to calibration.
Go beyond the answer
This topic is part of The Staff Engineer’s Thinking Infrastructure — a guided sequence of 20 lessons.
After completing this path you will be able to consciously choose your level of abstraction, build shared mental models across teams through ADRs and RFCs, make architecture decisions that persist beyond your involvement, structure your own time in an undefined role, and manage the invisible emotional load of technical leadership.
Start the path →