Why it is hard to speak up
Most people know in principle that they should mention a safety worry. In practice it can feel uncomfortable. You may be unsure that you are right, worried about looking foolish, reluctant to question a more senior colleague, or aware that the team is already behind schedule. You may have raised something before and been ignored.
These feelings are normal, and they are not a sign of weakness. Understanding them is the first step to working with them, whether you are the person with the concern or the person who receives it.
This article is general information. Employers, laws and professional codes differ between countries and industries, particularly about protections for people who raise concerns. Follow the policies and professional advice that apply to you.
Psychological safety in plain terms
Psychological safety is a team’s shared belief that it is acceptable to speak up with questions, ideas, mistakes or concerns without being punished or humiliated. It does not mean everyone agrees or that standards are low. It means that disagreement and bad news can be voiced and handled respectfully.
For safety this matters a great deal. A team that lacks it can contain several people who each privately suspect a problem and none who says so. Each assumes either that someone else has noticed or that raising it would not be welcome. By the time a problem is obvious, it may be serious.
Teams build psychological safety through everyday behaviour:
- responding to questions and concerns with curiosity rather than irritation
- admitting your own mistakes openly
- thanking people who raise issues, even if the concern turns out to be unfounded
- keeping disagreement about ideas, not about people, which is part of handling technical disagreements well
- following through, so people see that speaking up leads to something
These patterns are central to a wider safety culture, but every individual can contribute to them.
Before you speak: a short preparation
You do not need certainty to raise a safety concern. Reasonable suspicion is enough to ask a question. But a little preparation makes the conversation more effective.
- Write down what you observed. Stick to facts: what you saw, where, when, and under what conditions.
- Note why it worries you. What harm could result, and how?
- Check quickly whether you are missing something. A brief look at the drawing, procedure or numbers may answer your question. Simple sanity checks can help, but do not let checking become a reason to delay a serious concern.
- Decide who can act. This might be your supervisor, the person who owns the equipment, a safety officer or a design owner.
- Think about urgency. If there is an immediate danger, stop the work or alert people first and discuss afterwards, in line with your workplace’s rules.
Wording that tends to work
How you phrase a concern affects how it is heard. Some practical patterns follow.
- Start with the observation. “I noticed the guard is off the cutting station.” This is harder to dispute than “this place is unsafe.”
- State the concern and the possible consequence. “I’m worried someone could catch a sleeve in the blade.”
- Ask a question where appropriate. “Is there a reason it’s been removed? I may be missing something.”
- Offer help or a suggestion if you have one. “Could we refit it until the job is done, or would a temporary barrier work?”
- Be specific about what you need. “Can someone with authority look at this before the next shift?”
A structure used in some workplaces is to state the concern, say why it matters, propose what you would like done and ask for agreement. The words matter less than being clear and calm. The principles overlap with giving constructive feedback: describe what you see, explain the effect and keep the tone respectful.
Written concerns are useful when the issue is complex or you need a record. A short, plain message with the facts and the specific request is often better than a long one. Habits from clear technical emails apply here.
Choosing the moment and the channel
- Urgent danger. Act immediately, using stop-work authority or emergency procedures if your workplace has them.
- Routine concerns. A quick word with your supervisor or the relevant owner is often enough.
- Design concerns. Raise them in design reviews or other technical meetings, where other disciplines can contribute, or directly with the designer beforehand if you prefer to avoid surprising them.
- Sensitive matters. If you are worried about the response, you may consider a trusted mentor, a safety representative or an anonymous reporting route if your organisation provides one.
If you work with someone more experienced, remember that most good engineers prefer a polite question to a hidden problem. A phrase such as “I’d like to understand this better” is rarely taken as an attack.
If you are not heard
Sometimes the first response is dismissive or nothing happens. Reasonable next steps include:
- Restate the concern clearly, with the facts and the possible consequence, and ask what the plan is.
- Put it in writing so there is a record of what was raised, when and with whom.
- Ask for the reasoning if the answer is that the risk is accepted. Understanding the basis may resolve your concern, or may reveal that it needs more attention.
- Escalate to the next level of management, a safety officer, a quality or compliance function, or a safety committee.
- Use formal channels such as a whistleblowing policy, a regulator or a professional body when the matter is serious and internal routes have failed. Legal protections and procedures differ by country, so seek advice appropriate to your situation.
Keep your focus on the problem rather than on winning an argument, and keep notes factual. Stopping at the first brush-off is understandable but, for a real hazard, may not be sufficient.
If you are the one receiving a concern
How you react teaches everyone watching. Listen first. Thank the person. Ask questions to understand. Say what you will do and by when, even if the answer is that you will look into it. If you decide not to act, explain why. Do not retaliate or make jokes at the person’s expense. Over time, the way a team treats its first concern determines whether it hears the second.
A final note
You will sometimes be wrong. A concern that turns out to be unfounded still costs little compared with an unspoken one that proves real. Outcomes can never be fully predicted, and speaking up does not guarantee a fix, but it is one of the most practical contributions any engineer can make to safe work.