How to Bring a Concern to Your Team or Leader
For raising something that isn't working — a culture issue, a decision you disagree with, a pattern that's hurting people — without it reading as complaining or disloyalty.
What you could say
- "I want to raise something I've noticed, because I think it matters to how we're doing as a team, not because I'm trying to cause friction."
- "Can I bring you something I've been sitting with? I think it's worth naming before it gets bigger."
- "I care about this team, which is why I want to say this directly instead of letting it sit unspoken."
If they respond like this
"Why are you the one bringing this up?"
You could say: "Because I noticed it, and I'd rather it come from someone directly than stay a quiet rumor."
They get defensive about the concern.
You could say: "I'm not saying this to blame anyone — I'm saying it because I think we can do better, and I think you'd want to know."
"Noted" or a response that feels dismissive.
You could say: "I want to make sure this actually gets addressed, not just heard — can we set a time to follow up on it?" (Naming a follow-up makes it harder for the concern to quietly disappear.)
Worth avoiding
- Bringing the concern to everyone except the person who can actually act on it.
- Leading with blame of a specific person rather than the pattern or the impact.
- Waiting for a formal setting that may never come — a direct, private conversation is often more effective than a public one anyway.
Why this works
Teams with genuine psychological safety are measurably more effective, according to Google's own internal research on high-performing teams (Project Aristotle) — and psychological safety isn't built by the absence of hard conversations, it's built by people surviving having them. Naming a concern well, once, does more for a culture than staying silent to protect it.