Powerless speech is Erickson et al.'s 1978 term for the cluster of six linguistic markers that consistently reduce how an audience rates a speaker's credibility, attractiveness, and persuasiveness — and impair message recall even when the content is identical. The six markers are: hedges ("sort of," "I think"), fillers ("um," "uh," "you know"), empty intensifiers ("really," "very," "totally"), excessive politeness ("I'm so sorry to bother you"), empty adjectives ("terrific," "fantastic"), and uptalk (rising intonation on declarative statements). The research finding that matters practically is that the markers compound: two or three together produce a rating significantly lower than any one alone.

When to use Powerless speech

Monitor for powerless speech patterns when you are presenting, pitching, or asserting in a high-stakes setting. The compound effect means a single session with several markers accumulates quickly.

Client or executive presentations
Pitching a proposal or recommendation
Salary or scope negotiations
Giving feedback to a senior colleague
Any recording or video call where delivery is under scrutiny

How to use it

Identify your dominant marker first. Most speakers have one — fillers are the most common, hedges second. Record a presentation run-through once and count. Target the dominant marker, not all six at once.
Replace fillers with silence. A brief pause reads as deliberation. "Um" reads as uncertainty. The pause is strictly better.
Audit intensifiers. "This is really important" → "This is important." Intensifiers without specificity discount the noun they modify.
Replace excessive politeness with gratitude. "Sorry to bother you" → "Thanks for making time." Gratitude acknowledges the other person without apologizing for existing.
Watch for uptalk on statements. A rising intonation on "We launched in March?" turns a fact into a question. Declarative statements land flat.

Example

Them

Can you walk us through the recommendation?

On your HUD

The recommendation is to migrate to the new infrastructure by Q3. Three reasons: cost, reliability, and developer experience.
On cost: we save $40K annually at current usage. On reliability: four outages in six months on the old stack, none in six months on the new one. On developer experience: two of the three engineers we lost cited the tooling in their exit interviews.

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

Common pitfalls

Trying to eliminate all six markers at once. Six simultaneous changes produce self-consciousness, not fluency. Pick one, get it to baseline, then move to the next.
Eliminating hedges that signal genuine uncertainty. "I'm not sure about the Q4 number" is accurate. Stripping it makes you sound falsely certain.
Conflating powerless speech with personality. The research is not about confidence as a trait — it is about specific, learnable patterns. You do not need to become a different person.

Where it comes from

Erickson, Lind, Johnson & O'Barr, JESP (1978) · Hosman & Siltanen (2006)

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.