What Happens When You’re Expected to Be “On” All the Time

I didn’t notice at first. I told myself I was just engaged, responsive, committed — the usual internal narrative people give themselves when work stretches into the edges of life. But there was a subtle shift that happened over time: the sense that I was expected to be “on” even when there was nothing urgent to respond to.

In the early days, I would respond quickly because I wanted to. I appreciated the rhythm of being involved. A quick Slack message felt like connection, a fast reply felt like contribution, a late-night email felt like diligence. There was an ease to it — a playful engagement rather than a pull on my bandwidth.

But that ease dissolved like fog under sunlight. It vanished so gradually that I barely noticed it until I tried to rest. It wasn’t a specific moment. It was a quiet accumulation of patterns that led me to believe I was supposed to be available — mentally, emotionally, and communicatively — at all times.

This expectation didn’t come from an explicit rule. No one ever said, “You must always respond immediately.” But the cadence of interaction communicated it anyway. Messages didn’t wait. Threads didn’t pause. Conversations flowed in a way that implied presence was constant. And before long, I started to feel that being “off” was almost impossible.

Looking back, this pattern began around the same time I noticed a similar invisible demand in how workload creep became the new normal. Both experiences blurred the lines between presence and permission, between engagement and expectation.

On good days, being “on” felt productive. I’d respond to messages quickly, contribute early in meetings, and jump into collaborative threads with ease. It felt like being part of the flow. But on ordinary days, being “on” felt like a soft pressure under my skin — a sense that I was never fully off-duty.

Even when I wasn’t actively replying, I was listening internally, scanning for what might come next. Silent threads weighed on me just as tangibly as active ones. There was a background hum in my mind — a constant checking for updates, for replies, for any sign that something needed attention.

This wasn’t about urgency. There wasn’t always anything urgent happening. It was about readiness. A sense that I needed to be prepared for something to happen at any moment. And that kept me from fully grounding in the present because part of me was always half-attending a future response I might need to make.

And when I think about how this felt, it reminds me of what I wrote in why I don’t know how to relax on my days off. In both experiences, the absence of clear boundaries made it feel like work was only paused, never truly gone.

As this pattern took hold, my experience of downtime changed. I would step away from my desk, only to find my thoughts drifting back to unanswered messages, unfinished threads, or potential replies. My brain didn’t switch off. It simply shifted modes — from active engagement to quiet anticipation.

Weeks off didn’t feel like rest. They felt like suspended animation, where work was paused but my attention was still half-committed. I couldn’t drop out of the loop because I was still listening for it internally. I wasn’t responding externally, but internally I was still switched on, still scanning, still ready.

There were nights when I’d wake up and reach for my phone before remembering that I didn’t have to. And in the seconds it took to realize I wasn’t expected to respond, a faint resistance would rise — like something had been conditioned into me without my permission.

On days when nothing urgent was happening, the expectation to be “on” felt lighter — but it was still there. It wasn’t loud or demanding. It was a quiet background presence, like an internal alarm that had learned to operate without notification tones. I didn’t need alerts. My mind had become vigilant on its own.

This wasn’t about being ambitious or committed. It was about a rhythm of responsiveness that became default rather than optional. The line between willingness and obligation disappeared. When everything feels important, nothing feels optional — even when it is.

In meetings, this appeared as a readiness to jump in at any moment. Even when I didn’t have something to add, I felt the pressure to be alert, prepared, and engaged as if silence were a signal of disengagement rather than a space to think. Quiet moments began to feel like gaps I needed to fill, rather than neutral pauses.

On Slack, I’d draft replies carefully — not just once, but multiple times — because the pressure to be “on” made me worry about how my message would land. Even simple responses carried the weight of being interpreted correctly. And because I never fully stepped out of that internal scrutiny, my presence was constant even when my body was absent.

Sometimes I’d compare how I felt with how others responded. Some people seemed to let threads sit without checking them again. They’d come back hours later, or even the next day, without a sense of strain. I envied that quality — not because their work was lighter, but because their inner readiness wasn’t tethered to the loop the way mine was.

I began to notice how rarely I experienced rest that didn’t feel like preparation for something else. Even when I wasn’t working, I was rehearsing responses, scanning for context, anticipating what might arrive next. Real downtime wasn’t an absence of work for me. It was a lull in internal monitoring, and those moments were fleeting.

And somehow, this constant expectation didn’t show up in obvious ways. There was no performance review that said I was too slow. No one explicitly reprimanded me for not responding immediately. But the cadence of interaction made it feel like immediate response was expected, even when it wasn’t stated.

In its quiet persistence, this expectation shaped how I experienced both work and rest. It wasn’t a rule anyone wrote. It was a rhythm everyone moved in. And because the rhythm didn’t pause, I felt like I was always in motion — even when I wasn’t moving at all.