Hedging — "I sort of think," "I guess," "maybe," tag questions — marks the speaker as uncertain even when they are not. Lakoff’s 1975 analysis named it, and the subsequent decades of research made the finding durable: hedged language reduces how much audiences believe you, remember you, and rate you as credible. The important nuance is that hedging is correct in two situations — when you are genuinely uncertain, and when you are doing something socially risky. In every other situation, the hedge is costing you credibility you are not buying anything with.

When to use Hedging

Notice hedging when you are asserting expertise or presenting data you own. Preserve it when you are genuinely uncertain or when you are making a face-threatening request.

Presenting findings in a meeting where you own the data
Recommending a direction to a client or executive
Stating a price or proposal in a negotiation
Giving a direct assessment to a senior colleague
Any moment where "I think" is attached to something you actually know

How to use it

Audit your hedge vocabulary. The common markers: "sort of," "kind of," "I guess," "maybe," "I think" (when you know), tag questions ("it’s good, isn’t it?"), and rising intonation on declarative sentences.
Separate genuine uncertainty from performed uncertainty. "I believe the number is around forty percent" when you have the spreadsheet open is performed. "I’m not sure how the team will respond" is genuine.
Replace assertion hedges with plain assertions. "I think we should move the deadline" → "We should move the deadline." The directness is not rude; the hedge was not making it polite, it was making it smaller.
Preserve hedges for face-threatening acts. Feedback, disagreement, and difficult requests benefit from hedged language — "it seemed like," "I might be wrong, but" — because they make it easier for the other person to correct a misreading without losing face.

Example

Them

What’s your read on the market positioning?

On your HUD

The positioning is off in two ways: the headline targets the wrong job-to-be-done, and the comparison set doesn’t include the two products buyers actually compare us against.
The fix is a different page, not a different product.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Removing all hedges. Hedging that signals genuine epistemic humility ("I haven’t seen the full data, but…") is accurate, not weak. Stripping every hedge makes you sound falsely certain.
Hedging most in high-stakes moments. Nervousness generates hedges at exactly the moments when you can least afford them. Practicing in low-stakes contexts first builds the muscle.
Confusing hedging with softening. You can be direct without being harsh. "This report needs another pass" is direct and professional. "I sort of think maybe this could be a bit stronger?" is hedged. Directness and harshness are not the same thing.

Where it comes from

Lakoff (1975) · Erickson et al. (1978) · Durik et al. (2008) · Carli (1990)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.