“Stop hedging,” a manager says, in the kind of feedback session that gets called constructive, “and just tell me what you think.” He isn’t asking her to clarify her level of confidence in the recommendation. What he actually means here: stop giving yourself an exit. Commit. Say it like you mean it.
That’s the workplace definition of hedging, and almost everyone in professional life is using it, I’ve heard it a thousand times: skirting the question without really answering, refusing to land on an answer when you’re unsure, protecting yourself from being wrong by never quite saying anything wrong with pretty words that evade real knowledge.
It gets coached out of people in leadership training.
It gets flagged in performance reviews as a confidence problem.
It is treated, consistently, as a synonym for evasion.
In this post, we’ll be looking at hedging from a social lens:
* Why hedging isn’t evasion. It’s a fully formed claim with its confidence level attached — more information, not less.
* What is the double bind? Hedge, and you’re read as unsure. Don’t hedge, and you’re read as difficult. Same content, opposite penalty.
* Two different Lakoffs, two different questions. George named the hedge. Robin named what it costs the people expected to use it.
* Why no register is safe. The framework doesn’t teach you how to speak — it teaches you to see the filter running.
* Finally, for my Linguistics Lab members why the pattern doesn’t start in a performance review. It starts years before there’s a job on the line.
This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit thestrategiclinguist.substack.com/subscribe