← Back to blog

Handling a Culture Complaint That Names Someone

The first 24 hours after an employee tells you their manager or a peer is the problem. What warm but direct actually looks like, and where operator judgment ends and HR begins.

Kiyong (Eric) Lee·Operations Executive·August 2026·10 min read

The short version

Listen without interpreting. Take notes with dates and specific words. Do not paraphrase what you think they mean.
Promise only what you can deliver. Total confidentiality is not one of those things. Narrower, honest promises are.
Loop HR the same day for anything involving physical contact, threats, protected-class conduct, wages, or a repeat name. When in doubt, loop early.
Protect the reporter by not changing their pattern without asking. Silent protection reads as punishment.
Talk to the named person as the second data point, not the first defendant. Open wide before you narrow.

A line cook at Zareen's Palo Alto asked to talk to me one Thursday after service. He waited until everyone had left the kitchen and closed the office door. He told me that his sous chef had been mocking his English in front of the line for about two months. He said it happened maybe three or four times a week. He said it had gotten worse in the last two weeks and that on Tuesday another cook had told him he should just laugh along or it would get worse for him.

He was shaking a little. Not visibly, but in the way his hands sat on his knees. He asked me not to tell anyone he had come to see me.

I made small mistakes in the first ten minutes. I promised confidentiality I could not fully deliver. I asked questions that leaned toward interpretation instead of information. I said "we will handle this" before I knew what handling it looked like. He walked out with less clarity than he came in with. Everything I do now started from the corrections I had to make.

This piece is what I do in the first 24 hours after an employee tells you their manager, or a peer, is the problem. It is not legal advice. It is operator judgment, built from sixteen years running multi-unit operations across a combined $54M in scope, most recently a Michelin-recognized Bay Area group of about 215 people.

What a "culture complaint" actually is when it lands on your desk

When someone walks into your office to tell you a specific person is the problem, they have worked up the courage for weeks. They have practiced the sentence. They decided the risk of telling you is smaller than the risk of not. That decision is the most important context you have, and it changes how the first conversation should go.

There are three shapes the complaint takes, and they need different treatment.

Incident. One specific thing happened on one specific day. A comment, a shove, a message. It is discrete, it is dated, and in some categories it is easier to act on quickly.
Pattern. A behavior that has been repeating for weeks or months. Small in isolation, corrosive in aggregate. The reporter has been sitting with it, questioning whether it counted, and finally decided it did.
Signal. The reporter is not sure the behavior is wrong. They are testing whether you are the kind of leader who would take it seriously. Signals almost always sit on top of a real pattern that has not fully surfaced yet.

Your first job is not to decide which shape the complaint is. It is to listen well enough that the reporter tells you the whole shape of it. Deciding too fast pushes them into the version they think you want.

The first 24 hours

The first 24 hours are the part where you either build the trust that makes the next 30 days workable, or you lose it in a way that is very hard to earn back. There is a specific sequence I use now.

Listen without interpreting

For the first twenty minutes, ask open questions and take notes with dates and specific words. Do not paraphrase. Do not editorialize. Do not say "so what you are saying is." If they say "he told me my English is bad in front of everyone at expo on Tuesday," that is what you write. Not "hostile behavior." The reporter is watching whether you interpret. If you do, they stop trusting the notes.

Do not promise confidentiality you cannot keep

The line I use now: "I am going to protect who told me as far as I can. There are some categories where I am required to loop HR in, and if this turns out to be one of those, I will tell you before I do it. I will not tell the person you named that you named them unless the process requires it, and if it does, we will talk about how first."

It is not as reassuring as "this stays between us." But it is what you can deliver, and the reporter can tell the difference. They have been lied to in other rooms about how much of their story would stay in the room.

Do not promise action you have not decided

"We will handle this" is a sentence I have said too many times. It sounds like leadership. It is actually a promise you have not thought through. Better version: "I hear you. I am going to talk to two or three people this week, and I will come back to you by Friday with what I know and what I am going to do next." Time-boxed. Specific. And Friday means Friday.

Ask what outcome they want

Most reporters have thought about this and are afraid to say it. Ask them. "If you could pick, what would you want to happen here." The answers surprise you. Sometimes it is a formal write-up. Sometimes it is a schedule adjustment. Sometimes it is just "I want it to stop and I do not want to have to say anything else." The answer is not binding. But you cannot design a landing without knowing what they were hoping for.

Fig. 1 · The sequence for the first 24 hours.

The confidentiality question, without dressing it up

Confidentiality is not binary. It is a set of narrower promises, and clarity about which one you are making is the difference between a reporter who trusts you and one who does not.

You can usually promise: their name will not come up in your first conversation with the named person. Their schedule will not change punitively. You will not gossip.

You often cannot promise: that HR will not be told. That the named person will never figure out who reported. That no one on the team will guess based on shift patterns. When you know which category the promise falls in, say so. When you do not, say that too. The worst version is the sweeping promise that gets walked back forty eight hours later.

Confidentiality in a real complaint is a set of specific, honest promises. It is never one big promise. Reporters have been burned by the big promise before and can smell it a mile away.

When to loop HR

There are categories where HR must be looped in the same day, and there are categories where you have a beat to gather information first. This is where operator judgment lives, and it is also where you should defer to your HR partner or employment counsel if you have any doubt.

Loop HR the same day when:

The complaint involves physical contact, threats, or anything that could constitute harassment as a protected-class issue.
The complaint involves a named person who has been complained about before, even informally.
The complaint touches wages, hours, or documented protected activity.
You are unsure. Uncertainty is a green light to loop, not a reason to wait.

You have a working beat to gather information first when:

The complaint is about interpersonal style, coaching tone, or communication that is uncomfortable but not into protected-class territory.
The behavior described is a first-time observation with no prior signal on the person named.

Even in the second category, the beat is measured in hours, not days. If anything pushes the complaint into the first category, HR gets looped that afternoon. I am not a lawyer. Working rule: when in doubt, HR gets the note the same day. The cost of looping too early is small. The cost of looping too late is very large.

Protecting the reporter without changing their shape

This is the part that is easiest to get wrong with good intentions. You want to protect the reporter, so you move them off the shift they share with the named person. You give them a lighter load. You stop assigning them to the tough station.

Every one of those moves reads to the team as punishment. It reads to the reporter as punishment. It reads to the named person, if they figure out who complained, as vindication. You cannot protect a reporter by changing their pattern visibly without their agreement.

The working rule: do not change the reporter's schedule, assignment, or workload without asking them first, and without a reason you would give if the complaint did not exist. If they ask for a change, give them what they ask for and document why. Do not decide for them what protection looks like. The one exception is immediate physical safety, which changes the schedule the same day and loops HR that afternoon.

Watch for retaliation signals for two to four weeks. If the named person is suddenly cold, if the reporter's tips are shorter, if the reporter is being left off the group thread, that is retaliation regardless of whether the named person could name it as such. Move on it early.

Talking to the named person, without prejudging

Eventually you talk to the person named. That conversation is not the verdict. It is the one where you gather the other side of the picture.

The frame I use: "I want to talk to you about how things are going on the line lately. I am hearing that the tone has been rough with a couple of people. I am not here to accuse you of anything. I am here to understand what is going on for you and to give you a chance to tell me your read."

Notice what is not in that sentence. The reporter is not named. The incident is not named. Nothing has been decided. You are opening a conversation that gives the named person a chance to describe their own picture before you narrow it.

Most of the time one of two things happens next. They bring up something close to the complaint themselves ("yeah, I have been short with the new guy, I have been sleeping badly"), or they give you a picture different enough to widen your investigation. Both are useful. The one that is not useful is the one where you walk in with the verdict pre-loaded and they can only give you a defense.

The person named in the complaint is not automatically the villain of the story. They are the second data point. Treating them as the second data point instead of the first defendant is what makes the investigation honest.

Warm but direct

Warm does not mean soft. Direct does not mean cold. In this kind of conversation, both are load-bearing.

Warm looks like the same side of the table, water within reach, naming that this is a hard conversation for both of you, not filling silence.

Direct looks like naming the behavior specifically. Not letting "I did not mean it that way" stand as a full response, and following up with "regardless of what you meant, the effect on the other person was this, and we have to talk about the effect."

I lead multilingual teams in English, Korean, and Spanish, and I have had this conversation in all three. Warm and direct translates. Vague does not. If you are unclear because you are trying to be kind, the person leaves without knowing what has to change, and nothing does.

What I got wrong the first time

Three mistakes from earlier versions of this playbook I still cringe about:

I promised total confidentiality in that first Zareen's conversation and had to walk it back the next morning when HR needed looping. The walk-back damaged trust more than the original complaint had damaged the reporter's week.
I moved the reporter to a different shift for their protection, without asking, and it read as demotion to peers. The reporter told me later that was the single worst thing I did in the whole process.
I opened with the named person by naming the specific incident. That gave them no room to tell me their own picture. It turned the whole thing into a defense.

The point

An employee coming to you with a complaint about a named person is a gift and a test. A gift because they trust you enough to try. A test because how you handle the first 24 hours decides whether the next person with a complaint comes to you at all.

Listen without interpreting. Promise only what you can deliver. Loop HR when the category needs it, and when in doubt loop early. Protect the reporter without changing their pattern punitively. Talk to the named person as a second data point, not a defendant. Be warm. Be direct.

Do that, and you run the kind of operation where problems surface early enough to be solvable. Skip it, and problems only surface after they have already broken something hard to fix. The people who work for you are watching how the first one goes.

Sitting with a hard one right now?

I coach a small number of multi-unit operators each year on culture, employee relations, and the specific first-24-hours calls that shape everything downstream. If someone came into your office this week and you are not sure what the next move is, I am happy to trade notes.

Get in touch

Questions people ask

What is a culture complaint in an operations context?

A culture complaint is when an employee comes to you directly, or through a channel you own, to tell you that a named person on the team is the problem. It usually falls into one of three shapes. An incident, meaning one specific thing happened on a specific day. A pattern, meaning a behavior has been repeating for weeks or months. Or a signal, meaning the reporter is testing whether you are the kind of leader who would take it seriously. Each shape needs a different first move.

What should you do in the first 24 hours after an employee complains about a named person?

Listen first without interpreting or paraphrasing. Take notes with dates and specific words. Promise only what you can actually deliver on confidentiality, not sweeping assurances you may have to walk back. Ask what outcome they want. Decide whether the category requires HR the same day, and if it does, tell the reporter before you loop. Time-box your next update to a specific day, not vague soon.

Can you promise confidentiality to someone reporting a complaint?

Not total confidentiality. What you can promise is a narrower set: their name will not come up in your first conversation with the named person, their schedule will not change punitively, you will not gossip, and if HR needs to be looped you will tell them before you do it. What you cannot promise is that HR will never know, that the named person will not eventually figure out who reported, or that the team will not guess based on shift patterns. Being clear about which promise you are making is the difference between a reporter who trusts you and one who does not.

When should you loop HR in on a culture complaint?

Loop HR the same day if the complaint involves physical contact, threats, harassment that could touch a protected class, wages or hours, or a person who has already been complained about even informally. When you are uncertain, loop early. The cost of looping too early is a slightly annoyed HR partner. The cost of looping too late is much larger, both for the company and for the reporter. This is operator judgment, not legal advice, and if you have any doubt you should also consult employment counsel.

How do you protect an employee who has filed a culture complaint?

Do not change their schedule, assignment, or workload without asking them first and without a reason you would still give if the complaint did not exist. Well-intentioned protection that changes the reporter's pattern reads as punishment to the team and as vindication to the named person. Ask them what protection looks like from their side. The one exception is immediate physical safety, which changes the schedule the same day. Watch for retaliation signals in the two to four weeks that follow.

How do you talk to the person who has been named in the complaint?

Open the conversation without naming the reporter or the specific incident. Say you want to talk about how things have been going on the line, that you are hearing that the tone has been rough with a couple of people, that you are not accusing them of anything, and that you want to understand their picture. Most of the time they will either raise something close to the complaint themselves or give you a picture different enough that you widen your investigation. Walking in with the verdict pre-loaded turns the conversation into a defense and costs you information.

Should you change the reporter's shift to protect them?

Not without asking them first. Silent schedule changes read as demotion to the reporter and as a signal to the team that they must have done something wrong. Ask them what they want. If they ask for a change, give them what they ask for and document why. If they do not, do not decide for them what protection looks like. The one exception is if there is a real, immediate physical safety concern, in which case you move the schedule the same day and loop HR that afternoon.