Feedback on Process, Not Just Product

Share / assign

Why it works

Feedback can aim at different levels, and the level it targets changes what a student learns from it. Feedback about the person ('you're so smart,' 'you're just not a math person') is the least useful and can be actively harmful, because it tells the student the outcome is about a fixed trait, not something they can change. Feedback about the product alone ('this answer is wrong,' 'good essay') tells the student where they stand but not how to get better. The most powerful feedback, in syntheses by Hattie and others and in Carol Dweck's work on mindset, targets the process and the self-regulation behind the work: the strategies the student used, the effort and approach they took, what they did that worked and what to try instead. Process feedback teaches the how of improvement, 'the way you organized this argument around evidence made it much stronger; now try the same with the counterargument', and it builds a growth orientation, because it locates success in things the student controls and can repeat. This does not mean never commenting on the product; students need to know where they stand. It means pairing that with the process insight that makes improvement possible, and being especially careful to praise process and strategy rather than fixed ability. The practical shift is a habit of asking, when giving feedback, 'am I telling them how to get better, or just how they did?' and 'am I pointing at what they did, or at who they are?' The workshop helps teachers rewrite their default feedback toward process, retire person-level praise and criticism, and keep the product feedback that genuinely orients students.

The research: Research on feedback levels (Hattie, Timperley) and process praise (Dweck).

The run-of-show

Choose your slot. The agenda, timings, and length update to match.

The core activity: aim feedback at process

The heart of the session is rewriting default feedback so it targets the strategies and effort behind the work.

Name the strategies, approach, and effort the student used, what worked and what to try instead.
Retire person-level feedback ('so smart,' 'not a math person'), which locates success in fixed traits.
Keep the product feedback that orients students on where they stand, paired with the process insight that enables improvement.
Build the habit of asking: am I telling them how to improve, or just how they did, and am I pointing at what they did or who they are?

Name the how, not the whoFeedback on the process, the strategies and effort behind the work, teaches students how to improve and builds a growth orientation. Person-level praise and product-only comments do not. Keep product feedback for orientation; add process for improvement.

Facilitator notes

Person-level praise ('you're so smart') is the subtle trap; it feels kind but ties success to a fixed trait.
Process feedback must be specific; 'good effort' is not process feedback, naming the strategy is.
Keep some product feedback; students still need to know where they stand, paired with the how.

'You're so smart' is not a compliment that helpsPraising fixed ability teaches students that success is a trait, so struggle means they lack it. Praise the strategy and effort instead, which they can control and repeat.

Adapt it

Elementary: name the specific thing the child did ('you checked your work'), not 'good job.'
Secondary: point at the strategy in the work and the next move; tie it to their goals.
Any setting: watch reflexive ability praise; redirect it to process every time.

Participant handout

One page for every teacher. Print it, or save it as a PDF.

K12 Academics · Professional Learning

Feedback on Process: name the how

Person < product < process: name the strategy and effort, retire fixed-ability praise, keep orienting product feedback.

A product comment rewritten as process feedback:
The specific strategy or effort I will name:
A person-level phrase I will retire:
The product feedback I keep for orientation:
My two self-check questions before giving feedback:

Make it stick

Process feedback becomes natural with practice. Close by setting the follow-up:

Name a check-in: is your feedback teaching the how of improvement?
Bring one process rewrite that helped a student.
Keep catching reflexive ability praise and redirecting it.

Common questions

Isn't praising intelligence encouraging?

It feels encouraging and tends to backfire. Praising fixed ability ('you're so smart') teaches students that success reflects a trait they either have or lack, so when they later struggle, they read it as evidence they lack it, and they avoid challenge to protect the label. Praising the process, the strategy and effort they can control, encourages them to take on difficulty because improvement is in their hands.

Should I stop telling students whether their work is good?

No. Students still need to know where they stand, that is useful product feedback. The shift is to pair it with process feedback that makes improvement possible, rather than stopping at the verdict. 'This is strong' tells them where they are; 'it's strong because you grounded each claim in evidence, now do that with the counterargument' tells them how to get stronger.

What makes process feedback effective rather than vague?

Specificity. 'Good effort' is not process feedback; it is vague praise. Effective process feedback names the actual strategy or move the student used and its effect, and points to the next one: 'organizing by theme instead of by source made your analysis clearer.' It identifies something concrete the student did and can repeat, which is what makes it teach.