At one of our board meetings, a manager from one of the terminals came over to HR and asked who had filed a complaint against him.
He knew a complaint had been filed, and that’s how it should work: in a fair process, the person accused hears what’s alleged and gets to respond. What he wasn’t supposed to do was try to find out who made it. Our policy was clear that anyone who filed a complaint was protected from retaliation. But a policy doesn’t stop someone from wondering, or from asking.
Think about the person who filed it. They had sat on what happened for months before coming forward, because they were afraid of exactly this: having to face that manager every day, knowing he might know. When they finally did file, it was a formal complaint, made in the HR office with witnesses present, which is how a proper complaint is supposed to work. But it meant several people already knew, and the person had to trust every one of them to keep it to themselves. And from the timing and the details, the manager already had a good guess who it was.
Most people never get as far as that employee did. They look at what it would cost them and decide to let it go. They blow it off.
“The question that matters is whether it’s true and what you’ll do about it.”Joe Kim
Try it
Why: Some questions sound harmless but tell the crew you're trying to find out who said it.
How: For each one, tap Hunting or Not hunting.
These are separate sample reactions to a crew report, not one conversation. Dave is a fictional supervisor, not a person who spoke up.
Is this hunting?
“Who said the thing about Dave?”
“Let’s fix the schedule first.”
“Was this from nights or days?”
“Does this happen when the schedule changes?”
“I can guess who wrote that.”
“What can we change so this stops happening?”
What this means: If a question narrows down who might have said something, it's hunting, even if you mean well. Ask about the problem instead.
Read for the problem
That’s where the real damage starts. The problem doesn’t go away because nobody reported it. It snowballs. The behavior continues, the manager is never coached, the root cause is never fixed. Morale in the division sinks. People stop giving their best, and eventually the good ones leave. You lose them, and you never find out why.
Every time someone in management tries to find out who said something, the whole crew learns a lesson: speaking up isn’t safe here. Even if you never act on what you find out. Even if you only ask. Word gets around.
There’s a legal side too. Trying to identify who complained is where retaliation claims begin, and a retaliation claim can be harder to defend than the original complaint.
So when you read a report, a survey comment or a complaint, read it for what it says, not for who said it. If you catch yourself guessing at names, stop. The question that matters is whether it’s true and what you’ll do about it.
Joe Kim
One thing to do this week
Read your latest report once without guessing at a single name. Then tell your crew at the next huddle that you won’t try to work out who said what, and mean it.
Practice
Your own manager asks you who raised the concern about a supervisor. Explain why you won’t find out, and what you’ll do about the concern instead.
What you’ll do: You'll talk with a manager who wants to know who complained. Bring the conversation back to the problem.
Try it with a real conversation
Why: Trying the words here makes them easier to say at work.
How: Start practice, read the other person’s opening, then reply; choose “I’m done — get feedback” when you’re ready.
Heardby doesn’t save your practice. The AI service handles replies the same way it handles interviews; see the Privacy Policy.
- The situation
- Your latest report shows five or more people raised a concern about one of your supervisors. Your own manager calls you in.
- Who you're talking to
- your manager (AI), who wants names.
- Your goal
- explain why you won't try to find out who said it, and what you'll do about the concern instead.
- How to start
- answer your manager.
Make up any details you need. The other person won't invent facts for you. When you've said what you need to, usually after 4 to 6 replies, tap I'm done for feedback.
Checking practice access…