Feedback That Doesn't Increase Overwhelm

More comments is not the same as more useful

Thorough feedback is usually meant as a kindness, every issue flagged so nothing gets missed next time. For someone already close to capacity, though, a long list of corrections doesn't read as thoroughness, it reads as a fresh pile of things to hold in mind at once, delivered at the exact moment they're least able to process it.

The result is a paradox worth naming directly: the more comprehensive the feedback, the less of it often actually gets used, because volume itself becomes the barrier, not the individual points being wrong or unhelpful.

By the end of this module you'll be able to explain why comment volume and cognitive load aren't the same axis as feedback quality, apply a one-changeable-thing approach to any piece of feedback, and sequence improvement across several rounds rather than trying to deliver it all in one.

Each comment has a cost, not just a content

A comment on a piece of work isn't free to receive. Reading it, understanding what it's asking for, deciding what to do differently, and holding that alongside every other comment on the same page, all of that is cognitive work, on top of whatever capacity the task itself already used. Fifteen well-intentioned comments can add up to a genuine overload, independent of how correct or reasonable any single one is.

This is why exhaustive feedback so often produces disengagement rather than improvement: faced with more than can be processed at once, the common response isn't to work through it systematically, it's to act on none of it, or to fixate on the most emotionally loud comment rather than the most useful one.

The fix isn't to care less or lower standards, it's to separate "everything that's technically true" from "the one thing that will move this piece of work forward the most," and deliver mainly the second.

Four working principles

This doesn't mean withholding information, other issues can still be noted briefly, but the feedback session should have one clear headline change, stated specifically enough to act on today, rather than a flat list where every point competes for the same attention.

Worked example: a draft report has weak structure, inconsistent referencing, several typos, and a conclusion that doesn't match the evidence. All four are true and all four are tempting to flag at once. Applying the method: structure is the highest-leverage point, nothing else can be properly judged until the piece is organised, so that's the headline comment, stated concretely ("move your strongest evidence to the second paragraph, it's currently buried in the fourth"). Referencing and typos get a brief one-line note each, not a full markup; the conclusion mismatch becomes the headline for the next round, once structure is fixed and it's possible to see clearly.

Applying it in practice

Reflect before the assessment

Think of a piece of feedback you've recently given or received. Without naming anyone:

• Roughly how many separate points did it contain?
• What would the single highest-leverage point have been, on its own?
• How could the remaining points have been sequenced across later conversations instead?

0 of 80 words written

This reflection isn't saved by the page. It stays on your screen only — copy and paste it somewhere safe (a note, your CPD log) before you move on if you'd like to keep it.

Check your understanding

6 questions. A score of 5/6 (83%) or higher unlocks your printable certificate. You can retake it as many times as you like.

Neurodivergent Minds · Certificate of Completion

This certifies that

has completed the CPD module

Feedback That Doesn't Increase Overwhelm

Date completed

50minutes

Assessment score

Certificate reference: · for your own records

Use your browser's Print (Ctrl/Cmd+P → Save as PDF) to save or print this printable certificate.