November 19, 2026 Jo Builds 6 min read

Hedging words that quietly kill your point

Hand-colored engraving of a Heliconia butterfly, Drury 1837

A hedge kills your point when it announces doubt without saying what the doubt is about. "I could be wrong, but" asks the reader to discount you and hands them nothing to discount with.

Now the other kind. "I have not opened the file since the last round, so the second half of this is from memory." Also a hedge. It tells the reader which half to trust.

That difference holds almost everywhere. A hedge with a reason attached is information. A hedge with nothing attached is noise you stapled to your own sentence.

What a hedge asks the reader to do

Every hedge gives the reader a job: decide how much of your sentence to believe.

Readers are bad at that job. Nobody discounts by a percentage. They round.

Rounding goes one of two ways. They ignore the hedge and treat your sentence as a flat claim, which is the thing you were trying to prevent, or they ignore the sentence.

The second one is quieter and happens more. A recommendation with enough padding around it stops looking like a recommendation, and the reader moves to a message that told them what to do.

You did the thinking. You formed a view. Then you filed it in a shape nobody can act on.

Hedges that carry information

A hedge earns its place when it names which part of your claim is soft and why that part is soft.

The good ones point at something checkable. The reader sees the gap and decides whether to go close it.

Each of those leaves the reader knowing more than they did before you hedged. That is the whole test, and it is easy to run on your own draft.

Hedges that only move blame around

The dead hedges are the ones that would fit unchanged in a sentence about anything at all.

I could be wrong. Just my two cents. Sort of. I feel like. Maybe. Drop any of them into any claim in any field and nothing breaks, because they were never attached to the claim.

What they attach to is you. They are a pre-built escape route, and the reader can hear the door swinging.

My own notes are the worst offender I know. I once wrote that a fix "should probably handle most editors", and when I came back to it I could not tell whether I had tested the thing or hoped at it. Probably was doing the work of a test I never ran.

These leak into messages the same way, and I catch mine late, with the draft typed and my hand already on send. That is where taking a Direct rewrite in Unvent pays for itself: the claim survives, the three retractions I attached out of nerves do not.

Stacked hedges are where the damage is

One hedge is a qualifier. Three in a sentence is a retraction with extra steps.

Watch it happen: "I think maybe we should probably consider moving the launch, if that seems reasonable to you."

There is a real recommendation buried in there. Move the launch. Everything else is throat clearing, and the reader has to dig through it to find the one actionable verb, then decide whether you meant it enough to defend.

The rule I use on myself is one hedge per sentence, and it has to be earned. When a second one wants in, the second one is fear, not accuracy.

Hedging spreads, too. Answer a hedged message with a hedged reply and the thread becomes two people asking each other to go first. A decision request can die that way without anyone ever refusing it.

The retraction at the end

The most expensive hedge sits after your point, where it undoes work you already did.

"Anyway, could be wrong." "But happy to go with whatever." "Does that make sense?"

The ending is where a reader decides what happens next, which is why a retraction parked there does more damage than the same words would at the top.

"Happy to go with whatever" is the worst of the family, mostly because it is untrue. You are not happy. You had a view and you traded it for the appearance of being easy to work with, and you will be mildly annoyed for a week when the other option wins.

"Does that make sense?" is fine after you explained something genuinely tangled and want to know whether the explanation landed. As a reflex at the end of a simple sentence it reads as asking permission to have spoken.

When hedging is the honest answer

Some claims really are soft, and flattening them would be a lie about your own state of mind.

Say those out loud. "This is a guess" is a strong sentence. "I might be wrong" doing an impression of a guess is a weak one.

I would rather read a paragraph with three honest hedges in it than one clean confident line from somebody who checked nothing, and most writing advice pushes you toward producing the second.

What your hedging teaches people about you

People work out how much to trust you from the distance between how sure you sound and how right you turn out to be.

Hedge everything and you get no credit when you were right, because you never claimed it. Hedge nothing and you spend all your credit the first time you are confidently wrong in public.

So label your calls. Say which ones you would bet on and which ones you are floating.

The people I go to first are the ones whose "I'm sure" means something, and they earned that by also saying "no idea" out loud, often, without dressing it up.

Next time you type "I could be wrong", finish the sentence before you send it. Wrong about what, and why. If you can finish it, keep the hedge; it is doing work. If you cannot, you were apologizing for having an opinion, and you can delete the apology without touching the opinion.

A recommendation that still recommends

Unvent rewrites what you are typing, in place, so your recommendation still reads like a recommendation. Say what you think, at the strength you actually think it.

Add Unvent to Chrome
u

Jo Builds makes Unvent, a Chrome extension that rewrites whatever you are typing, in place, in the tone you pick. More on the about page.