THE INTEL ANALYST ACADEMY
Professional Intelligence Training
Printable Lesson
Key Assumptions Check Testing What Your Judgment Rests On
The Intel Analyst Academy · Lesson Notes
By the end of this lesson you will be able to run a Key Assumptions Check on a draft assessment. You will list what you are taking for granted, test each item, and change your wording, confidence level or collection requests where the test fails. One analyst, one colleague and a whiteboard are enough.
This matters because assessments rarely fail on the facts. They fail on the unstated bridge between the facts and the judgment. A customer will not challenge a bridge nobody told them was there, and by the time they find it, it is usually in a meeting you are not invited to.
An assumption is something you believe about the world, an actor, a source or a method that you have not verified, and that your reasoning depends on. It differs from three neighbours:
An assumption is "key" if, when it turns out false, your key judgment would change materially or your confidence in it would drop. "The suspect uses a phone" is an assumption. It is rarely key. "The suspect will keep using the same supplier" may hold up an entire forecast.
Key assumptions tend to fall into five groups:
The best time is before you finalise a key judgment, while changing the wording still costs nothing. It is also worth running in these situations:
The check pairs well with other techniques. It tests the premises that sit under every hypothesis, while Analysis of Competing Hypotheses tests the hypotheses against the evidence. The Cognitive Biases in Intelligence lesson explains why you skip this step when you are busy and confident, which is exactly when you should do it.
Step 1: Write the draft judgment in one sentence. Include the confidence level you currently intend to use. If you cannot state it in one sentence, you are not ready for this exercise yet.
Step 2: Ask what must be true for this to be right. Work backwards through your reasoning and list everything. Include the dull items. Aim for eight to fifteen candidates. Do this with someone who has not worked on the project, because they will ask about things you stopped seeing weeks ago.
Step 3: Select the key ones. For each candidate, ask whether the judgment would change if it were false. Keep those that pass. Discard the rest without guilt.
Step 4: Challenge each key assumption. Ask:
Step 5: Rate each one.
Step 6: Act on the rating. Supported assumptions get stated in the product. Caveated ones get their conditions written into the text. Unsupported ones need a decision: collect evidence, reduce confidence, reword the judgment, or remove the dependency.
Step 7: Record it. Keep the list, the ratings and the reasons. Add indicators that would tell you an assumption has failed, and review them on a schedule. The Indicators and Warnings lesson covers how to build those.
This is an illustration. Maya is a financial crime analyst at a bank. Her draft reads: "We assess with high confidence that the accounts opened last month are a single money mule network run by one organiser." Her evidence is a shared device identifier across the accounts, onboarding times that cluster closely, and funds that arrive and leave within hours.
Maya and her colleague Tom list what must be true:
They test the key items, which are the first, second and fifth.
On the first, a device identifier can be shared by a household, a shared workplace terminal or a public computer. The assumption is caveated. Maya can check whether the same identifier also appears on unrelated, long-standing accounts. If it does, the link is weaker.
On the second, nobody has checked whether the bank ran a sign-up promotion that month. Tom asks the marketing team. One did run. This explains the timing for part of the cluster, so onboarding time stops counting as evidence of coordination. The assumption was unsupported.
On the fifth, the device data comes from one channel only, so Maya states that limitation in the product and files a collection request for the other channels.
The revised judgment: "We assess with moderate confidence that a subset of the accounts is linked through shared device use and rapid fund movement. Timing alone does not indicate coordination." The product lists the three key assumptions with their ratings, and it names an indicator that would raise confidence: repeated identical transfer patterns across accounts that share no promotion.
The customer here may freeze accounts or file reports. A wrongly labelled customer is a real cost, which is why the check sits comfortably inside proportionality as well as tradecraft.
Pick an assessment you wrote or inherited, ideally one with a forecast in it. Old products are fine, and checking one that has since been overtaken by events is instructive.
Keep the one-page record. Next time you are asked how sure you are, you will have an answer that includes what you checked.
Continue your training
This lesson is part of The Intel Analyst Academy — professional intelligence analysis training built for analysts. Explore the full course library, structured learning paths, and practical tools at theintelanalystacademy.com.