Family rewards guide

How to Praise a Child for Effort (Not the Result)

Praise the specific thing your child did, not the result and not the child. 'Good job' and 'you're so smart' both point a child at the outcome and at your reaction to it, which teaches them to look outward for approval and to avoid anything they might fail at. Name the effort you actually saw — the part they kept going on, the strategy they tried, the bit that was hard — and the praise lands on something they can repeat and control. Said forty times a day, 'good job' means nothing; said once, about the specific thing that was difficult, it tells your child exactly what to do again.

You say it constantly. Good job, good job, good job — at the drawing, the spelling test, the shoes going on the right feet, the tower before it falls. You say it because you mean it and because the alternative feels cold, and somewhere along the way it has become background noise for both of you. She has stopped looking up when you say it. He asks if it is good before he has even finished, and will not try anything he is not already good at.

The worry underneath is real and worth taking seriously. A child praised for every result learns that the result is the point and that your reaction is the prize, and a child who is told they are smart quietly works out that the safest way to stay smart is to never attempt the thing that might prove otherwise. You are not creating confidence. You are teaching them to perform for you and to steer around difficulty, which is the opposite of what you wanted the praise to do.

Why 'good job' and 'you're so smart' both backfire

The problem is not that you praise too much. It is what the praise points at. 'Good job' points at the outcome — the finished thing, the right answer — and tells the child nothing about how they got there, so there is nothing in it they can use next time. 'You're so smart' is worse, because it praises a fixed trait the child did not choose and cannot grow, and a child who believes success comes from being smart will protect that label by avoiding anything that risks it.

There is decades of research behind this, and the finding is consistent: children praised for ability pick easier tasks afterward and fall apart when something is hard, while children praised for effort pick the harder task and keep going. The ability praise was not neutral. It actively made them more fragile, because it told them the goal was to look capable rather than to get better.

And the sheer volume strips the words of meaning on its own. Praise said at everything is information about nothing — the child cannot tell the real accomplishment from the shoes going on, so none of it registers. The fix is not to praise less warmly. It is to make the praise specific enough that it actually says something, and to aim it at the part the child controls.

Name the specific thing they did, not the result or the kid

The whole shift is one move: describe what you actually saw them do, instead of judging how it came out. Not 'good job on the tower' but 'you kept rebuilding the bottom every time it wobbled' — that names a thing the child did on purpose, and it is a thing they can do again tomorrow on something else. The child hears exactly which part worked, which is the one piece 'good job' can never carry.

Aim it at effort, strategy, and the parts that were hard, because those are the parts within the child's control. 'You tried three different ways before that one worked.' 'You stuck with the hard page even though you wanted to stop.' 'You went back and checked it.' None of these mention whether the result was good, and that is the point — the child learns that the trying is what gets noticed, so trying is what they do more of.

You can be plainly honest too, which matters when the result genuinely was not good. A child knows when a drawing is a mess, and 'good job' said over it teaches them your praise is not to be trusted. 'That was a hard one and you finished the whole thing' is true, lands, and keeps your praise worth something, because the child can tell you are describing what happened rather than managing their feelings.

Describe, then let them judge the result themselves

The quiet goal of effort praise is a child who does not need you to tell them whether it was good. So after you have named what they did, hand the judging back to them. 'You worked on that for a long time — what do you think of it?' puts the evaluation where it belongs, inside the child, instead of training them to glance at your face for the verdict every time.

This is the fix for the kid who asks 'is it good?' before they have finished. The question is a tell that they have learned the result is yours to approve, and every time you answer it you confirm that. Turn it around gently — 'you tell me, what part are you happiest with?' — and over time the child stops outsourcing the judgment, which is the actual confidence you were trying to build in the first place.

It is also what protects them when you are not in the room. A child who can look at their own work and see the effort in it does not fall apart when nobody claps, and does not need a teacher or a coach or eventually a boss to keep refilling the tank. The praise was always meant to become unnecessary. Describing rather than judging is how you get there.

Back the words with recognition tied to effort in QuestSpark

Words aimed at effort work far better when the rest of the system agrees with them, and this is where a reward loop can quietly undo you if it only ever pays finished results. If a child earns the same whether they breezed through a task or fought through a hard one, the system is teaching the outcome lesson while your mouth teaches the effort one, and the system usually wins.

QuestSpark gives you an approval step on every quest, and that step is the place to put the specific praise rather than a silent thumbs-up. When you approve the work, name the part that was hard — 'you did the whole room without being reminded' — so the recognition arrives attached to the effort, not just the coins. The coin is the same; the sentence next to it is what the child remembers.

You can also aim the quests themselves at effort by valuing the trying, not only the clean result — a 'practised piano for fifteen minutes' quest rewards the showing up, which is the behaviour you actually want to grow, in a way that 'played the piece perfectly' never could. Let the words and the system say the same thing, and the child stops performing for your reaction and starts noticing their own.

Common questions

What should I say instead of 'good job'?

Describe the specific thing your child did, especially the part that was hard or that they chose to keep going on. 'You rebuilt the bottom every time it wobbled' or 'you tried three ways before that one worked' names something the child controlled and can repeat, which 'good job' cannot. The rule of thumb is to report what you saw rather than judge how it came out, and to aim it at effort and strategy instead of the result or the child's cleverness.

Is it bad to tell my child they're smart?

Praising the fixed trait tends to backfire, because a child who believes success comes from being smart protects that label by avoiding anything that might prove otherwise. In the research, children praised for ability pick easier tasks and give up faster when things get hard, while children praised for effort take on the harder task and persist. Swap 'you're so smart' for 'you worked really hard at that' and you point the child at the thing they can actually grow.

What do I say when the result genuinely wasn't good?

Be honest and describe the effort rather than praising the outcome. A child knows when a drawing is a mess, and saying 'good job' over it teaches them your praise does not mean anything. Something true like 'that was a hard one and you finished the whole thing' lands, keeps your praise worth something, and still points the child at the part worth repeating — the sticking with it — without pretending the result was something it wasn't.

My kid asks 'is it good?' about everything. How do I stop that?

That question is a sign they have learned the result is yours to approve, and answering it every time confirms it. Hand the judgment back: 'you tell me — what part are you happiest with?' After you have named the effort you saw, let the child evaluate the result themselves. Over time they stop glancing at your face for the verdict, which is the actual confidence you were trying to build.

How does QuestSpark help me praise effort?

QuestSpark turns chores and routines into quests kids complete and submit for your approval, and that approval step is where the specific praise goes. Instead of a silent thumbs-up, name the hard part when you approve — 'you did the whole room without being reminded' — so recognition arrives attached to the effort rather than just the coins. You can also build quests that reward the trying, like fifteen minutes of practice, so the system teaches the same effort lesson your words do instead of quietly paying for results.

See how QuestSpark works

QuestSpark helps families connect chores, routines, rewards, and earned screen time in one system that is easier for parents to run and easier for kids to understand.

Visit homepage →Read FAQ →