You favor a plan. Evidence for it appears everywhere. Counterpoints feel like noise. Confirmation feels like clarity until a cheap test would have killed the idea in fifteen minutes. Nobody ran it because the room already liked the story.
Argue the opposite case for five minutes. Not forever. One timed brief that tries to kill your current claim. That short attack turns fog into a move you can finish inside a focus block and record without drama.
Freeze the claim before you attack it
Write one sentence: I think X is true because Y. If you cannot write it, you are still exploring, not deciding. Exploration needs a wider notebook. Attack needs a claim you are willing to risk on the page in front of a teammate.
When the claim keeps morphing, you are in a decision loop. Put a timebox around naming the claim using the exit habits in timebox looping decisions so choices stop spinning. Freeze the wording when the timer ends. Refuse new adjectives.
Spend five minutes as the critic
Set five minutes. Write only reasons the claim fails: missing data, rival explanations, cost of being wrong. Do not polish the original plan in this window. The critic needs airtime without the author interrupting with rescue narratives.
If unfinished notes threaten the next switch, park unfinished sentences before switches so the critic brief survives the break. It should still make sense tomorrow morning without rereading a foggy half draft.
Turn the strongest attack into one test
Pick the attack that would hurt most if true. Design one cheap falsifier under fifteen minutes. That pairs with how you split a stuck hard problem into one next cheap test. The opposite brief feeds the test queue instead of feeding more theory slides.
Record pass, fail, or unclear. Unclear means the test was poorly designed, not that you need more philosophy. Redesign once, then run again before you open a third theory draft.
Keep working memory free for the brief
Close unrelated drafts. Shed load so the critic has room. Habits from shed working-memory load before you start work apply here. A crowded pad makes every counterpoint feel optional and easy to dismiss.
After meetings, clear residue before you claim you are arguing fairly. Residue makes every attack feel muddy, which is why people clear attention residue after meetings on purpose before returning to hard choices that need clean judgment.
Chain briefs instead of defending pride
When a test fails, write the next claim from the failure, not from pride. When it passes, widen the next opposite brief slightly. Chains beat master plans when uncertainty is high and stakeholders want theater instead of evidence on the page.
Review weekly which choices locked without a single opposite brief. Those are process failures, not intelligence failures. Require five minutes of attack before another hour of confirmation hunting that feels like work.
FAQ
How long should the opposite brief last?
Five minutes is enough to surface the strongest attack. Longer briefs invite polishing the original plan.
What do I write first?
One sentence claim you would defend today. Freeze it before the critic window starts.
What if I cannot find a counterargument?
That usually means the claim is vague. Narrow it until an attack becomes possible.
Should I share the brief with others?
Yes when stakes are high. A second person often finds the cheap falsifier faster.
How does this relate to next tests?
The strongest attack should become one cheap falsifier you can run the same day.
What if the attack fails?
Record that the claim survived this attack, then choose the next stronger attack or lock the choice.
