Blogs
The Silent Erosion at Work: 7 Small Moments That Make a Good Employee Stop Trying
Nobody has complained. Nobody has resigned. She still delivers on time, still says "sure" when a new task lands on her desk, and her manager would describe her as dependable. But she stopped bringing ideas to meetings some time ago, and if you asked anyone when, they couldn't tell you.
Good employees rarely leave over one event. They drift out through a long run of small exchanges where something they offered went nowhere. Each exchange is too minor to raise. A missed reply is a missed reply. A forgotten follow-up is a busy week. The employee explains it away first, usually kindly, and that habit is what keeps the pattern hidden from both sides.
The cost turns up late. Effort drops first, then initiative, then the person starts reading job listings on a Sunday evening. By the time a manager notices, the real decision was made months earlier, on an ordinary Tuesday nobody marked.
I wrote about the same mechanism between partners in The Silent Erosion back in March. Work runs on it too. Below are seven moments I see repeatedly in the teams I train and in the couples I coach. The people in the scenes are composites. None of them is a real client.
In This Post
1. The Idea That Got No Reply
Maya spends a week thinking about how the team handles client handovers. She writes up a change and posts it in the team channel on Monday morning. Two colleagues add a thumbs-up. Her manager reads it, means to answer, and gets pulled into a budget call. By Friday the post is buried under everything that came after it.
The conclusion Maya reaches is that the idea wasn't worth a reply, which is harder to carry than being told it was weak. She also notices that she checked the channel more often than she'd admit to anyone.
Her manager meant to answer. The intention was there and the calendar wasn't. Maya only sees the silence, and she fills it herself, because people always do.
What I See as a Coach
Offering an idea is the exposed part of a job. It feels a lot like telling a partner about something you want and hearing "mm" from behind a phone. The quality of the answer matters less than the fact of one. A single line such as "Read this, want to think about it, back to you Thursday" keeps the door open.
The quality of the answer matters less than the fact of one.
2. The Credit That Went Somewhere Else
Kai builds the analysis behind a decision the leadership team is about to make. It takes his evenings for weeks. In the review, his director says, "I've been looking closely at the numbers, and this is where I've landed." Kai is sitting two chairs away. He says nothing, because correcting it in the room would look petty.
Afterwards nothing happens. The director probably didn't register the sentence at all. Kai registers it for days. He goes back over whether he should have spoken, and each time the answer is a different kind of no.
The next analysis he builds is a little less thorough. Nobody can see the difference, including Kai, who would tell you he's just busy.
What I See as a Coach
Unshared credit works like a chore that one partner does every week and the other calls "helping out." People will carry a great deal of invisible work. They stop when they realise it will stay invisible. Saying the name out loud, in the room where the work is presented, is a five-second habit that most managers never build.
People will carry a great deal of invisible work. They stop when they realize it will stay invisible.
3. The "Let's Circle Back" That Never Came Back
Amara tells her manager that nobody on the project knows who owns the vendor decisions. Two people are making them, and they've started contradicting each other. Her manager nods and says, "Good flag. Let's circle back on that next week." Next week is full. So is the week after.
Amara doesn't raise it again. Raising it twice feels like nagging, and she has never wanted to be the person who nags. So she does what capable people do with an unresolved problem. She works around it. She checks with both vendor contacts before every decision and quietly absorbs the confusion, and her days get longer in a way that never shows up on any plan.
Her manager, if asked, would say the conversation is still on the list. Amara remembers the exact words and the exact day.
What I See as a Coach
A deferred conversation is a promise, and the person who asked for it is the only one keeping count. It's the couple's "we'll talk about it this weekend" with a calendar invite that never gets sent. Attaching a date to the words "circle back" is what turns them from a polite way of closing a topic into an actual commitment.
A deferred conversation is a promise, and the person who asked for it is the only one keeping count.
4. The Question That Got a Sigh
Leo joined the team a few weeks ago. He asks a senior colleague how the approvals process works for a client contract. She says, "It's in the doc," and lets out a small breath before turning back to her screen. Someone nearby smiles. Leo says thanks and opens the doc, which has its own table of contents.
The next time Leo isn't sure about something, he weighs the cost of asking against the cost of guessing. Guessing wins. A few weeks later he gets an approval step wrong, and it's the kind of mistake that could have been avoided with a two-minute question.
The senior colleague now has evidence for something she already suspected, which is that new people don't read the documentation. Leo has evidence that asking is expensive. Both are right about what they saw, and the loop tightens from there.
What I See as a Coach
Contempt rarely shows up as an insult. It shows up as an exhale or a raised eyebrow, the same small signals that end a partner's willingness to say "I don't understand." Teams lose their ability to learn out loud one sigh at a time.
Contempt rarely shows up as an insult. It shows up as an exhale or a raised eyebrow.
5. The Feedback That Waited for the Review
Dana sits down for her mid-year review expecting a good conversation. Her manager says, "There have been some concerns about how you handle stakeholder communication." Dana asks who raised them and when. The answer is vague. It has been building for a while, apparently. It's the first she has heard of it.
Dana spends the rest of the meeting nodding. That evening she goes back through the last several months, looking for the moment someone could have said something. She finds a meeting where a colleague looked at her a beat too long. She finds an email with a short reply. Every ordinary interaction now looks like a note somebody was taking.
What I See as a Coach
Feedback that is held back stops being information and becomes a verdict. It's the same thing that happens when a partner saves a list of grievances for one big argument. The person on the receiving end can't fix what they never knew about, and they start to feel watched instead of supported. A sentence said on the day, "that update went out without the client's context and it caused a scramble," is easier to hear than a summary delivered months later.
Feedback that is held back stops being information and becomes a verdict.
6. The Meeting That Happened Without Them
Noa has run a project for the past year. On Thursday she finds out, from a calendar invite that lands in her inbox as an afterthought, that the planning session for its next phase already took place. She mentions it lightly to her manager. "It was a quick one," he says, "and we didn't want to pull you in when you're so stretched."
The explanation is kind, and that is what makes it hard to answer. Noa can't object to being protected. She says, "Of course, thanks," and means about half of it.
What she hears underneath is that the decisions about her own project can be made without her, and that her time was the reason. The next time she is invited to something, she wonders whether the invitation was a courtesy.
What I See as a Coach
Exclusion delivered kindly is still exclusion, and it lands the way a partner's "I didn't want to bother you" lands after a decision has already been made about the weekend. The person is left grateful on the surface and smaller underneath. Asking "do you want in on this?" before deciding for someone that they don't costs a few seconds and prevents most of it.
Exclusion delivered kindly is still exclusion.
7. The Effort That Was Met With More Work
Alex gives up a weekend to settle a difficult client escalation that nobody else wanted. On Monday morning the client is calm and the account is safe. His manager says, "Great, that's exactly why I wanted you on it. Can you take the next one too?"
There was no thank you, and Alex can hear the absence more clearly than he could have heard the words. He takes the next one. He does it well, because that's who he is, and it goes to him again after that.
Somewhere in that sequence he learns the rule the organization is actually running on: competence is rewarded with more of the work nobody wants. So he adjusts. He does what is asked, carefully, and stops offering anything on top of it. From above this looks like a steady performer. From inside it is a person protecting himself.
What I See as a Coach
It's the partner who handles every difficult phone call and every awkward family conversation, whose reliability gradually becomes the reason nobody thanks them. Reliability read as a given is one of the fastest routes to resentment I know. A sentence of acknowledgement, said before the next request, changes what the next request means.
Reliability read as a given is one of the fastest routes to resentment I know.
If these seven moments feel familiar, I write about the same pattern every Thursday in Proximity, a newsletter that reads workplace friction as relational dynamics rather than technical failure. Subscribe to Proximity →
The Half of This That Belongs to the Employee
Nobody in those seven scenes behaved badly enough to report. The manager who didn't reply had a full week. The director was thinking about the room. The colleague who sighed was tired. Every moment has an ordinary explanation, and that explanation is what stops anyone from stepping in.
The employee's side of it deserves the same honesty. Maya, Kai, Amara and the rest each decided what the silence meant, and none of them checked. Nobody said, "I posted that on Monday and haven't heard anything, did it land?" Each pulled back instead, and the pulling back felt like maturity. It worked like a slow withdrawal.
In a marriage this is the partner who stops raising things and gets described as "easier lately." At work it's the colleague who becomes "low maintenance." Quiet gets read as peace by everyone, including the person being quiet. Each person in these scenes added something, and none of them added it on purpose. That's why blame doesn't get you far here, and why a specific conversation between two people usually does.
What to Do This Week
If you manage people, or work beside them, these five habits interrupt most of the moments above:
Write down every "let's circle back" you have said in the past month. Put a date next to each one and send it to the person who asked.
Answer ideas on the day they arrive, even if the answer is "not yet." One line is enough.
Say who did the work, by name, in the room where it is presented.
Give feedback the day you have it, in a sentence, so nobody hears it for the first time in a review.
Ask one person on your team, "Is there something you've stopped mentioning to me because it didn't seem worth it?" Then listen without defending anything.
If you are the one who went quiet, pick a single moment from this list and tell the other person plainly. For example: "I stopped sending ideas after a few of them went unanswered. I'd like to start again, and I need to know how you want to receive them." That gives them something specific to respond to, which a general sense of being unhappy never does.
Some of these situations sit too long for a sentence to fix. Two people have each built a story about the other, and the story has hardened. This is the work I do in coaching and corporate training. I sit both people down, and we go through what happened, what each of them assumed, and what each needs from here. I use the same approach I use with couples, because being unheard feels the same at a desk as it does at a dinner table.
If you recognized your team, or yourself, in any of these seven moments, book a free 30-minute call and we can look at where yours began.
Handcrafted by Coach Foundation | Copyright © 2023 Swati Mukherjee's Coaching. All Rights Reserved.