Copying the senior people who own a stake in a decision onto a request or a stalled thread, so the reply happens in front of them and any delay has to be explained.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Seven weeks before peak season, the warehouse operations director at a parcel-fulfillment company needed IT to schedule a firmware update for 900 handheld scanners; the old version dropped connections in the freezer section. Her ticket had been open three weeks, and two direct emails to the IT manager had drawn 'looking into it'. She wrote one more message, calm and four lines long: the problem, the error rate (6 percent of freezer scans), the date peak volume began, and a request for an install date by Friday. She copied the vice president of operations and the vice president of IT, who jointly owned peak readiness, and nobody else. The IT manager replied within two hours with a weekend install slot. The IT vice president added a line asking to hear about anything else for peak that was stuck.
Why it works
Adding the right witnesses changes what each answer costs. A prompt reply now earns the recipient visible credit with people whose opinion matters, so complying looks better. Quiet stalling and 'let's discuss offline' lose their value, because silence reads as evasion when seniors are watching, and saying no costs more because it happens in public. It depends on copying people with real authority and a genuine stake, a request that is plainly reasonable, and a calm, factual tone. Any visible aggression flips the audience's sympathy to the recipient.
The thinking behind it
Erving Goffman Erving Goffman's The Presentation of Self in Everyday Life (1956) describes performances given in a front region before an audience, with preparation kept to a back region. Copying senior stakeholders moves a stalled request from the back region of a private thread into a front region. The recipient's reply now becomes a performance in front of people whose opinion matters, which is why a prompt, helpful answer suddenly costs less than silence.
Robert B. Cialdini Robert Cialdini's Influence (1984) describes the authority principle: people tend to defer to those who appear to hold legitimate position. Copying the vice presidents who own peak readiness brings their authority into the thread without either saying a word. Copying people with no stake borrows authority they do not have in the matter, which is why over-salting reads as intimidation.
When it fits
Escalate this way when a reasonable request has stalled in private, the delay has a real cost, and the senior people you would copy already own the outcome. You need a clean record of earlier private attempts, a request you can state in a few lines, and a culture where open escalation is accepted; in consensus-heavy cultures it can brand you a troublemaker.
How to use it well
Put the request on the record only after the private route has failed.
- Ask privately first, at least twice, and keep those messages. Escalation is credible only after the private route has failed.
- Copy the people who own the outcome or the resource, and only them. A manager two levels up on a trivial ask reads as intimidation.
- Write in a neutral register: the facts, the cost of delay, a specific ask with a date. Leave out complaint and blame.
- Give the recipient an easy way to say yes, or to explain a real constraint.
When the answer comes, thank the recipient on the same thread, so the seniors see the resolution and the recipient gets the credit. If the reply shows a real constraint, accept it in front of the same audience.
What it costs and where it backfires
It works once or twice against the same person and then gets expensive. Each use spends goodwill with the recipient, and people learn to read your CC line as a threat. Over-salting backfires (copying people with no stake, or a boss's boss on a small request), and so does any hint of aggression. The line is crossed when the copy exists to shame or intimidate. Copying someone's manager on a request you know is unreasonable, or to punish a refusal, is coercion, and senior readers can tell.
When it is used on you
Watch for your manager and skip-level newly added to a routine request, or a stalled thread suddenly copied to both bosses. Answer promptly on the same thread with a clear position or a date, since silence is what gives the move its force. If the request is unreasonable, explain why, factually, in front of the same audience. A senior recipient can name the move and take the discussion back to its owners.