The client was polite about it, which somehow made it worse. "I assume your team mentioned the delay?" They hadn't. You heard about it mid-call, with nothing ready to say.
Afterward, you asked your team why nobody told you. You got a round of "we were going to," and not much else.
It isn't the first time. Problems reach you late, softened, or secondhand. By the time you hear about them, they're bigger and more expensive than they needed to be.
The obvious explanation is that your team has a communication problem. There's a less obvious one worth considering: they may have learned how you take things.
How the pattern shows up
Taking things personally rarely feels like hurt feelings from the inside. It feels like caring deeply, being invested, holding a high bar.
From the outside, it looks different. Someone asks, "Why did we go with this vendor?" and you hear "You made a bad call." Your answer comes out sharper than the question deserved. A team member points out a gap in the plan, and the temperature in the room drops. A client complaint about one small deliverable sits with you all weekend. A resignation lands like a betrayal, even when the person was clear it was about a move or a new opportunity.
Your team doesn't need you to raise your voice to read any of this. Your face changes before you've said a word. Your answers get shorter. Your shoulders rise. People's nervous systems pick up on those shifts faster than they process words, and they respond to what they sense, not just what you say.
So they adjust. They phrase questions so carefully that the real question gets lost. They wait for a good time to raise the problem, and the good time never quite arrives. They fix things themselves without telling you, or they tell a colleague instead. They still respect you. They've simply learned that bad news costs them something when it reaches you.
"You found out from a client" is usually the last link in a long chain of those small decisions.
Signs it may be happening on your team
Because filtering happens out of sight, it's easy to miss. A few signals tend to show up first.
Status updates are always on track, right up until they suddenly aren't. Nothing turns amber. It goes straight from green to red.
People start sentences with "This is probably nothing, but..." or "I don't want to make a big deal of this..." Softening language like that often means someone is calculating what it will cost to tell you. Meetings run smoothly, with very little disagreement. That can look like alignment. Sometimes it's the opposite.
You hear about problems from clients, partners or other teams before you hear about them from your own people.
Any one of these can have other explanations. Two or three together are worth paying attention to.
Why "just don't take it personally" doesn't work
You've probably heard this advice before, maybe from a mentor, maybe from yourself in the car after a hard meeting. You know, intellectually, that a question about a vendor isn't a judgment on your worth. And still, in the moment, it lands like one.
That's because the reaction arrives before the reasoning does. Before you've had time to think "that's just a question," your body has already registered it as criticism and started to defend. Telling yourself not to take it personally is advice for the part of you that shows up second.
Where it can come from
For some people, feedback was never just information. It was a verdict.
Maybe you grew up in a home where comments about what you did often felt like comments about who you were. Where a B-plus brought the question "what happened to the A?" Where praise was rare and criticism was frequent, so you learned to scan every remark for the disappointment hidden inside it. Maybe approval felt like it depended on getting things right, so any sign of falling short felt like losing ground.
A child in that kind of environment learns to listen very closely for criticism, because hearing it early made it easier to prepare for. That sensitivity was useful. It may even be part of why you read people so well today.
The trouble is that the old filter is still running. A team member's question can echo something much older, and the reaction you're having isn't really to the question in front of you. It's to everything that question reminds your nervous system of.
This isn't about blame. It's about recognizing that a lot of what stings at work was set up long before work.
What it's costing
This is where taking things personally stops being a private struggle and becomes a business problem.
When your team filters what they tell you, you end up making decisions on a softened version of the truth. Good news reaches you quickly. Bad news arrives late, if it arrives at all. A risk someone spotted weeks ago surfaces only once it's already expensive. Clients notice the gap before you do.
Gallup's research has found that only about one in five U.S. workers strongly agree that their opinions count at work. On a team of ten, that's two people who believe what they say actually makes a difference. Gallup also points out that employees are often closer to the day-to-day issues than their manager is, which is exactly why their input matters. The people nearest the problems are often nearest the solutions too. When they stop speaking up, you lose both.
There's a personal cost as well. Taking things personally is exhausting. Replaying a comment for three days, rehearsing what you should have said, wondering what someone really meant. That energy could be going into the business, or into your evenings and weekends.
What changes when the pattern settles
Resolving this doesn't mean becoming someone who doesn't care. You'll still care about your work, your team and your clients. What changes is the filter. A question starts landing as a question. Feedback starts registering as information you can use, not a judgment you have to survive.
From there, conversations get easier. You can say "tell me more" instead of defending. You can thank someone for bad news and mean it. And your team notices faster than you'd expect. The careful phrasing relaxes. People stop waiting for the perfect moment. Your clients stop being the ones who tell you first.
One sentence can start the shift: "If something's going sideways, I want to hear it from you first, even if it's messy." Then comes the harder part. When someone takes you up on it, thank them before you react to the news.
A small experiment for this week: said versus heard
This week, when a comment or question stings, write down two things as soon as you can. First, the exact words the person said. Second, what you heard.
"Why did we go with this vendor?" might have become "You made a bad call, and everyone can see it." "Can we revisit the timeline?" might have become "You've let everyone down again."
Then look at the gap between the two. Notice what your body did in that gap: the heat, the tightness, the urge to explain yourself. You don't have to fix anything yet. Seeing the gap is where it starts to close.
Where to start
This is the second in a series on patterns at work. If you missed the first, Why Your Team Won't Make a Decision Without You looks at the need to approve everything.
I'm Anita Govender, an emotional intelligence coach, and this is the kind of pattern I work with privately, with founders and business owners who want their teams to tell them the truth. If you're curious how you respond under pressure right now, the Presence Under Pressure Score will show you where you stand. It takes three minutes → kyraca.com/pups
