Feedback fatigue at work

What it really looks like

• Team members stop opening written feedback or skim messages without absorbing them.
• People reply with brief acknowledgements (“Noted”) but take no action.
• Meetings become dominated by justifying past choices rather than reflecting or learning.

These signs are behavioural shortcuts: people conserve attention by filtering out inputs they judge low value. The behaviour is visible across channels—email, one‑on‑ones, instant messages and review forms—and usually starts subtly before becoming a pattern.

How it appears in everyday work

• Unread review forms and low engagement with feedback platforms.
• Repeated requests to clarify previous feedback because recipients didn’t act on it.
• Managers complain that “feedback doesn’t stick” or that people are defensive in catch‑ups.
• Creators delay delivering work until they get a single consolidated review rather than iterative input.

These everyday manifestations change meeting dynamics: retrospectives become recaps, not experiments; one‑on‑ones turn into status reports; and asynchronous comments pile up without synthesis. The operational cost is slower iteration and missed learning moments.

Practical first steps managers can take

• Clarify purpose: set the intent for each feedback channel (e.g., coaching, approvals, celebration).
• Consolidate inputs: route feedback through a single reviewer or a curated summary for substantive changes.
• Prioritize: label feedback as "urgent," "optional," or "learning note" so recipients can triage.
• Set cadence: agree on windows for feedback (no‑feedback days, end‑of‑sprint reviews) to protect focus.
• Close the loop: require a brief action plan or response to show which suggestions were accepted or declined.
• Train givers: short guidelines on specificity, examples, and whether the intent is formative or summative.

These interventions reduce the cognitive cost of feedback. When managers model triage and follow‑up—by honoring agreed cadences and explaining why a comment matters—teams begin to treat feedback as a scarce, valuable resource rather than ambient noise.

A workplace example and edge cases

A product team shifted to daily written reviews from several stakeholders. Engineers grew slower: they spent more time parsing contradictory comments than shipping. The lead introduced a simple rule: only one technical reviewer for each change, and other stakeholders added consolidated points to a weekly digest. Within two cycles the team reported faster merges and more useful iterations.

Imagine a senior analyst gets ten micro‑comments on a slide deck in chat, two different people ask for opposite revisions, and a VP adds a late request before a presentation. The analyst stops acting on anything and simply presents the first draft. The useful fix is not more training for the analyst but process changes: designate a single owner for final content, ask reviewers to prioritize comments, and build a 24‑hour freeze before external presentations.

Edge cases: in small startups, rapid feedback can be productive if tightly coordinated; in large organizations the same rhythm creates noise. Also, high‑stakes situations (security, compliance) legitimately need multiple concurrent reviews—there the remedy is clearer governance, not less scrutiny.

Questions worth asking before you react

• Whose time is the feedback consuming, and what is the expected outcome?
• Are reviewers aligned on the criteria they’re using?
• Is feedback duplicative across channels or coming from too many directions?
• Have previous suggestions been visibly acted upon or ignored?

Asking these diagnostic questions first prevents knee‑jerk solutions (e.g., “stop giving feedback”) and leads to practical fixes—adjusting cadence, clarifying roles, or improving the quality and traceability of comments.