Chatbots Tips for Preschoolers

1. Anchor to a chatbots example they already use. The help widget on a shop website answering delivery questions is a better opening than any definition, because the learner has already seen the behaviour and only needs a name for it. 2. Demonstrate before defining — at this age that means a physical activity, since no chatbots tool is usable yet. 3. Introduce exactly one concept per session; for chatbots at ages 3–5 that means sorting and matching, nothing more abstract.

4. Kill the standard misconception early. Most people assume that a chatbot that says it is happy to help, or says it likes you, means anything by it, and chatbots is unusually prone to it. In fact it produced the words most likely to follow. There is nothing behind them — which matters enormously as children start using bots that are deliberately designed to feel like company. 5. Make it fail on purpose — with chatbots the failures are more instructive than the successes, because they show the boundary of what the examples covered. 6. Keep a log of what broke it; over a few sessions that log becomes a genuine picture of how chatbots behaves.

7. Connect it forward when the learner is ready. Conversation design is a real and growing job — deciding what a system should say, what it should refuse, and what it does when it does not know. That framing matters more than it looks: it moves chatbots from a novelty to something with a use, which is what makes a learner come back to it a third and fourth time.

Preschoolers are at the point where they can articulate a rule they have just noticed, which is exactly what makes this age band different from toddlers. They can watch a drawing game guess what they are drawing, and they can tell you it got it wrong. That single exchange — machine guesses, guess is wrong, child notices — is the whole foundation.

What they cannot yet do is connect the guess to anything the machine learned. Training data is not a concept that lands at four. So resist explaining where the guess came from; the goal is only that a machine guessing is normal, and that a confident guess can still be wrong.

Say "guessed". Avoid "knew", "understood", "thought", "decided" and "recognised" — every one of them implies an inner life the system does not have, and a learner who picks up that framing has to unlearn it later. "The computer guessed dog, and it was wrong" is accurate and needs no correction at any later age.

Avoid the brain analogy entirely, even though it is everywhere. Most people assume that a chatbot that says it is happy to help, or says it likes you, means anything by it; in fact it produced the words most likely to follow. There is nothing behind them — which matters enormously as children start using bots that are deliberately designed to feel like company. At ages 3–5, with a reading level of pre-reading to early letter recognition, the brain comparison does not simplify anything — it substitutes one thing the learner cannot picture for another, and it plants a misconception you will have to remove.

Name the examples. "It has seen a lot of pictures of dogs" is concrete and true, and it quietly introduces training data without the term. When the learner is ready for the term, it attaches to something they have already pictured.

The model keeps getting it right and the learner is bored. This is a good problem: the activity has no tension left. With chatbots the fix is to change the test rather than the tool — feed it something the examples never covered and watch the confidence stay high while the answer goes wrong. Boredom here almost always means the difficulty is too low, not that chatbots is the wrong topic.

The model keeps getting it wrong and the learner is frustrated. Stop and separate the two questions: is it failing because the examples were too few, or because the test is unreasonable? Say the distinction out loud. Frustration turns into interest the moment a learner believes the failure is diagnosable rather than random.

Attention drops before you finish. At ages 3–5 the realistic ceiling is about 10 minutes, and pushing past it converts learning into clicking. Stop at a point where something works, and leave the extension for next time — an unfinished activity someone wants to return to beats a finished one nobody does.

The learner asks a chatbots question you cannot answer — and with chatbots they will, because the honest answers involve statistics and scale. Say so, and find out together. This is the single highest-value moment available: modelling "I do not know, let us check" against a system that never says it is unsure teaches more than the activity was going to.