# A stated reason is a hypothesis rather than a rule

Turning a reviewer's stated reasons into a filter threw out good accounts.

By Ki Moon · 2026-08-31 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/stated-reason-hypothesis/

**Symptom:** An exclusion rule in your target list traces back to one person's explanations of their no's, with no outcome data behind it.

A seller reviewed a batch of our target accounts and disqualified several, with a reason for each. My analysis read the reasons as rules.

More than a third of the no's shared one firmographic attribute, so the analysis turned that attribute into a penalty. A back-test agreed, because it ran on the same verdicts the rule came from.

The filter then removed about twice as many accounts as the seller had rejected, none of them researched.

The reason had the cause wrong. Those no's shared a passing business condition rather than a fixed attribute. The removed accounts were re-screened and recovered.

Now a verdict and its stated reason are separate records. The reason is a hypothesis with a confidence, never a rule.

Until outcomes can test a rule, I don't mine rules. A new candidate shows the 3 most similar past verdicts beside it, and a person judges.

## Check your setup (read-only)

List each exclusion rule in your target-list scoring config. An account with a known opposite verdict is one the rule excludes whose CRM opportunity closed won. It is also one the rule keeps whose opportunity closed lost. Look for a stored test that scores each rule against such accounts. A stored test is a script, its output or a doc. The test must use accounts that weren't used to derive the rule. Any rule with no such test is a gap.

**Passes if:** Every exclusion rule was scored against accounts with a known opposite verdict that weren't used to derive it.

**Access needed:** local-config, crm-read

## If it fails (changes to make later, not part of the check)

1. Store each verdict and its stated reason as separate records.
2. Do not mine rules until outcomes, not opinions, can test the rules. Show the 3 most similar past verdicts beside a new candidate until then.
3. Score the accounts a rule would touch against their recorded verdicts before the rule surfaces.
4. Do not back-test a rule on the verdicts it was derived from.
5. Let rules down-rank with a visible reason, never remove. Let anyone challenge a rule back into review.

**Applies if:** Your scoring config takes reviewer verdicts as input, and fewer than a few hundred accounts carry a verdict.

**Skip if:** Your CRM holds a few hundred or more closed-won and closed-lost opportunities to test rules against.

Tags: data quality, measurement
