The Always-On Trap: Why Middle Managers Can't Disconnect & What Actually Helps

Editorial Note: This is a story about three middle managers trying to create better boundaries in an always-on work culture. Their experiments are personal, imperfect, and not meant to be universal solutions. What matters is not disconnecting perfectly, but finding small ways to make presence a choice again.

The Always-On Trap: Three Middle Managers, Three Different Cages

Always-On Culture in Middle Management: When Connectivity Becomes the Job

Maya Chen is thirty-five. She lives in Austin, Texas, and works as an engineering manager at a developer-tools startup. Her team of twelve is spread across four time zones. The company has been fully remote since day one. There is no office, no desk with her name on it, no hallway where you bump into a colleague and hash something out in thirty seconds. Every interaction happens inside Slack, Linear, and Notion. The last time Maya shared a physical room with a coworker was eight months ago, at the annual offsite.

On this particular evening, her husband is asleep. Her daughter is asleep. The dishes are cycling through the dishwasher. Maya sits on the couch with her phone face-down on the cushion beside her. A Linear notification lights the screen. A comment on a pull request. Probably nothing urgent. She knows that. Her hand reaches for the phone anyway.

She unlocks it, reads the comment twice, closes the app. Opens Slack. Scrolls through the engineering standup channel. Nobody has tagged her. Nothing requires her input right now. She sets the phone down. Picks it up again.

What she is afraid of has nothing to do with outages or emergencies. What she is afraid of is waking up tomorrow to discover that two senior engineers reached a technical consensus in an async thread sometime after midnight, and her absence from that thread will be read as approval. By morning the decision will be "already agreed upon." She will have missed the window to object, and nobody will think to loop her in because the conversation was, technically, closed.

She once described the feeling to a friend over coffee. "I'm a gateway," she said. "All traffic routes through me. And a gateway doesn't get to clock out."

In Portland, Oregon, David Kessler is forty-two and works as content director for a consumer-goods brand. His team owns everything from product copy to social media posts to quarterly campaign messaging. Last year the company rolled out AI-assisted writing tools across the department. Notion AI. Grammarly Business. A couple of industry-specific generators. The logic from leadership was simple and unquestioned: the tools double your speed, so the output expectation doubles too.

It is dinnertime. His wife made pasta. His nine-year-old daughter is mid-story about something that happened at school, her fork gesturing at the air for emphasis. David sits at the table with a strand of cold pasta hooked on his fork, not quite making it to his mouth. His phone rests at the corner of the table, screen up. Notion AI just spat out a third round of revision suggestions on a product description that was finalized last week. Marketing changed the selling point. Everything needs to be rewritten. The tool can generate a draft in ten minutes. But every draft requires him to check tone, verify claims, and decide whether the language actually sounds like something their brand would say. Three rounds in, his brain has been running without a pause.

His daughter stops talking. Looks at him. "Dad, are you listening?"

"Yeah. Listening." He means it. He also doesn't. His attention is a rope pulled taut between two anchor points: the girl in front of him and the nine-a.m. publishing window tomorrow morning. The rope holds. Barely. The pasta goes cold. His wife says nothing. She has learned not to.

Elena Vasquez is forty-seven and lives in Chicago. She is an operations supervisor for a regional healthcare group, overseeing scheduling, bed allocation, and administrative workflow across three outpatient clinics. Her job has a specific kind of violence to it: half her day is spent at a desk answering Teams messages and emails, and the other half she must be physically present in the corridors. A nurse station is short-staffed. An exam room's equipment just went down. A patient's family is waiting for someone to explain what happens next. She cannot do this job remotely. She also cannot stop being online.

This afternoon she is walking back from the second-floor nurse station toward her office, a bed-allocation form in one hand that still needs her signature. Teams pings. The regional director wants confirmation on next week's schedule. She types a reply one-handed while flipping through the paper in her other hand. Then she switches to the nurse station group chat and fires off the schedule.

She glances at the screen after sending. Wrong group. She sent Ward A's schedule to Ward C's head nurse.

She recalls the message. Resends it to the correct channel. Types a quick apology. But the Ward C head nurse already screenshots the error and forwards it to two nurses. Those two nurses adjust their shifts based on the wrong information. By the time Elena catches the downstream confusion, six hours have passed. One nurse shows up for a shift she was never supposed to work. Another shift sits empty. It takes a scramble of phone calls and a favor from a float pool to patch things together.

Nobody gets written up. Nobody blames her. But that night, driving home on Lake Shore Drive with the windows down, Elena grips the steering wheel and turns the same thought over and over: I live in two worlds at once, and I am the most fragile interface between them.

Three people. Three industries. Three cities. Three entirely different shapes of pressure. And yet the same low-grade fever runs through all of them: the persistent, humming conviction that if they put their phone down, something will fall apart. The conviction is not a personal failing. It is a structural feature of the role they occupy. The role was designed to be always on.

Why Managers Can't Disconnect: The Invisible Scripts Running in the Background

Each of them tried, at different points and in different settings, to articulate what was actually driving the compulsion to check, respond, stay available. None of the answers landed on "I love my job" or "I'm a control freak." The answers were quieter than that, and harder to shake.

Maya's explanation came closest to engineering language. Async culture, she said, was supposed to liberate time. Everyone works at their own pace. No need to be online simultaneously. In practice, though, when twelve people across four time zones are each moving at their own speed, the burden of making sure everyone is still aligned falls on one person. Her. Her output is no longer code reviews or architecture decisions. Her output is the perception that the team is aligned. A Slack message left unanswered for three hours reads, to the organization, as a dropped signal. She must remain online because "being online" is the service she delivers.

She calls it a perception-management tax. Most of her day is spent maintaining the illusion that information is flowing smoothly. And maintaining that illusion requires her green dot to stay lit. Always.

David's explanation used a hardware metaphor. Overclocking. The AI tools genuinely save time. But the saved time doesn't become rest. It becomes another round of output. The baseline was three pieces a week. The tools make three pieces a day look possible. So the expectation becomes three pieces a day. His cognition runs like a CPU with its clock speed cranked up: performance is technically higher, but the thermal throttling never kicks in because nobody asks whether the chip needs to cool down. "Faster" is assumed to be correct. Nobody interrogates "faster."

What exhausts him most, he realized, is not the volume. It is the psychological cost of verifying each output. The AI text looks plausible. But every phrase has to pass through his judgment: does this sound like us? Is this claim accurate? Is this the voice we'd use in front of a customer? That verification pass is more tiring than writing from scratch. The tool eliminated typing time. It multiplied thinking time.

Elena's script is physical. Her body must be in the corridor. Her attention must be on Teams. Both demands arrive simultaneously, with no priority ranking and no transition gap between them. She used to consider multitasking a skill, even a point of pride. Around that time, the migraines started. Three weeks of them, relentless, pressing against the back of her eyes. Her doctor asked a simple question: "How much of your day do you spend focused on only one thing?" She thought about it. She could not answer.

She told a friend later: "Humans don't have parallel ports. You think you're doing two things at once. You're actually switching back and forth at high speed, losing a little something with every switch. After enough switches, you do both things poorly. And you come apart."

Seeing the script clearly did not fix anything overnight. No one wakes up on a Monday and announces, "Starting today, I don't answer messages." But seeing it changed one thing. It replaced the question "Am I too weak?" with a different one: "This structure is designed this way, and I happen to be standing in the position where the pressure concentrates." The self-blame loosened. And where self-blame loosens, a small space opens for experimentation.

Digital Boundaries for Managers: Real Experiments in Reclaiming Attention

Maya's first experiment was pure engineer instinct: solve a rules problem with better rules.

She wrote automation scripts that hooked into Slack and Linear's APIs. Non-urgent channels went silent after eight in the evening. Non-critical Linear notifications bundled into a single summary email delivered at nine the next morning. She set her phone to a focus mode that allowed only phone calls and messages from two specific contacts to break through.

The first week felt like a revelation. She slept through three full nights. Mornings came with a clear head.

Then, on Thursday of the second week, something broke. The night before, two senior engineers had spent forty minutes in a Slack thread hashing out an architecture direction. They hadn't tagged her because the discussion wasn't "urgent." By the time her nine-a.m. summary email arrived, the decision had already moved into execution. Her team was assigned a technical approach she disagreed with, and her silence had been read as consent.

She killed every filtering rule that same evening. The panic was too familiar: the gateway is down, traffic is uncontrolled, everything is scattering.

But she did not fully revert. Over the next few days she built something clumsier and more durable. Every day from two to four in the afternoon, she blocks her team's shared calendar with the label "Offline – Deep Work." During those two hours she does not look at her phone, does not open Slack, does not handle anything below a P0 severity. The critical difference: the absence is public and predictable. The team knows she is gone. The team knows she will be back at four. "Offline" stops being a guilty escape and becomes a scheduled protocol, written into the calendar, visible to everyone.

She calls it predictable absence. It does not solve everything. During sprint pushes she still works late. She still catches herself scrolling Slack in bed. But she added one rule for herself: if she works more than two hours past her normal end-time two days in a row, the third day she takes a full morning off. No work apps. No email. She calls it paying down technical debt. You don't have to die when the balance is overdrawn. You just need a repayment plan.

David's experiment went in a completely different direction.

He tried a digital sabbath first. Every Saturday: no phone, no laptop, no screens of any kind. The first Saturday was genuinely peaceful. He took his daughter to a park. He and his wife cooked dinner together. He felt human again. Then Sunday evening arrived. He sat down, opened his phone, and found nearly fifty unread messages. He spent four hours reading every single one, replied to more than thirty, and ended the night more anxious than if he had never disconnected at all. Like someone who fasted for two days and then charged into a buffet, grabbing everything.

He abandoned the full-disconnect approach. Replaced it with something smaller: physical anchors.

When he drafts initial copy, he no longer opens Notion. He pulls an old Smith-Corona typewriter out of a closet. His father's. The machine has no undo, no possibility of writing a sloppy sentence and fixing it later. Every letter commits to the page the moment it lands. This forces him to finish a thought in his head before his fingers move. His first drafts take longer to produce. But their quality is higher, and more importantly, his attention has exactly one place to be: the line of type in front of him. No pop-ups. No red badges. No temptation to "just check one email."

Before meetings, he stopped generating agendas with AI. He takes an index card and a pen and writes three lines: What problem are we solving? What do I need from the people in the room? What do I want to walk out with? Three lines. Then he goes into the meeting. The act of handwriting is a speed bump. It collapses infinite scroll into three sentences.

None of this fixes the underlying problem. He still gets pulled into AI-tool notifications at midnight. He still loses focus at the dinner table. But he has developed a discrimination he did not have before. Before every click on a "generate" button, he pauses for ten seconds and asks: where did this idea actually come from? Was it mine, or did the algorithm feed it to me? Ten seconds will not save an industry. But they let him keep a small, necessary feeling: this is still my voice. He does not want to lose that feeling. And the ten-second pause is how he protects it.

Elena's experiment started after the scheduling incident.

The week after the error, she called in sick. Not a mental-health day framed in HR language. A real fever. The migraines came back. She could not get out of bed. Her supervisor approved two weeks.

The thing she had been most terrified of happened during those two weeks: nothing happened. The team did not collapse. The deputy supervisor covered the scheduling. Meetings got held. The system continued to function without her node. She had believed she was load-bearing. She was decorative. Remove her and the building still stands.

The realization was not relief. It was a complicated, shame-tinged clarity: I bound myself so tightly partly because the work genuinely needed me, and partly because I needed the feeling of being needed to confirm that I mattered.

When she returned, she did one small thing. Every time she leaves her desk, whether to walk the corridor, attend a meeting, or go home for the evening, she writes three lines on a sticky note: Where the current task stands. What the next step is. Who to contact if something urgent comes up. She sticks the note to her monitor and photographs it into the team's Teams channel.

This is not a management methodology. It is a physical permission slip that says: I am leaving, and the work continues without me. It tells her colleagues the thread has not snapped. It tells herself the sky has not fallen.

Her phone still buzzes on weekends. She set a rule: non-urgent messages get a four-hour delay before she opens them. She does not hit the mark every time. Sometimes the screen lights up and her thumb moves before her brain can intervene. But the act of allowing herself to wait, even imperfectly, is the largest freedom she has given herself in years.

She told a friend: "I used to think a boundary was a wall. Build it once and you're done. Now I think it's more like a fence. The wind knocks it down. Something crashes through it. You repair it. You don't need it to never fall. You just need to keep fixing it."

Manager Burnout Recovery: From Perfect Balance to Honest Boundaries

All three of them now live in a state that is imperfect but lucid.

Maya still feels the anxiety during sprint pushes. But she has learned to name it: "That's the gateway-overload feeling." Once it has a name, she can choose to act on it, set it aside, or simply let it pass. The choice, previously, did not belong to her.

David still gets seduced by the tools. But he pauses before every generation. Ten seconds. One question: is this thought mine, or was it handed to me? Ten seconds will not reshape an industry. They will let him keep the feeling that he is still the one creating. That feeling, he has decided, is non-negotiable.

Elena still occasionally sends a message to the wrong group. Still occasionally fields two phone calls while walking a corridor. But she no longer reads every small mistake as proof that she can never step away. She accepts that a boundary requires ongoing maintenance. Today it holds. Tomorrow something punches through it. She fixes it again.

None of them "solved" the problem. If solving means never being interrupted by a notification, never drifting during a family dinner, never feeling torn between two simultaneous demands, then no one solves it. What they did is smaller and harder. They converted "always on" from a default setting into an active choice. The system used to decide when they were present and in what form. Now, at least part of that decision belongs to them.

Even when they choose wrong, it is their choice.

Reclaiming Attention at Work: Small Shifts Toward a More Human Digital Life

If you have ever been jolted awake by a notification that turned out to be nothing, and then sat in the dark holding your phone for twenty minutes.

If you have ever sat at a dinner table while someone you love talks to you, your fork full of cold food, your mind somewhere else entirely.

If you carry a quiet, constant hum that says if I put this phone down, something will fall apart, but you cannot name what, exactly, would fall.

You are not alone. You are not undisciplined. You are standing in a role that was designed to be always on, and that role happens to sit directly in the seam where every organizational gap needs someone watching.

You do not need a grand disconnection plan. Maybe you block one afternoon on your calendar, write "offline" in the description, and actually close the laptop. Maybe you pause for ten seconds before opening a generation tool and ask where the idea came from. Maybe you write three lines on a sticky note before you walk away from your desk, telling your team the thread holds and telling yourself the sky holds.

None of these are solutions. There is no permanent solution. They are a signal you send to yourself: I am still here. I choose when to be here, and how.

Technology will keep evolving. Notifications will keep arriving. Algorithms will keep refining the question of how to earn one more glance.

But the human need for quiet, for presence, for right now I belong only to this place and this person will not be overwritten by any version update.

The real upgrade has always been a clearer choice.

Continue Exploring

References

Eurofound. Right to disconnect: Implementation and impact at company level. 2023. https://www.eurofound.europa.eu/en/publications/all/right-disconnect-implementation-and-impact-company-level
Microsoft. Work Trend Index. Microsoft WorkLab. https://www.microsoft.com/en-us/worklab/work-trend-index?msockid=2ab327b4fce866f0014a316ffd0c671d