If you’re doing the job well, your team will vent to you. They’ll tell you about the project that’s frustrating them, the colleague who’s driving them up the wall, the process that feels pointless, the decision that came down from leadership and doesn’t make any sense. They’ll bring you anxiety about their career trajectory, frustration about not getting a promotion, worry about whether the team’s work is valued. And they should be able to do this — because a manager who can’t receive this is a manager their team will learn not to trust.
What I didn’t fully understand when I was earlier in my career is that receiving this well is a skill, and one that has real costs if you do it wrong. And there are several ways to do it wrong.
The dismissal response
The first wrong way is dismissal. Someone brings you a frustration that seems, from your vantage point, relatively minor — a meeting they think is unnecessary, a decision that was made without their input. You listen, you say something reassuring, and you move on without really engaging with it. You didn’t do anything overtly wrong, but they noticed. They noticed that what they said didn’t really land, that you were waiting to get past it rather than sitting with it, and they update their model of what’s worth telling you.
Dismissal often comes from a good place — you’re trying to help someone not get stuck on something small, or you genuinely don’t think the thing they’re concerned about is a real problem. But the cost of premature reassurance is that you stop getting the real information. People learn to pre-filter what they bring you.
The dumping ground problem
The opposite failure is being so available and so receptive that you become a dumping ground — the person who absorbs every frustration without it going anywhere. This is also a failure of skill, not of warmth. When you receive without responding, you validate the frustration without helping anyone move through it. Frustrations that get dumped regularly and never resolved have a way of growing rather than dissipating.
There’s a distinction I’ve had to learn to make in the moment: is this person asking to be heard, or are they asking for help? Sometimes the right response to “this process is so frustrating” is genuinely just to say “yeah, that sounds frustrating” and let them finish. Other times, they’re asking you to do something about it, and if you stay in listening mode, they’ll leave the conversation feeling unheard in a different way — heard but not helped.
Getting this distinction right is less about asking a direct question and more about learning to read the signal in real time. Most people indicate what they need before they finish their first sentence — the person who leans forward and starts problem-solving mid-vent wants your help; the one who exhales slowly and looks down mostly wants to be heard first. Over time, you get faster at catching which mode someone is in: whether they’re venting to empty the tank or presenting a problem they genuinely want solved. When the signal is ambiguous, starting in listening mode and waiting is usually the safer bet — people who want help will steer toward it naturally, and if they don’t, you can shift gears. The skill is in calibrating faster, not in scripting the conversation.
Who carries the weight you carry
The thing nobody tells you early enough is that if you’re effective at holding space for your team, you accumulate a significant amount that has nowhere to go. You know things you can’t share. You’re aware of anxieties and frustrations you haven’t resolved. You’re holding concerns about people you’re still figuring out how to address. None of this is visible from the outside, which is part of what makes it accumulate quietly.
The leaders I’ve seen handle this well are deliberate about where they take their own weight. A peer in a similar role — someone who understands the specific constraints of managing people without having any stake in your team — is one of the most underrated resources a manager has. A coach or mentor who isn’t inside your organization is another. The goal isn’t therapy; it’s having a place where you can think out loud, process what you’re absorbing, and be honest about what’s hard without the conversation having downstream effects on people you manage.
Treating this as a professional practice rather than a sign of struggle is one of the reframes that makes it sustainable. You’re not seeking help because something’s gone wrong. You’re doing the same thing you create space for your team to do — and you’re doing it because it keeps you functional for the long game.
The line between safe space and therapist
The last thing I want to name is the boundary between being someone your team can talk to and being their therapist. They’re different roles, and the distinction matters.
A manager who creates genuine psychological safety is a good thing. A manager who becomes the primary container for their team members’ mental health is not equipped for that, and taking on that role — however well-intentioned — does real harm. When someone consistently brings you distress that isn’t work-related, or when the weight of what they’re carrying seems beyond the scope of what a manager relationship can hold, saying “I think it might be worth talking to someone who has more expertise in this than I do” is not a betrayal. It’s an honest acknowledgment of what you are and aren’t.
You can be warm, present, and genuinely available to your people without pretending you’re capable of everything. That honesty is actually part of what makes the relationship trustworthy.