Why "just one bite" backfires
Every parent arrives at "just one bite" honestly. The plate is full, the child is not eating, dinner is going cold, and one bite seems like the smallest thing in the world to ask for. It is a reasonable request. It is also the one most likely to make tomorrow harder.
What the child hears
A bite is a commitment. Once it is in, it cannot be taken back — not the taste, not the texture, not the moment of discovering that it is worse than it looked. For a child who is already wary of a food, that is the whole problem in one mouthful.
So the request lands as something bigger than it sounds. Not "try this", but "agree, now, to the part you are most afraid of". And because it is asked at the table, in front of everyone, with the meal on hold, the answer becomes a performance rather than a preference.
What it teaches
The bite usually happens. Most children, most nights, will take it to end the conversation. What they learn is not that broccoli is fine. What they learn is that broccoli is the thing that starts arguments.
The food picks up a second meaning it did not have before. It is no longer just a green vegetable with an odd smell; it is the moment the table went quiet. Next week that meaning arrives before the plate does.
There is a smaller cost too, and it lasts longer. If the only outcome that counts is eating, then everything the child actually did — sitting near it, touching it, licking it, putting it down again — counted as nothing. A child who gets nothing for four honest attempts stops making them.
What works instead
Repetition without stakes. A food that shows up regularly, is allowed to be refused, and costs nothing to refuse, stops being a question. Somewhere in that run of no-pressure meetings, on a day nobody planned, it gets eaten.
This is slower than one bite. It is also the version that holds: nothing was won by pressure, so nothing collapses when the pressure stops.
What helps in the meantime is counting the smaller steps out loud. Not as a trick — children see through encouragement that is really instruction — but because those steps are genuinely the road. Sitting at the same table as a new food is progress from the week the child left the room.
What this has to do with us
Taste a Day is built around exactly this. It never asks whether your child ate it; it asks how close they got, and it records that as a win. Five steps, and the first one is being in the same room.
That is a design decision, not a claim about outcomes. Repetition without pressure is well described in the feeding literature, and this is a game built on it — not a treatment, and not a promise that it will work for your child.
If eating is affecting your child's health or growth, that is a conversation for a paediatrician, not an app.