Why absolute language is ruining feedback

A rater opens the form, thinks about a colleague for a second, and types “always misses deadlines.” They hit submit and move to the next question. Nobody meant to exaggerate. They just reached for the fastest way to express a real frustration, and the fastest way is almost always an absolute.

Absolute language, the always, never, everyone, completely reflex that shows up across nearly every 360 review, is a symptom rather than a wording problem you can fix with a better word list. A rater who reaches for an absolute usually has a real moment behind it somewhere; the question in front of them just never asked them to name it.

One quick distinction before we go further: this isn’t about absolute rating scales, a design choice about scoring someone against a fixed standard instead of their peers. This is about the words themselves and what they cost a 360 review.

Key takeaways

• Absolute language (“always,” “never,” “everyone”) is what a rater defaults to when the question they were asked didn’t require anything specific, more than it’s a wording tic.
• Absolutist claims are unfalsifiable. “Always misses deadlines” can’t be checked, agreed with, or acted on, and one counterexample is enough for the recipient to dismiss the whole thing.
• It follows the same pattern as an unanchored numeric rating: both let the rater round to an extreme instead of doing the harder, specific work.
• Softer word choices (“often,” “regularly”) treat the symptom. The actual fix is a question that asks for a specific moment in the first place.
• Ask for one instance and its effect, and absolute language mostly disappears on its own.

What “always” and “never” actually do to a 360

Absolutist wording breaks a 360 review in three specific ways, and none of them are about tone.

First, it’s unfalsifiable. “Always misses deadlines” can’t be checked against anything, agreed with, or turned into an action, because it describes an impression stretched across every instance the rater can’t actually enumerate rather than one real event.

Second, it invites the recipient to disprove it rather than consider it. Imagine a manager reading “never speaks up in meetings” about a direct report who spoke up twice last week. The manager’s first reaction is “that’s not true,” and the entire piece of feedback gets discarded, including whatever real observation was underneath it.

Third, raters round to the extreme because it’s the path of least resistance. Naming one specific Tuesday takes more effort and feels more exposing than reaching for a general impression. “Always” and “never” let a rater express a real feeling without doing the harder work of remembering and defending a specific moment.

Why it keeps happening, even to thoughtful raters

This is the same root cause behind why 360 feedback is vague generally: a question that never required a specific answer, and a rater who reaches for whatever is easiest to write.

The same failure shows up in numeric ratings, the case against a standalone rating scale: a bare number, a 2 out of 5 on “communication,” is just as unfalsifiable as “never communicates well.” Both let the rater avoid the specific, harder work of describing what actually happened. A rating scale on its own corrupts a 360 review the same way absolute language does, by giving the rater an easy exit that produces nothing the recipient can act on.

Imagine a peer reviewer staring at a blank text box under the question “How does this person handle deadlines?” They genuinely can’t recall a specific instance on demand, so they write “usually pretty good” or “sometimes misses them,” and the review moves on with nothing anyone can point to. They’re answering the exact question they were asked, which was too broad from the start to produce anything sharper.

The fix isn’t better words, it’s a better question

Telling raters to avoid “always” and “never” treats the symptom. It asks people to self-edit under time pressure, which works inconsistently at best. The actual fix sits upstream: ask a question specific enough that an absolute becomes the harder answer to give.

Compare two versions of the same competency question. A vague version: “Rate this person’s collaboration and communication.” A rater with nothing specific in mind will default to a number and maybe a general line. An anchored version: “Describe a recent situation where this person’s communication either helped or hurt the outcome. What happened, and what was the effect?” The second version makes the specific answer the natural one, with no shortcut through “always” or “never” once the question is already asking for one real moment.

For more on writing questions this way across a whole review, see 360 feedback questions that actually surface blind spots.

This is the model behind written feedback and criteria ratings in Lynxify.me: every question in the criteria library carries a description of what a high rating specifically looks like, so a rater has something concrete to respond to rather than a blank invitation to generalize. I mention it because it’s the actual mechanism behind the fix, and you can build the same principle into a shared document yourself: ask for one moment and what it cost, and the question does the rest.

What to write instead

If you want a tactic you can use before your next review round, here it is: replace the pattern with the instance. Instead of “always misses deadlines,” write “missed the launch deadline twice this quarter without flagging it in advance, so the team found out the day of.” Instead of “never speaks up,” write “didn’t raise a concern in three sprint planning sessions where I later learned they disagreed with the plan.”

Notice what changed. The specific version is checkable, the recipient can either recall the moment or ask a clarifying question, and it survives a single counterexample because it never claimed to be universal. It’s also more useful: “always” tells someone there’s a problem, while “missed the launch deadline twice without flagging it” tells them exactly what to change.

For what the specific version actually looks like across more situations, see 360 feedback examples.

Keep this technique in your back pocket, but don’t stop there. A questionnaire that keeps producing absolutist answers no matter how carefully people are briefed is telling you something about the questions themselves.

The words are a symptom worth reading correctly

Absolute language is what happens by default when a question leaves room for a general impression instead of asking for a specific one. Fix the question, and the words mostly take care of themselves without any phrasing reminders.

If you’re building your next round of questions and want that specificity built in from the start, you can start your first 360 in Lynxify.me by signing in with Google or Microsoft, no setup call needed. The principle travels with or without the tool: ask for one moment, and the absolutes mostly disappear on their own.