Where tonight sits
Five sessions have each taken one way a number can be true and still fail to support the decision it is carrying. A score that depends on an arrangement. A pipeline that could have returned a different model with the same score. A set that started choosing instead of measuring. A benchmark that measured somebody else's task. A body of published evidence with a known flaw running through it. Tonight collapses all five into the last question in a review, and into the one line that makes the answer checkable later.
★ What you walk out with tonight. Five questions you can ask in any model review, each with the specific answer that would settle it. The four parts a falsifier needs before it can ever fire: a named metric, a named population, a threshold and a date. And one written sentence for the next model you approve, with an owner against it.
LiveA claim with no falsifier is not a weak claim4 min▶
"The model performs well" survives every observation. So does "it may degrade over time", and so does "we will keep an eye on it". Nothing that could happen next quarter is inconsistent with any of them, which means none of them is doing work. A claim with no falsifier is not a weak claim; it is not a claim, because there is no state of the world it rules out.
The repair is small and it is entirely a matter of when. Written after the drop, a threshold is a negotiation about whether the drop counts. Written at approval, the same threshold is an agreement, and the only thing left to do in March is read a number. The sentence costs a minute in the meeting where everyone is calm and saves the argument in the meeting where nobody is.
Thornbury approved on 0.949 held out. The ward agreed with the outcome about 90 percent of the time in the collection year and about 50 percent after the reorganisation, and the same model scored 0.765. Every ingredient of the falsifier existed at approval: the metric was already being computed, the population was already defined, and the reorganisation was already on a project plan somewhere in the group.
Self-studyWhere practitioners disagree about falsifiers4 min▶
One camp treats the falsifier as a logical test: the observation arrives, the claim is refuted, the model comes out. The other camp points out that no single observation ever refutes a model claim on its own, because a bad number can always be attributed to the sample, the threshold, an implementation change or an unusual month. On that reading a falsifier is not a test at all; it is a commitment device, useful because it removes the option of choosing the explanation after seeing the number.
The disagreement is real and it is not settled. What both sides accept is the part that matters for a review: the threshold has to be written before the data arrives, because whoever writes it afterwards is choosing the verdict. Pick whichever justification you find convincing and write the same sentence.
Self-studyThe vocabulary the five sessions leave behind3 min▶
- Warrant. The reason a claim is believable. A score plus the assumptions that let it travel.
- Underspecification. A pipeline that can return many models with equally strong held-out performance which behave differently in deployment. Session 2.
- Optimism. The gap between a number reported after selecting on a set and the same model's score on data nobody selected on. Session 3.
- Construct validity. Whether an instrument reads the quantity you care about. Session 4.
- Leakage. Information about the outcome reaching the inputs. Session 5, at the scale of a literature.
- Falsifier. The observation that would end the claim, named in advance with a metric, a population, a threshold and a date.
Five sessions, five questions, five answers that would settle them
13 min liveEach earlier session ends in a question an approver can ask out loud in under ten seconds. What makes the question useful is not the question, it is having decided in advance which answer would move you. Asking without that is a conversation; asking with it is a control.
LiveTwo of the five answers are almost free4 min▶
The seed question costs three retrains. At Thornbury, twenty models that differed only in their random seed sat within a held-out spread of 0.003 to 0.019 depending on the data draw, and pulled apart by 0.034 to 0.051 once the wards moved: the shifted spread ran 2.7 to 11.3 times the held-out spread, in five draws out of five. Three retrains will not reproduce that whole picture, and they do not need to. They tell you whether the number in front of you identifies one model or a family.
The fresh-set question costs one scoring run. The measured optimism at Thornbury from selecting the best of a hundred candidates was 0.0072, and the same model's accuracy on data nobody selected on barely moved between one candidate and a hundred: 0.9500 down to 0.9497. That is small, and the point of asking is not to catch a scandal. It is that the answer takes an afternoon, so an unanswered version of it is a choice rather than a constraint.
LiveThe two questions where the honest answer is "we cannot"4 min▶
A published rank and a published paper both sit outside your control. You cannot rerun somebody else's benchmark on your population, and you cannot re-split their data. When the answer that would change your mind is unobtainable, the finding is not that the evidence is bad; the finding is how much weight it can carry, which is less than a number of its size suggests.
What you can do is bound the exposure. Kapoor and Narayanan found leakage in 17 fields, collectively affecting 294 papers, with a taxonomy of eight types. That base rate is an argument for asking how much of a decision rests on evidence nobody in the room produced, and for funding the one cheap replication that would move the answer, rather than for discounting the literature wholesale.
A vendor slide shows a first-place rank. The answer that would change your mind is the same model scored on 500 of your own patients, with your outcome definition and your threshold. If the vendor can run that, the rank stops mattering because you have the number you actually needed. If they cannot, you have learned the price of the rank.
A falsifier that can actually fire
9 min liveMost written falsifiers are gestures. They name a direction instead of a number, a feeling instead of a population, and no date at all, so no observation ever contradicts them and nothing ever triggers. Four parts fix that, and all four are usually already known at approval.
LiveWhere the threshold comes from4 min▶
The most common objection to writing a number is that nobody knows the right one. That is true and it is not a reason to leave it out, because a threshold is a statement about what the organisation would do, not an estimate of anything. It sits between the score that justified approval and the score at which the model is doing harm, and both ends of that range are usually known or arguable in the room.
At Thornbury the approved figure was 0.949 and the post-reorganisation figure turned out to be 0.765. A threshold anywhere in between converts the fall into a scheduled decision rather than a discovery. Picking it badly is recoverable; the sentence can be rewritten at the next review with the reason for the change recorded. Picking nothing is what leaves the question open for eighteen months.
Self-studyTwo failure modes of a written falsifier3 min▶
Set so low it never fires. A threshold chosen to be safe from embarrassment is a threshold chosen to be inert. The test is simple: ask what the metric would have to read for the sentence to trigger, then ask whether the model would still be usable at that level. If the honest answer is no, the sentence is protecting the approval rather than the patients.
Attached to a metric nobody computes. A falsifier written against a quantity that requires a special study will not be evaluated, whatever the note says. Pick something already on a dashboard or already produced monthly, even if it is a rougher measure, because a rough check that happens beats a precise check that does not.
Write one, for a model you are about to approve
20 min build-alongNo laptop. Pick a model your area is about to approve or renew, and produce one sentence with four parts and a name against it. The measure of success is that somebody who was not in the room could run the check without asking you what you meant.
Name the model and the number on the slide. The figure, the data it was computed on, and when that data was collected. Everything that follows hangs off this sentence, so say it out loud before anybody improves it.
Pick the metric that already exists. Not the best measure of value, the best measure somebody is already computing monthly. Write its name exactly as it appears wherever it is produced.
Name the population, including its time window. "Patients on the reorganised wards, admitted in the quarter" is a population. "Our users" is not, because two people will compute it differently and both will be right.
Choose the threshold out loud, and record the reasoning. Put it between the score that justified approval and the score at which you would not deploy at all. Somebody will disagree; that argument is the useful part and it is much cheaper now than in March.
Set two dates, not one. A calendar date so the check happens on a quiet quarter, and an event trigger for the arrangement most likely to move: a reorganisation, a supplier change, a new intake form, a policy.
Put a name against it and say the consequence. Who runs the check, and what happens if it trips: withdrawn, reduced to advisory, or rescored within a stated number of days. A trigger with no stated consequence becomes a discussion.
Read it back to somebody who was not involved. If they can tell you what would make the claim false and when they would find out, the sentence is finished. If they ask what you meant, it is a draft.
The one-sentence version to take into an approval. "If [metric] on [population] is below [number] at [date], or on the day [named change] happens, [person] pulls the model into review and it comes out of [use] until it is rescored." Everything in the five sessions is an argument for why that sentence is worth the minute it costs.
Three questions
An approval note says "we will monitor the model and revisit if performance degrades materially". What is wrong with it?
The sentence is compatible with every future, including the one where accuracy falls by two tenths and everybody explains it. Monitoring is not the missing part; the missing part is the number that decides whether what is being monitored counts as degradation.
A team objects that they cannot write a threshold because nobody knows what level would be unacceptable. What is the best response?
A threshold is a statement about what the organisation would do, not an estimate of a quantity, so there is no study that could produce it. Waiting for certainty leaves the decision to whoever is in the room after the number falls, which is the situation the sentence exists to prevent.
A vendor rank is the main evidence for a purchase, and the vendor will not score their model on your data. What has the review learned?
A rank is a claim about a task, a distribution and a scoring rule that are not yours, and refusing the replication does not make it false. It makes it unfalsifiable from where you sit, which is a fact about how much of the decision it can support, not a verdict on the vendor.
After the leader track
30 minTake the sentence you wrote tonight to the team that owns the model and get two things added: a name and a date in whatever system already holds their recurring work. Then look back through the last four approvals your area signed and count how many carry a condition somebody could run. The count is usually zero, and it is the most useful number you will bring to your next governance meeting. Anyone continuing into the practitioner track can run both Thornbury benches themselves from session 1 onwards.