"You're hedging too much in this update, just commit to something." True, maybe — and still the wrong way to say it.
Blunt feedback like "you are hedging" or "stop hedging" can sound like a character judgment rather than a writing note, even when the person is simply exercising legitimate caution about a genuinely uncertain situation. The better move is to give specific, constructive guidance about the writing itself, not a label for how the person communicates.
Why the blunt version lands badly
"Hedging" carries a built-in tone judgment — prudent on one side, evasive on the other. Telling someone directly that they're "hedging" risks implying they're being evasive or even dishonest, when they may simply be genuinely uncertain about something that actually is uncertain. Constructive feedback should name the specific writing issue instead — too many stacked qualifiers, or a missing named condition — rather than labeling the person's communication style or, by implication, their character.
"You're hedging too much in this update, just commit to something" is accusatory and vague about what to actually change; it tells the writer there's a problem without telling them where it is. "This paragraph has three separate qualifiers stacked together — can you pick the one condition that actually matters and state the rest more directly?" names the specific writing issue instead of the person's tone, and gives them something concrete to fix. "The launch date reads as fully confident, but I know we still have that vendor dependency open — worth naming it so the risk is visible?" addresses underhedging specifically, without implying the writer was being careless on purpose.
The mistake to avoid
The mistake to avoid is blunt feedback like "stop hedging," which can feel like a character judgment rather than a writing note, and can damage trust with the person being reviewed — even when the underlying critique of the writing itself is completely valid. A writer who hears "stop hedging" learns that something was wrong, but not what, and the next draft is as likely to overcorrect into false confidence as it is to actually fix the real issue.
Want to learn "Hedge" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →Specific feedback does more than avoid offense. It also produces a better second draft, because it points at the actual sentence-level problem instead of asking someone to guess what "less hedgy" is supposed to look like.
Practice scenarios
Practice giving constructive feedback about hedged writing in situations like:
- pointing out stacked qualifiers in a paragraph without labeling the writer as evasive
- flagging underhedged writing that omits a known risk, without implying carelessness
- rewriting a blunt "stop hedging" note into a specific, actionable suggestion
Useful practice phrases:
- "Can you pick the one condition that actually matters here?"
- "I know we have [dependency] open — worth naming it in this update?"
- "Instead of 'stop hedging,' let's look at this specific sentence."