At some point, the act of hearing people’s concerns stopped feeling like incidental conversation and began to feel like an expectation without compensation.
At First It Felt Casual
I used to think these conversations were just friendly check-ins — the small moments where someone wanted to share the weight of a tense meeting or an awkward exchange. I told myself it was normal, human, incidental.
I told myself it was just kindness, nothing structural. It wasn’t work. It wasn’t labor. It was just being present.
But over time, the cumulative effect of these moments began to shape my days in a way that wasn’t incidental anymore. There was a rhythm to them. A pattern. And eventually, an expectation.
This is the quiet sense you recognize when what once felt like support becomes something you feel obligated to provide — even if no one ever named it a responsibility.
Conversations That Aren’t About Tasks
These exchanges aren’t about deliverables. They don’t hinge on who said what in a meeting or which deadline is approaching. They start with nuance — tone, pause, hesitation, uncertainty.
Someone messages you after a meeting not to clarify a decision, but to say, “I’m not sure how that made me feel.” Someone else catches you in the hallway and says, “Did you notice how tense that felt?”
These are not questions about tasks. They are questions about experience — and they don’t have answers that live in process documents or org charts.
And because they don’t, they end up in a space that feels separate from work, even though it is deeply tied to how work feels.
The Shift From Support to Expectation
I didn’t notice when the subtle shift happened.
It started with a couple of conversations here and there. Then one. Then another. A colleague paused in the hallway. Someone else sent a message after a team call. Then someone asked, without preamble, “Can we talk later?”
At some point, these moments stopped being occasional and started being part of my day — not because there was an agreement, not because there was a title, but because people began to expect it.
It became less about “Do you have time?” and more about “I’m coming to you.” Because that felt easier than formal channels. Because it felt safe. Because it felt immediate.
And when no one questions it, it solidifies into a quiet responsibility.
Listening becomes an unpaid responsibility when it’s assumed rather than acknowledged.
It Feels Like Being on Call Without a Pager
There’s an odd kind of tension that comes with knowing people will reach out to you at unpredictable times — not for direction or strategy, but for understanding.
Someone texts you after lunch because they felt dismissed in a call. Another messages you mid-afternoon because they’re unsure how to interpret a comment from a colleague. Another wants to talk about how they’re feeling about work itself.
Those interactions don’t come with boundaries. They don’t come with schedules. They don’t come with credit or compensation. And yet they arrive with a sense of urgency that feels real to the person reaching out.
It’s the kind of labor you can’t put on a calendar, because it isn’t framed as work. But the absence of framing doesn’t make it less taxing.
The Internal Shifts You Don’t Notice at First
At first, I responded freely. I didn’t see it as labor — just being present. Just being empathetic. Just being a colleague who listened.
But over time, I began to notice small internal shifts. I’d check messages with a certain caution because I wasn’t sure whether it was a request for help or another emotional conversation. I’d pause before answering, wondering whether my tone would make someone feel heard or dismissed.
Part of my attention was always being allocated to other people’s moods, anxieties, and fears — even when it wasn’t part of my job description.
And because it wasn’t part of a job description, there was no language for naming what it was costing me.
It Intersects With What Others Avoid
People rarely bring uncomfortable feelings into formal channels.
They don’t draft emails to leadership saying, “I felt dismissed in that conversation.” They don’t file complaints about tension. They don’t schedule meetings with HR to unpack their uncertainty about how someone spoke to them.
Those forums exist, but they feel procedural. They feel weighty. They feel formal.
What people want instead — sometimes — is language. Validation. A sense that what they experienced makes sense emotionally, even if it doesn’t violate any policy.
And who they come to for that isn’t structured by job description, it’s structured by who feels safe.
The Day Begins Before Work Begins
Many mornings start with that low hum — the uncertainty of wondering whether the first message you open will be about tasks or about feelings.
I used to check messages and see only actionable items. Now I often see emotional signals first — replies with ellipses, replies that don’t quite land, replies that feel like hesitation rather than clarity.
That shift is subtle. But it changes how you approach the day before the day even starts.
It’s not that emotional conversations are burdensome — it’s that they become part of the landscape of your day without ever being framed as something you agreed to carry.
When it Feels Like It’s on You
What makes this different from normal collegial interaction is the implicit weight attached to it. It begins to feel like it’s on you — not because anyone said so, but because people come to you without hesitation and because the conversations don’t stop arriving.
It’s similar to patterns I’ve noticed in other writing, like when people come to me with their work stress instead of going to HR in why people bring their work stress to me instead of HR, but here it feels quieter because it’s not strategic. It’s not about avoidance of formal channels. It’s about something deeper: the sense that talking to you feels safer and more human.
And once that sense takes shape in your daily rhythm, it begins to shape how you show up — before you even read any of the actual tasks that day.
Listening becomes work when it’s a responsibility people assume you’ll carry without ever saying so.

Leave a Reply