You notice something that does not fit. The plan has a gap, a figure looks wrong, or an important check appears to have been missed.
The person leading the discussion seems certain. Everyone else is moving on. You are new, junior, temporary, or simply the person whose voice carries least weight.
Speaking up takes more than confidence when the consequences of being dismissed are uneven. A useful approach must acknowledge that reality while making the concern clear enough to address.
Describe the observation before the interpretation
Begin with what you can identify. “The version in this folder has yesterday’s figures” is more actionable than “This process is careless.”
Then explain why the observation matters and what you are asking for: “If we send this version, the customer may receive an incorrect total. Can we confirm the current file before release?”
The concern has three parts: an observation, a possible consequence, and a requested action. None requires you to claim knowledge you do not have.
Where you are unsure, say so precisely. “I may have missed an update” leaves room for information. Follow it with the actual question, rather than withdrawing your concern before anyone can examine it.
Match the language to the stakes
An uncertain preference and an immediate safety concern need different treatment. Avoid softening a serious issue until it sounds optional. Equally, do not describe every disagreement as a crisis.
AHRQ’s TeamSTEPPS CUS tool provides healthcare teams with escalating language for expressing concern, discomfort, and a safety issue. Its purpose illustrates why teams need recognizable ways to signal that a concern requires attention. In regulated or safety-critical work, use your organization’s required procedures and escalation routes.
For an ordinary project issue, a clear pause request may be enough: “Before we approve this, I need us to check one discrepancy.” For an immediate risk, follow the applicable emergency or safety process rather than waiting for an ideal conversation.
Choose the channel with care
Some concerns are best raised in the meeting because a decision is about to be made. Others need a private conversation, a factual written note, or an established reporting channel.
Consider urgency, confidentiality, who has authority to act, and whether speaking directly exposes you to a foreseeable risk. Where retaliation is a concern, seek appropriate confidential advice or support. No sentence can guarantee protection in an unsafe workplace.
Keep records factual and within workplace rules. Do not collect or distribute confidential material indiscriminately in an attempt to make your concern persuasive.
If the first response answers a different question, return to the specific issue: “I understand the deadline is important. My concern is whether this is the approved version. Who can verify that?”
You can be courteous without letting the central question disappear.
Leaders must make speaking up consequential
If you lead a team, asking people to “be brave” is insufficient. A concern needs a response: acknowledgment, investigation where appropriate, a decision, and an explanation of what happens next.
Do not punish a person for raising a reasonable concern that turns out to be mistaken. Explain the information that resolves it. Do not praise openness in general while treating a real interruption as disloyalty.
Invite specific scrutiny before decisions: “What might we have missed?” Then make space for someone to answer without competing against the meeting’s momentum.
The least powerful person in the room should not have to carry the entire burden of keeping the work honest. They can make a concern clear. The team must make that clarity useful.
When something matters, begin with the observable detail. Name the consequence. Ask for the necessary check. A precise concern gives others a chance to respond responsibly—and makes it harder for the issue to vanish inside a vague reassurance.
Sources and further reading
State the concern, the concrete risk and the response needed. Use the established escalation route where required.
Explore all Insights Follow this reading path


