Written Feedback¶

Strategy · All strategies
Evidence · no claims cited

Description¶

Written feedback delivers comments on learner work — identifying what was done well, where performance falls short of the goal, and what to do next. It is carried out through margin comments, end comments, rubric-anchored notes, or structured feedback sheets, ideally framed as actionable guidance rather than verdicts.

Design Implications¶

Written feedback is one of the most powerful — and most variable — influences on achievement: its average effect is large, but roughly a third of feedback studies show negative effects because poorly designed feedback directs attention to the self rather than the task [~S]. Feedback works when it answers three questions — Where am I going? How am I doing? Where to next? — and fails when it merely grades or praises. Because written comments arrive after performance, they must be paired with opportunities to revise or re-attempt, or they are simply documentation of failure.

Context¶

Requirements¶

• Clear success criteria shared with learners in advance, so comments reference a known target (Assessment for Learning)
• Comments that are specific, task-focused, and include a next action — not just error location
• Time and structure for learners to act on the feedback (Revision or resubmission)

Constraints¶

• Feedback accompanied by a grade or score is often ignored; learners attend to the mark and skip the comments [-S]
• Praise and personal comments ("you're so smart") redirect attention to ego and can depress subsequent performance, especially after failure [-S]
• Overly detailed feedback on weak work can overwhelm working memory and produce worse outcomes than no feedback for novices [~S]
• Feedback without an opportunity to apply it produces negligible learning gains [-S]

Implementation Variability¶

• Comment codes (e.g., "AWK" for awkward syntax) reduce marking load and force learners to self-correct
• Whole-class written feedback (e.g., "next-step" sheets addressing common errors) trades individualization for speed and reduced threat
• Audio/screen-recorded feedback conveys tone and nuance that text strips out, at similar production cost
• Peer written feedback using structured protocols builds evaluative judgment, though quality must be trained

Target Learners¶

• Struggling learners benefit most from specific, actionable, task-level comments; ego-directed feedback harms them disproportionately [~S]
• High-achievers benefit more from hints and prompts than from full corrections, which can do the thinking for them
• Novices need more directive feedback; experts benefit more from facilitative comments that prompt self-evaluation [~M]

Target Learning Goals¶

• Improving quality of complex products (writing, code, designs) through iterative revision
• Developing evaluative judgment — the capacity to judge one's own work against criteria
• Closing identified gaps between current and target performance (Assessment as learning, not just measurement)

Instructions¶

1. Establish success criteria or a rubric before the task so feedback has a shared reference point (Clear Structure)
2. Collect work and diagnose against the criteria, identifying one or two high-leverage issues per learner rather than marking everything (Cognitive Load Management)
3. Write comments in the form of a next action ("Add a topic sentence that states your claim") rather than a judgment ("weak paragraph")
4. Withhold the grade until the learner has read and acted on the comments
5. Build in class time for revision and resubmission, so feedback is a midpoint, not an endpoint (Action-Oriented Feedback)

Related Strategies¶

• Action-Oriented Feedback — the framing principle: every comment should specify what to do next
• 5-Minute Writing Conferences — the oral counterpart; written and conferenced feedback are often alternated in writing instruction
• 3-2-1 Reflection — a lightweight structure for learners to process and respond to feedback received

Examples¶

• Writing instruction with revision cycles — Draft–comment–revise sequences in which the teacher's margin comments drive a mandatory second draft; the revision, not the comment, produces the gain.
• Code review on GitHub — Inline line-level comments plus summary review comments on pull requests; the merge-blocking review is a structural guarantee that feedback is acted on.
• No-grades marking policies — Several UK schools (e.g., approaches documented by Evidence Based Education) replace scores with comment-only marking after evidence that grades mask comments.

Key Sources¶

• Hattie, J., & Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81–112. doi:10.3102/003465430298487
• Shute, V. J. (2008). Focus on formative feedback. Review of Educational Research, 78(1), 153–189. doi:10.3102/0034654307313795
• Kluger, A. N., & DeNisi, A. (1996). The effects of feedback interventions on performance: A historical review, a meta-analysis, and a preliminary feedback intervention theory. Psychological Bulletin, 119(2), 254–284. doi:10.1037/0033-2909.119.2.254
• Wiliam, D. (2011). Embedded formative assessment. Solution Tree Press.
• Butler, R. (1988). Enhancing and undermining intrinsic motivation: The effects of task-involving and ego-involving evaluation on interest and performance. British Journal of Educational Psychology, 58(1), 1–14. doi:10.1111/j.2044-8279.1988.tb00874.x