The new step that never sticks

You decide your six-year-old should start brushing her teeth without being marched to the sink. Or that your son will put his lunchbox on the counter the second he walks in, instead of leaving it to ferment in his backpack until morning. The intention is good. The first day goes fine because you remember to remind him. By Thursday the reminder slips, and the new habit quietly dies.

The usual diagnosis is that the child isn't trying, or that you weren't consistent enough. But the real problem is structural. A brand-new behavior has nothing to hold onto. It floats free in the day, waiting for someone to remember it — and the someone is almost always you. The fix isn't more willpower or more nagging. It's giving the new step an anchor.

Why some behaviors run themselves

Think about the things your child already does without a single reminder: kicking off their shoes at the door, climbing into the car seat, reaching for the same cereal bowl. These aren't acts of discipline. They're habits, and habits run on a loop psychologists describe as cue, routine, reward. A cue in the environment — the doorway, the car, the morning — triggers a behavior automatically, before conscious decision-making gets involved.

The important word is cue. Established habits already have a stable, reliable trigger baked in. The child doesn't have to decide to take off their shoes; the door decides for them. A new habit fails not because the child can't do the action, but because it has no cue of its own. So it never fires on its own.

Habit stacking is the move that solves this. Instead of inventing a fresh trigger and hoping it sticks, you bolt the new behavior onto a habit that already has a rock-solid cue. The formula, popularized in James Clear's work on behavior design, is simple: After [thing they already do], they do [the new thing]. After shoes come off, lunchbox goes on the counter. After pajamas go on, teeth get brushed. The old habit becomes the alarm clock for the new one.

The science of "after I do X, I'll do Y"

This isn't just a tidy mnemonic. It maps onto one of the most reliable findings in the psychology of behavior change: implementation intentions. The psychologist Peter Gollwitzer spent decades studying the difference between goal intentions ("I want to brush my teeth more") and implementation intentions ("When I finish putting on my pajamas, then I will brush my teeth"). The second kind, an explicit if-then link between a situation and an action, dramatically outperforms the first. Across a large body of studies, plans phrased this way produced a sizable, consistent boost in follow-through compared to good intentions alone.

Why does the if-then form work so well? Because it hands control of the behavior over to the environment. Once the link is rehearsed a few times, the cue — finishing the pajamas — starts to pull up the action automatically, the way a familiar smell pulls up a memory. The child no longer has to remember to brush. The previous step reminds them. For kids, whose ability to hold a future intention in mind is still developing, outsourcing the remembering to the environment is exactly what they need.

BJ Fogg, the behavior scientist behind Tiny Habits, calls the existing behavior an anchor. His advice is to make the new behavior small enough that it's almost impossible to skip, attach it firmly to the anchor, and let it grow from there. A child who reliably hangs up their backpack can reliably add one small action right after it. A child asked to overhaul their whole afternoon cannot.

How to actually build the stack

Start by watching, not instructing. For a few days, notice what your child already does on autopilot — the genuinely automatic moments, not the ones that require three reminders. Those automatic moments are your raw material. A habit that still needs prompting can't anchor anything, because it isn't stable yet itself.

Then pick one anchor and one new step, and make the link explicit out loud, in if-then language: "After you put your shoes by the door, you hang up your coat." Say it the same way every time. The consistency of the phrasing matters as much as the consistency of the action, because you're training a single, specific trigger — not a general sense that coats should be hung up.

Keep the new step tiny at first. The goal in week one is not a perfectly hung coat; it's the link firing reliably. Once the child is doing the new step right after the anchor without you saying anything, you've got a real stack. Now you can let the standard rise, or add a second link onto the end of the first. This is how short routines grow into long ones — not by adding everything at once, but by chaining one anchored step to the next, each new habit borrowing the reliability of the one before it.

A few things sink a stack. Anchoring to something that isn't actually automatic yet — the link has nothing to stand on. Choosing an anchor that happens at a wildly different time each day, so the cue is never the same. And piling three new steps onto one anchor, which overloads the link and guarantees that at least one gets dropped. One anchor, one new step, until it runs itself.

Let the chart hold the chain

There's a reason this works better when the sequence is visible rather than spoken. A spoken anchor still lives in your head; you have to be present to voice it. A visible sequence puts the chain in the world, where the child can see each step lead to the next without you in the loop. The order on the page becomes the if-then plan, made physical.

This is the quiet logic behind Rhythm — Visual Routines. Instead of you being the cue that triggers every step, the app lays the routine out as a chain a child can follow with their eyes: one picture leading to the next, each finished step pointing at the one after it. The anchor and the new habit sit side by side, so the link you're trying to build is right there in front of them. If you've been trying to graft a new step onto your child's day and watching it slide off by Thursday, you can see how Rhythm makes the chain visible at https://rhythm.lumenlabs.works. Build one good link, and the routine starts pulling itself forward.