Learning Platform
Глоссарий Troubleshooting Темы Колода
Урок 13.03 · 28 мин
Продвинутый
Politeness theoryFaceBrown and LevinsonFTAMitigationPragmaticsUS politeness
Требуемые знания:
  • english-c2-us / Implicature systems at C2

Politeness theory applied

Brown and Levinson’s Politeness: Some Universals in Language Usage (1987) is the single most influential framework in modern pragmatics, and the framework most useful for understanding why Russian-direct English routinely lands wrong in American conversation. The argument is short and powerful: every speaker has a public self-image — face — with two components, positive face (the want to be approved of, liked, included) and negative face (the want to be unimpeded, autonomous, free from imposition). Many speech acts intrinsically threaten one or both faces. These are face-threatening acts (FTAs): requests, refusals, criticisms, disagreements, advice, warnings, even compliments and offers can threaten face under the wrong conditions.

The native speaker’s machinery for handling FTAs is politeness strategies: a ladder of moves from blunt-and-unmitigated (bald on-record) through positive politeness (we’re in this together), negative politeness (I respect your autonomy), off-record (I’m not really asking), to don’t do the FTA at all. Choice along the ladder is governed by three variables — power (P), social distance (D), and rank of imposition (R) — whose weighted sum (Wx = P + D + R) determines how much face-work the FTA requires.

For a C2 Russian-speaking learner, the issue is rarely what to say and almost always how much face-work to layer in front of it. American English does not require more politeness than Russian in absolute terms — both are face-conscious cultures — but it deploys politeness with different markers, in different positions, and around different acts. This lesson maps the system.

Handling conflict and de-escalation — face-saving moves (C1) Meeting and group discussion — entering, holding, yielding (B2)

Face — what it is, what threatens it

Positive face: the want to be appreciated, approved, included, liked. Threatened by criticism, disagreement, accusations, taboo violations, mentioning failures, ignoring, interrupting, expressing strong negative emotions.

Negative face: the want to act unimpeded. Threatened by requests, orders, advice, warnings, threats, reminders, offers (which create debt), promises (which constrain), compliments (which can create envy or imposition to reciprocate).

The threats are mutual: many acts threaten both speaker’s and hearer’s face. Confessing a mistake threatens speaker’s positive face; correcting someone threatens hearer’s positive face. Politeness theory predicts the redress a speaker offers depends on how much face is at stake.

The Wx weight — when to mitigate

Brown & Levinson’s formula: Wx = P(H,S) + D(S,H) + R.

  • P (power): how much power the hearer has over the speaker. Boss-to-employee is high P from H’s perspective (the speaker has low power); peer-to-peer is zero.
  • D (distance): how socially close. Strangers are high D; old friends are low D.
  • R (rank of imposition): how big the request/demand. Borrow a pencil is low R; borrow a car is high R.

When Wx is high, you go further up the strategy ladder. Russian and English calibrate these variables slightly differently — Americans treat strangers with lower D than many cultures (chatty service interactions); Americans assign higher P to boss-relations in formal contexts but lower P in casual workplace culture than, say, Korean.

The strategy ladder

Brown & Levinson order five super-strategies from least to most face-saving:

  1. Bald on-record: maximally direct, no redress. Pass the salt. Close the door. Sit down.
  2. Positive politeness: redress oriented to hearer’s positive face — claim common ground, show appreciation. Hey buddy, could you grab the salt?
  3. Negative politeness: redress oriented to hearer’s negative face — minimize imposition, acknowledge their autonomy. Sorry to bother you, would you mind passing the salt?
  4. Off-record: don’t commit to the FTA at all; hint. Boy, this is bland. (= please pass the salt)
  5. Don’t do the FTA: stay silent; eat the bland food.

The C2 task is reading the situation and choosing the right level. Russian-direct English over-clusters at level 1; American conversational English clusters at 2 and 3.

Bald on-record — when it’s actually fine

Bald on-record is not impolite in itself. It’s the default when:

  • Urgency / safety: Get out! Move! Duck!
  • Task-focused contexts: chefs in a kitchen, surgeons in an OR, sports teams. Pass. Cover left. Move up.
  • Routinized contexts: Next. Sign here. Step forward.
  • Very intimate relationships: spouses, close family. Pass the salt. Get me a beer.
  • Granting permission: Sit down. Come in.

The trap: Russian speakers often deploy bald on-record in contexts where the American expectation is positive or negative politeness. Open the window to a colleague reads as commanding; the American move is Could you open the window? or Would you mind opening the window?

Positive politeness — claiming solidarity

Positive politeness strategies tell the hearer I want what you want / we are similar / I like you. The moves include:

  • Notice/attend to H: Hey, new haircut! Looks great.
  • Exaggerate interest/approval: That’s amazing! That’s so cool.
  • Use in-group identity markers: buddy, dude, pal, you guys, y’all, fam
  • Seek agreement: …right? you know? totally (after agreeing claim)
  • Avoid disagreement — token agreement: Yeah, no, totally — but I think…
  • Joke: So I have this terrible idea — hear me out.
  • Include both speaker and hearer: let’s, we should, why don’t we
  • Give gifts (in goods or in talk): compliments, sympathy, understanding

Example — request via positive politeness

Hey Mark, you’re the database guy, right? Quick favor — could you take a look at this query when you get a sec? I think I’m missing something obvious.

Compare with bald on-record: Mark, fix this query. Same request; opposite face-work. The positive-politeness version flatters (you’re the database guy), minimizes imposition (quick favor, when you get a sec), and self-deprecates (I’m missing something obvious) — all in 25 words.

Positive politeness in disagreement

US conversational disagreement very often uses positive politeness to soften the threat to the hearer’s positive face:

Yeah, totally — and I think you’re absolutely right that the bottleneck is in the data layer. The one thing I’d push back on is the proposed fix — I wonder if a queue would actually be cleaner here.

The disagreement is real but front-loaded with three positive-politeness moves: yeah, totally (agreement signal), absolutely right (exaggerated approval), the one thing (minimization of disagreement scope), I wonder if (epistemic hedge). Russian directness produces I disagree with the fix and skips the whole front-loading layer.

Negative politeness — respecting autonomy

Negative politeness strategies tell the hearer I recognize I’m imposing; you’re free to refuse. The moves include:

  • Be conventionally indirect: Could you…? Would you mind…? I was wondering if…
  • Hedge: I might be wrong, but…, If you have a moment…, perhaps, sort of
  • Be pessimistic about the request being granted: I don’t suppose you could…? You wouldn’t happen to…, would you?
  • Minimize the imposition: just, a quick, a small, only
  • Give deference: sir, ma’am, professor, Dr. X
  • Apologize: Sorry to bother you…, I hate to ask, but…
  • Impersonalize the speaker: One could argue…, it might be argued…, we wonder if…
  • State the FTA as a general rule: It’s company policy that…, we ask that…, visitors are required to…
  • Nominalize: Your cooperation would be appreciated (rather than please cooperate)

Example — negative politeness request

Sorry to bother you — I don’t suppose you’d have a minute to look at this when you get a chance? No rush at all.

Six negative-politeness moves: apology, pessimism, minimization (a minute), conditional (when you get a chance), explicit no-pressure (no rush at all), softener (at all). Russian speakers often skip this entire layer and produce Look at this please — which is grammatical but reads as commanding.

Negative politeness in formal AmE writing

Pursuant to our discussion of October 14, we respectfully request that the committee consider the enclosed proposal at its earliest convenience. Should additional information be required, the undersigned would be pleased to provide it.

Four NP moves in 36 words: deference (respectfully), impersonalization (the committee, the undersigned), pessimism (should additional information be required), and indirect offer (would be pleased to). This is the formal-AmE register: passive, nominalized, distant. C2 writers control the register without overdoing it.

Negative politeness for criticism

I might be missing something — and I might be reading the proposal differently than intended — but I’m a little concerned about the timeline assumptions on slide 4. Could be worth a second look.

Four NP moves for a single mild criticism: hedge (I might be missing something), hedge (reading differently than intended), minimizer (a little), pessimism-via-modal (could be worth a second look). The criticism is committed but the autonomy of the hearer is preserved.

Off-record — the hint

Off-record strategies don’t unambiguously commit the speaker to the FTA. They are deniable. Includes:

  • Hints (giving clues): It’s getting late. (= we should leave / you should leave)
  • Association clues: I forgot my wallet. (= can you spot me?)
  • Presupposition triggers: I had to walk all the way home. (presupposes the listener should have offered a ride)
  • Understatement: That paint job’s a little uneven. (= it’s a disaster)
  • Overstatement: Everyone is leaving! (= the trend is bad)
  • Tautology: Boys will be boys. (= explanation by hint)
  • Irony: Lovely weather. (during a storm)
  • Metaphor: He’s a real Eeyore.
  • Rhetorical questions: How many times do I have to tell you?
  • Ambiguity / vagueness: Some people just don’t pull their weight.

Off-record is high-stakes territory. The strategy buys deniability for the speaker but requires the hearer to compute the implicature. AmE off-record use is concentrated in close relationships (family, close friends) and in some workplace cultures (Southern AmE, polite midwestern); blunt regions and tech cultures use less off-record.

Real US example — off-record request in a sitcom

Wife (looking into empty refrigerator): Wow. The kids really cleaned us out.

Husband (heading out the door): I’ll grab some stuff on the way home.

The wife’s statement is propositionally about empty shelves; the off-record request is please get groceries. The husband’s response computes the implicature without ever requiring the wife to formulate the request bald-on-record. This is canonical American spousal pragmatics.

Off-record refusal

— Want to come to brunch on Saturday?

— Oh, Saturday is going to be a wild one for us — Sam’s got soccer, then I’ve got that thing in the afternoon, and…

Off-record refusal via overstatement of obstacles. The refusal is computable but never literal. The form preserves the asker’s positive face — the refusal isn’t no I don’t want to but circumstances make it hard.

Don’t do the FTA

Sometimes the right move is to not request, not criticize, not warn. C2 speakers should add this option to their toolkit explicitly. The American workplace often punishes both bald on-record and total silence; the balance lives at levels 2-3.

On-record vs off-record — when to be ambiguous

Brown & Levinson distinguish on-record (the FTA is unambiguously committed) from off-record (the speaker has plausible deniability). The choice depends on stakes and relationship.

On-record advantages

  • Clarity. The hearer knows what is being asked.
  • Efficiency. No interpretive work required.
  • Sincerity signal. I’m being direct because I respect you.

Off-record advantages

  • Deniability. I never asked you to do that — I just mentioned the broken light.
  • Face protection for both parties. The asker doesn’t formally ask; the answerer doesn’t formally refuse.
  • Tact in high-stakes social contexts.

When to use off-record in AmE

  • With close family, off-record requests are stock (The trash is full).
  • In some Southern AmE registers, off-record is the conventional default.
  • In contexts where the request is unusual or possibly imposing (asking for a personal favor from a colleague).

When NOT to use off-record in AmE

  • In professional contexts where deliverables matter — vague requests produce vague outputs.
  • With strangers — the hearer cannot easily compute the implicature without shared context.
  • In situations requiring action under time pressure.

Common American politeness conventions

The opening apology

American requests, especially negative-politeness ones, often open with sorry / I’m sorry / sorry to bother you. This is conventionalized — the speaker is not actually apologizing for a past wrong. I’m sorry, could I get a refill? uses sorry as a politeness marker, not a confession.

The minimizer

Just and a quick are American minimizers used everywhere: I just want to ask…, a quick question…, just a sec, a quick favor. They shrink the apparent imposition. Russian speakers underuse these.

The thank-you economy

Americans thank for small acts that some cultures consider unworthy of explicit thanks. Thanks! after a small service is routine; absence reads as cold. Russian спасибо density in equivalent contexts is lower; Russian speakers often produce English with insufficient thanks.

The compliment-response problem

American positive politeness includes giving and receiving compliments freely. The conventional response is Thanks! or Oh, thank you so much! — not the Russian-style modest deflection (Да ну). Modest deflection in American English can read as refusing the gift.

The hedged criticism

Direct criticism is high-FTA in American workplace culture. The convention is to sandwich criticism between positive and forward-looking moves: I really like X about this. Maybe consider Y. I think this is going to be great once that’s tweaked. Russian directness can produce just the Y and land as harsh.

The pre-request

US speakers often pre-request before requesting: Hey, do you have a sec? — Yeah, what’s up? — Got a quick question about the deck… The pre-request lets the hearer signal availability (or unavailability) before the FTA, distributing the imposition. Russian speakers often skip the pre-request and land directly on the request, which reads as abrupt.

The face-saving rhetorical question

US speakers convert direct requests into rhetorical questions to soften them: Why don’t we…? Wouldn’t it be easier to…? What if we tried…? These are not real questions; they propose courses of action while leaving the hearer the rhetorical out of disagreeing. Russian-direct equivalents would be imperatives or Я предлагаю… (I propose…), which English speakers may hear as more authoritative than intended.

Face-threat across speech-act types

Different speech acts threaten different faces by different amounts. A working table:

ActThreatens H’s positiveThreatens H’s negativeThreatens S’s positiveThreatens S’s negative
Requestlowhighlowmoderate
Orderlowvery highlowlow
Criticismvery highlowlowmoderate
Disagreementhighlowlowlow
Advice (unsolicited)highhighmoderatelow
Warninglowhighlowlow
Reminderlowmoderatelowlow
Complimentlowmoderatelowlow
Apologylowlowvery highmoderate
Confessionlowlowhighlow
Refusalhighlowlowhigh
Offerlowlowlowmoderate

The C2 calibration: pick the strategy ladder level that fits the threat profile. Requests need negative-politeness redress (autonomy threat); criticism needs positive-politeness redress (approval threat). Unsolicited advice threatens both — it presumes superior knowledge (S claims competence: threat to H’s positive face) and proposes courses of action (S imposes: threat to H’s negative face). This is why unsolicited advice is so often resisted.

AmE vs BrE in politeness

  • BrE understatement and off-record: BrE makes heavier use of off-record strategies. Quite good means mediocre; bear it in mind means I won’t act on it. AmE is more direct in feedback.
  • AmE positive politeness density: Americans deploy more hey, buddy, you’re awesome, that’s great than BrE. Service interactions especially.
  • BrE apology density: BrE sorry is even more frequent than AmE sorry; British speakers apologize for being bumped into.
  • Sir/ma’am: regional in AmE (Southern, military) but always-formal in BrE (now mostly archaic).
  • First-name use: AmE first-name use across power differentials is more common than BrE; AmE professionals often request first-name use early.

Mitigation devices — a working inventory

A mitigation device is any linguistic element that softens a face-threatening act. C2 speakers carry a working inventory.

Lexical mitigators

  • Just, a little, kind of, sort of, maybe, perhaps, possibly, probably
  • Quick, brief, small, short, one, only
  • Sorry, thanks, please, if you wouldn’t mind
  • Could, would, might, may (replace can, will)
  • I would think, I would say, I would imagine (replace bare I think)

Hedge constructions

  • I might be wrong, but…
  • I’m not sure if this is right, but…
  • You probably already know this, but…
  • This might be a stupid question, but…

Pre-empts

  • I don’t want to add to your plate, but…
  • I hate to ask, but…
  • I know you’re swamped, but…

Conditional softeners

  • If you have a sec…, if it’s not too much trouble…, if you wouldn’t mind…, when you get a chance…

Question-form requests

  • Could you…? Would you mind…? Would it be possible to…? Any chance you could…?

C2 production stacks 3-5 of these devices for moderate-to-high FTAs. Russian-trained speakers stack 0-1 and produce requests that read as commanding.

Functional view — politeness move ladder

LevelMoveMarker / formExample
1 BaldDirect commandimperativePass the salt.
2 PPSolidarityhey, buddy, you guys, totallyHey, could you grab the salt?
2 PPJokeself-deprecating introI’m being lazy — pass the salt?
3 NPConventional indirectCould you, Would you mindCould you pass the salt?
3 NPPessimismI don’t supposeI don’t suppose you’d pass the salt?
3 NPMinimizejust, a quick, onlyJust need the salt — could you?
3 NPApologizeSorry, I hate toSorry to bother you — the salt?
4 OffHintobservation/understatementThis needs a little salt.
5 No FTAStay silent(eat the bland food)
Проверка знанийKnowledge check
Two scenarios, each requiring you to choose a politeness strategy and justify it in Brown & Levinson terms. (a) You need your boss, with whom you have a friendly working relationship, to extend a deadline by three days. (b) A junior colleague's slide deck has a factual error you noticed an hour before the client meeting. Walk through P, D, R and the strategy choice.
ОтветAnswer
**Scenario (a) — deadline extension request.** P is high (boss has authority over deadline); D is moderate-low (friendly relationship cuts D); R is moderate-high (three days is non-trivial). Wx is therefore moderate-high — you need substantial face-work. The right level is **negative politeness** with some positive politeness mixed in. A C2 move: *Hey [name], I've got a tricky one — could I grab two minutes? The X project ran into Y, and I'm wondering if there's any way we could push the deadline by three days. I know it's not ideal, and I'm happy to take the heat with the client if needed — but I think the extra time would meaningfully improve the deliverable.* This uses positive politeness (hey + name; common ground via *tricky one*), conventional indirect (*could I, is there any way we could*), minimizer (*two minutes*), pessimism (*I know it's not ideal*), and offer (*happy to take the heat*) which gives the boss an out. Bald on-record (*I need three more days*) would threaten the boss's negative face (autonomy over deadlines) and the speaker's positive face (asking for accommodation). Off-record (*Things are kind of slipping...*) would underdeliver — the FTA is too important to leave to inference. **Scenario (b) — correcting a junior's slide before a client meeting.** P is reversed (speaker is senior); D is low (colleague); R is moderate (correction is mild FTA but time-pressure adds weight). The senior position lowers required face-work in one direction but raises it in another — over-bald correction abuses power. The right level is **positive politeness** to redress the threat to the junior's positive face. *Hey, quick one — I think slide 7 might have the Q3 revenue mixed up with Q2. Easy fix, but wanted to flag it before the client sees it. Want me to send the corrected number?* This uses positive politeness (in-group *hey*, casual *quick one*), hedged claim (*might have*), minimizer (*easy fix*), explicit help-offer (*want me to send*). Bald on-record (*Slide 7 is wrong, fix it*) would threaten the junior's positive face (competence) unnecessarily. The C2 instinct is to over-mitigate slightly when correcting subordinates — the cost is tiny, the benefit to working relationship significant.

Common Russian-speaker mistakes

  1. Defaulting to bald on-record in requests: Send me the fileCould you send me the file when you get a sec? Thanks! The added 9 words are not redundancy; they are conventional negative politeness redress.
  2. Skipping the opening sorry / hey: walking into a request cold reads as commanding. Front it: Hey, sorry to bother you…
  3. Modest deflection of compliments: Your presentation was greatOh, it was nothing reads as refusing the positive-politeness gift. Use Thanks so much! or That’s so nice to hear.
  4. Bare criticism without sandwiching: This slide is wrong in a US team setting threatens the junior’s positive face heavily. Sandwich: The data here is great — quick thing, I think the Q3 number got swapped with Q2. Easy fix.
  5. Reading hedges as weakness: a US speaker saying I might be wrong, but the timeline looks aggressive is not weak; the hedges are face-work, and the claim is committed. Don’t mistake the hedge for retraction.
  6. Off-record over-use with strangers: It’s getting late to a houseguest who isn’t close is a stronger move than Russian-direct might assume — it can read as kicking them out. Off-record requires sufficient closeness.
  7. Producing imperative + please as universal politeness: Pass the salt please is fine at table but is not enough redress in higher-FTA contexts. Please alone is not a substitute for could you / would you mind.

Summary

  • Brown & Levinson: every interaction is governed by positive face (approval-want) and negative face (autonomy-want); many acts threaten one or both.
  • Wx = P + D + R: the higher the weight, the more face-work the FTA requires.
  • Strategy ladder: bald on-record, positive politeness, negative politeness, off-record, don’t-do.
  • AmE workplace conventions cluster at PP and NP; bald on-record is reserved for urgency, intimacy, or task-focused contexts.
  • AmE-specific moves: opening sorry/hey, the just/quick minimizer, the thank-you economy, the sandwiched criticism.
  • BrE leans off-record and understatement more than AmE; AmE leans positive politeness more.
  • Russian directness most often misfires by skipping the negative-politeness redress in workplace requests and criticism.

Next lesson: Discourse cohesion at C2 — anaphora, cataphora, substitution, ellipsis, lexical cohesion; tracking referents across long texts and building cohesion in writing.

Закончили урок?

Отметьте его как пройденный, чтобы отслеживать свой прогресс

Войдите чтобы оценить урок

Прогресс модуля
0 из 5