You cannot see a colour you have no word for

Years ago I spent forty minutes explaining to a junior engineer why one version of a function was wrong and the other was fine. I drew it. I ran both. He nodded at every step, and at the end he said, honestly and without embarrassment: "they look the same to me."

They did look the same to him. That was not a failure of attention, and it certainly was not a failure of intelligence. He had no category to put the difference in, so his eye slid off it — the way your eye slides off a word in a language you do not read.

I think about that conversation every time someone tells me a training programme "covered" something.

The colour nobody can describe

There is a colour called Olo. It is produced by stimulating a narrow class of retinal cones directly, and it sits outside the range ordinary vision delivers. People who have seen it call it impossibly saturated, then immediately apologise for the description.

The apologies are the interesting part. Everybody reaches for "intense teal" and everybody says, in the same breath, that this is wrong.

Notice what is failing here. It is not precision. A more careful sentence would not help at all. The listener has no bucket to file the thing under, so every analogy lands in the nearest existing bucket and gets quietly bent to fit. The explanation is fine. The receiver is missing the category.

And this is not an exotic edge case about eyeballs. It is the normal condition of anyone learning anything.

Every field is full of Olo

Expertise, in large part, is having categories other people do not have. The expert is not looking harder. They are seeing a different number of things.

Read that middle column again. Every one of those pairs is a thing a beginner can look straight at, twice, and register as one thing.

So when someone says the course "covered" it — covered what, exactly? You can cover a distinction the learner cannot perceive. It happens constantly. The material was correct, the delivery was clear, the quiz was passed, and the category never formed.

You cannot explain a category into existence

This is the part most programmes get wrong, and it is an honest mistake, because explaining is what teaching feels like.

But you do not learn to hear ح versus ه from a paragraph about the pharynx. You learn it from hearing the pair, hundreds of times, guessing, and being told immediately whether you were right. Wine tasters, radiologists, and chess players are all built the same way. The research calls it perceptual learning; in practice it is embarrassingly simple:

1. Show pairs, not examples. One instance teaches nothing. The difference is the object of study, so the pair is the unit.

2. Make them commit before the answer. A guess creates a prediction, and a wrong prediction is what makes the correction stick. Recognition without commitment does nothing.

3. Give feedback in seconds. Not next week's session. The signal has to arrive while the guess is still in working memory.

4. Do hundreds of short reps. Ten minutes a day beats a full-day workshop, and it is not close.

That is not a lecture. It is closer to a drill, and it is unglamorous enough that it rarely survives contact with a training budget — nobody puts "we did 300 flashcards" in the annual report.

It is also the only thing that reliably works.

So here is the practical version. Next time you are building a course, or reviewing one, find the pairs. Ask which two things your learners currently see as one thing. If you cannot name them, you do not yet know what you are teaching — and if you can, you have just found the actual syllabus.

The Olo write-up is here, and it is worth five minutes.