Pattern
Escalate concern with a shared signal phrase
Sometimes the useful upgrade is not louder speech but less ambiguous speech.
When it fits
- A team needs unmistakable language that says a disagreement has crossed into material risk.
When to avoid it
- Do not label routine disagreement a safety issue; overuse destroys the shared meaning of the escalation signal.
What to look for
I am concerned because [evidence]. I am uncomfortable proceeding while [unresolved risk]. This is a material safety/risk issue because [possible harm].
Why it matters
Use graduated shared language: state that you are concerned, then why the situation makes you uncomfortable, then explicitly name the safety or material-risk issue if it remains unresolved. The value comes from the team agreeing that these phrases change the response mode.
An example
'I am concerned that the file contains production IDs. I am uncomfortable running it without reconciliation. This is a data-integrity risk because the update is irreversible.'
Check your result
The listener recognizes that the message requires resolution or escalation rather than ordinary debate.
Keep this limit in mind
- Do not label routine disagreement a safety issue; overuse destroys the shared meaning of the escalation signal.
Evidence and sources
AHRQ's CUS tool provides graduated signal phrases—concerned, uncomfortable, safety issue—to make escalating risk explicit to the team.
Use safety language only for material risk; overuse weakens the shared signal.
Tool: CUS · CUS steps