One of my reports cries every 1:1 now. I don't know what to say. What's the actual move?

Tears in a 1:1 aren't a performance problem — they're a signal that something is overloaded, and your report trusts you enough (or is desperate enough) to let it show. The move isn't to fix the crying. It's to figure out what's underneath it and decide whether that's something you can actually address as their manager.

What's actually happening

When someone cries repeatedly in 1:1s, it's almost always one of three things: (1) they're overwhelmed by workload or role ambiguity and the 1:1 is the only space where the mask comes off, (2) there's something interpersonal — a peer conflict, feeling unseen, a relationship with you that feels unsafe in ways you may not realize, or (3) something personal outside work is bleeding in. Each requires a different response from you.

The three approaches

1. Create space, then redirect to specifics

Open the next 1:1 with something like: "I've noticed our conversations have been heavy lately. I want to make sure I'm helping you with whatever's going on — can you help me understand what's driving it?" Then be quiet. Let them talk. Your job in that moment is to listen without solving. Devora Zack's work on communication styles is relevant here — people process differently, and someone who's emotional may need a longer runway before they can articulate the root cause [3]. Once they name it, you shift into manager mode: "Okay, what's one thing I could change this week that would help?"

Cost: Takes patience. You may hear things that are uncomfortable (including that you're part of the problem). Gain: You get actual data instead of guessing, and your report feels heard — which alone often reduces the intensity.

2. Set a gentle structural boundary

If the crying has become a pattern that's consuming the entire 1:1 and you're getting no signal on what's wrong, you can restructure. Start each 1:1 with a shared doc — three bullets from them on what they want to cover. This gives them a container. It also lets you say mid-conversation: "I hear you — let's come back to that. What's the status on [project X]?" You're not shutting them down; you're giving the meeting a spine.

This is essentially saying no to the 1:1 becoming a venting session without saying no to the person. Halligan's MSPOT logic applies at the micro level too — omitting certain uses of a meeting is as important as defining what it's for [2].

Cost: If the tears are a cry for help, adding structure can feel dismissive. You need to pair this with approach #1 at least once first. Gain: Preserves the 1:1 as a functional management tool while still leaving room for the human stuff.

3. Name the pattern directly

If you've tried the above and nothing shifts, or if you suspect the emotion is connected to a deeper issue you can't solve (personal crisis, mental health), name it plainly: "I've noticed you've been really upset in our last several meetings. I care about how you're doing, and I want to make sure you have the right support — not just from me. Have you thought about [EAP / talking to someone outside work]?"

This is the hardest move because it risks feeling like you're pathologizing them. But a manager who watches someone struggle week after week without naming it isn't being kind — they're being avoidant. Navarro's point about nonverbal signals applies in reverse here: your silence about the pattern is itself a signal, and your report is reading it [4].

Cost: They may feel embarrassed or pull back. The relationship might get awkward for a sprint. Gain: You've done the responsible thing. And often, being the first person to say "this seems bigger than work" is exactly the permission someone needs.

My read

Do approach #1 first — this week. You need data before you can pick the right longer-term move. Most managers skip this step because sitting with someone's emotion is uncomfortable, and they jump to structural fixes or referrals. But you can't route the problem if you don't know what it is.

The condition where this breaks: if your report can't or won't articulate what's wrong after a genuine, patient attempt. Then you move to #3 — name the pattern and offer a bridge to better support.

One thing to watch: check whether the crying started after a specific event — a reorg, a project outcome, feedback you gave, a peer dynamic. Silverman's account of working under a difficult boss is a good reminder that sometimes the trigger is the manager's own behavior, and the report will never say so directly [1]. That's worth sitting with honestly.

Want me to draft the actual opening lines for that first conversation — the version that's warm but doesn't turn you into a therapist?