How Unspoken Expectations Made My Job Feel Unsafe

There were rules at work — explicit ones — about deadlines, workflows, and deliverables. But beneath that surface lay a deeper web of unspoken expectations I only became aware of when I started noticing how often I felt unsure whether I was doing enough, or doing it the “right” way.

At the beginning of a role, there’s often orientation: statements of responsibility, clear objectives discussed, contextual markers that let you know what matters most. In my case, that orientation faded into an ongoing stream of subtle cues, half-said reactions, and assumed understandings that were never shared directly.

This wasn’t chaotic. It was normal on the surface. People communicated. Tasks were outlined. Meetings happened. But underneath, there was a quiet current of expectation that had no clear source. I felt it in the way someone asked for something again even after I thought it was completed. I felt it in the tone of follow-up messages that weren’t questions but felt like judgments. I felt it in the silence after a response — as if hesitation opened a gap I couldn’t see.

It made work feel unstable, not in terms of security or role continuity, but in terms of emotional presence within the role. The absence of clear criteria made every moment feel like a test I didn’t know I was taking.

I’d seen hints of this kind of internal tension in what I wrote about why I struggle to say no without feeling like I’m failing. There, boundaries were internal, emotional, and undefined. Here, expectations were external, implied, and unspoken, but the emotional effect was the same — a feeling that I was always responding to something I couldn’t name.

What made this particularly unsettling was how consistent the ambiguity was. It wasn’t a matter of occasional confusion. It was a pattern of subtle signals that suggested there was something I should already know — something that others seemed to take for granted. But no one ever articulated what that “something” was.

Requests weren’t straightforward. There was no “Here’s what success looks like.” Instead, there were half-phrased directions, suggestions dressed as questions, corrections that didn’t clarify what was expected, and feedback that assumed alignment rather than described it. The language always hovered near meaning but never fully landed there.

In meetings, it showed up as an undertone — the feeling that something wasn’t quite said, but was implied. When someone said, *Can you take care of this?* my mind immediately shifted to *But is that enough? Will they be satisfied? Did I capture what they meant?* That internal shift wasn’t rational. No one had spelled out dissatisfaction. But the space between what was said and what was assumed felt like risk.

This wasn’t a fear of failure per se. It was a fear of unmeasured evaluation — an anxiety rooted not in discrete outcomes, but in the possibility that I had missed something that no one told me mattered.

And because no one articulated the full expectations, I started to fill in the gaps myself. I tried to interpret tone, read between lines, and anticipate reactions that might never come. That anticipation became a second job — one that had no boundaries and no explicit criteria.

Over time, this shaped how I approached every request. I began with internal rehearsals before responding. I reviewed drafts multiple times before sending them. I adjusted phrasing, anticipating how someone might interpret it. I double-checked assumptions that didn’t need checking. My internal world became a negotiation with possibilities that might never actually manifest.

This wasn’t conscientiousness. It was caution lived in an ongoing, low-grade state.

There were days when I felt like nothing I did was ever quite enough — not because it truly wasn’t enough, but because the criteria for “enough” never fully appeared. I lived in a limbo where performance was never fully measurable, only implicitly judged.

After a while, I noticed I started prefacing responses with qualifications: *I think this approach makes sense, but I want to double-check this part.* Or *Let me know if this isn’t what you had in mind.* I did this not to invite collaboration — but to protect myself from the possibility that I had misunderstood something unspoken.

Language became hedged, not because I doubted my own judgment — but because the absence of clear expectations taught me to doubt that others shared my understanding of what was intended.

Tasks that seemed straightforward on their face began to feel like high-wire acts. Nothing was inherently complex — but the invisible criteria erected a sense of uncertainty that made every moment feel more consequential than it should have. What was asked was never enough. What was implied was always unknown.

This shaped how I felt entering work each day. I didn’t wake up thinking about deadlines. I woke up thinking about alignment — trying to predict whether the signals I received yesterday would align with language I’d hear today.

In Slack, messages left me staring at phrases that felt simple but carried emotional nuance I couldn’t decode. A question like *Did you get a chance to look at this?* read like: *Are you behind? Am I interrupting? Am I late?* The words didn’t say these things. But the unspoken expectations gave them weight they didn’t literally have.

During meetings, the absence of explicit criteria made me try to interpret expressions, feels, tones — all in service of trying to know whether I was aligned. I’d sit in silence longer than necessary while my mind parsed subtleties that others might not even notice. I didn’t want to misinterpret. But clarity was never given — only hinted at.

The emotional toll of this wasn’t dramatic. It wasn’t terror or paralysis. It was a quiet, ongoing tension — a sense that the ground beneath every task might shift without warning. And because the expectations were unspoken, there was no map for how to meet them. Only guesswork lived in a space that felt undefined but consequential.

This wasn’t a workplace where feedback was absent. It was a workplace where feedback was assumed to be understood — and that assumption made ambiguity feel like risk. Where the language of responsibility existed, but the language of success did not. Where the phrase *get this done* came without clear measures of what “done” actually entailed.

And so I performed — not with confidence, but with caution. Not with presence, but with vigilance. Not with a sense of belonging, but with a sense of measurement against invisible standards. Because unspoken expectations don’t just make a job confusing. They make it feel unstable. Unsafe. And unpredictable in a way that drains you quietly, without fanfare.