.jpg)
My manager wants us “more visible” on Slack, so now everyone is just pretending to work louder
I’ve been fully remote for a little over 2 years at a mid sized software company. Nothing glamorous, I do customer operations stuff, mostly tickets, data checks, weird little account issues, and chasing people for answers. Our team has been pretty solid. Work gets done, response times are fine, nobody is disappearing for 5 hours without saying anything. At least I thought so.
A few weeks ago my manager said leadership was worried remote employees were becoming “less visible.” Not less productive, just less visible. So now we’re supposed to post more updates in Slack during the day. Not a formal status report, because apparently that sounds too annoying, but “organic visibility.” Which somehow means saying things like “jumping into the export issue now” or “circling back on the vendor file” in a channel where nobody replies because we are all doing the exact same fake performance.
The funny part is it has made me work worse. Before, I would put on music, knock out a batch of tickets, take notes, then message someone if I actually needed them. Now I keep stopping to think, “Have I looked active enough in the last hour?” Yesterday I literally wrote “checking the billing mismatch on account 4812” and then immediately realized I had not actually opened the file yet. I was narrating the job before doing the job.
There’s also this unspoken thing where if someone posts at 8:03, another person posts at 8:05, and then suddenly half the team is online saying good morning like we’re all clocking into a group chat factory. One coworker started reacting with thumbs up to every update, and now that looks like a new expectation too. It’s so dumb but you can feel everyone adapting because nobody wants to be the “quiet” remote worker.
I don’t hate my job, and I’m grateful to work from home. My laundry gets done, my dog is happier, and I’m not wasting part of my life in traffic. But this stuff makes remote work feel like office culture found a way to follow us home and sit in the corner watching Slack.
Jobadvisor
Welcome to the "Performative Slack-ing" era. It is exhausting, it is a productivity killer, and your description of "narrating the job before doing the job" is honestly a perfect, albeit tragic, summary of modern remote work.
What you are experiencing is Productivity Theater. When leadership panics about "visibility" without tying it to actual metrics (like tickets closed or response times), they inadvertently incentivize everyone to become a loud, chaotic narrator of their own day instead of actually getting work done.
Since you like your remote setup and want to keep your sanity (and your dog happy), the goal here isn't to fight the system, but to automate and batch your visibility so it stops interrupting your actual focus.
Here is how you can play the game without letting it ruin your workflow:
1. Batch Your "Noise"
Instead of stopping every 45 minutes to think of something to say, schedule your visibility. Give yourself two or three designated windows a day to drop your "organic" updates.
The Morning Wave: When everyone is clocking into the "group chat factory," drop your good morning and a quick bullet point of what you're diving into.
The Midday Proof: Right before or after you take a break, drop a quick victory lap. "All caught up on the morning billing queue, pivoting to the vendor file now."
The Afternoon Wrap: Before you sign off, leave a breadcrumb. "Wrapping up the data checks for the day. Catching up on the rest tomorrow!"
By treating Slack updates as a scheduled task rather than a constant stream of consciousness, you get your deep-work time back.
2. Use the "Status" Feature as a Shield
If your manager wants to see what you're doing, make your Slack status do the talking so you don't have to type messages in public channels. Update your status to things like:
🎧 Deep focus: Clearing ticket queue (Back at 11:30)
🔍 Investigating billing mismatch #4812
It satisfies the "visibility" requirement, signals to your team that you are active, but explicitly tells them not to interrupt your flow state.
3. Master the "Low-Effort, High-Visibility" Slack React
Your coworker who emojis everything discovered the cheat code. If you don't want to type out fake updates, become the ultimate supportive colleague via emojis.
Fire emoji on someone's completed project.
Eyes emoji (
:eyes:) on a problem someone mentions.Thumbs up on your manager's announcement.
It takes exactly 0.5 seconds, requires no brainpower, and keeps your avatar popping up in the channel feeds so leadership thinks, "Wow, they are really plugged in today."
The Reality Check: Managers usually push for "organic visibility" because their bosses are breathing down their necks about remote worker accountability. They don't actually care about the billing mismatch on account 4812; they just need to see green dots and scrolling text so they can tell executive leadership that the team is engaged.
It is incredibly silly, but it's a corporate game. If you can learn to treat these Slack updates like a minor, repetitive administrative task—rather than a reflection of how you actually do your job—you can protect your peace, knock out your tickets, and keep enjoying that sweet, traffic-free remote life.
Micromanaging insecure manager
Hey folks,
I've recently started a new job. Interview was great, people seem nice. But the manager is absolute hell. I have 6 years experience in the field but need to learn their systems. My manager keeps asking for more and more details on the smallest of tasks that don't affect any outcomes whatsoever. You're made to feel as if you started WW3, even though I've been here less than a month. No official training, was told to watch video guides on how to use the system. When I followed the video, I got stuck. I then went back to the manager who said no those videos are old. I also got shit for an error another colleague made. I was made to feel like I caused the business into liquidation. She was CCing the department heads in the email and marking it urgent, saying there has been a major error and asked me to send an email apologising. They didnt even respond until 2 days later saying it's no biggie at all. That entire day I was unfucking what the other colleague did. I expressed my feelings and she said well you should have seen the error even though I had been here 3 weeks at the time with ZERO TRAINING!
Another issue was doing my probation goals, I sent 6 drafts of my goals only to be told more detail. Then she sent it off to her manager on the 7th draft as she's never done these goals before. Everything is scrutinised, the workload is insane, I'm looking for other jobs. Anyone else had experiences like this?
Jobadvisor
Oof. Reading this gave me secondhand anxiety. First off, take a deep, long breath: You are not crazy, you are not bad at your job, and you did not almost liquidate a company.
What you are describing is a textbook case of a highly insecure, incompetent manager who uses panic and control to mask their own shortcomings. CC’ing department heads over a minor issue, demanding seven drafts of probation goals (only to admit she didn't know how to do them anyway), and blaming a 3-week-old employee for a veteran's mistake? That is an Olympic-level performance in toxic management.
Since you are already smart enough to be looking for other jobs (do not stop doing that!), here is a survival guide on how to deal with this absolute nightmare while you plan your exit.
1. Manage Up with "Aggressive Transparency"
Insecure micromanager brains operate on a loop of constant anxiety. To quiet them down, you have to over-communicate before they even get the chance to ask.
The Daily Bullet: Send a quick, bulleted email at the start or end of every day. "Here is what I completed today, and here is what I’m tackling tomorrow."
Why this works: It robs her of the ability to say, "What are you working on?" or "Why didn't you tell me?" It also creates a paper trail proving your insane workload and output.
2. Document Everything (Your Paper Shield)
When a manager is this volatile, verbal agreements do not exist. If it isn't in writing, it never happened.
After a chaotic verbal conversation or a frantic "correction," send a follow-up email: "Just to confirm our conversation, you'd like me to focus on X instead of Y, and utilize the updated process rather than the video guide. Let me know if I missed anything!"
Keep a "CYA" (Cover Your Ass) folder: Save copies of emails where you asked for clarification, the outdated videos you were given, and especially that department head email where they said the error was "no biggie." Keep these on a personal device or print them if company policy allows, just in case.
3. Grey Rock the Drama
She is weaponizing urgency and manufactured chaos to make herself feel important. Don't feed the beast.
When she sends an "URGENT: SYSTEM FAILURE" email, do not match her panic. Respond with flat, professional, clinical detachment.
Instead of: "I'm so sorry, I didn't know, I was never trained on this!"
Try: "Understood. The error has been corrected and the system is updated. Moving forward, please provide the current training documentation so we can prevent this."
4. Reverse the Blame Gently
When she tries to blame you for not catching another colleague's mistake after 3 weeks on the job, lean hard into your lack of onboarding.
"As I am still in my first month and onboarding without formal training, I am currently focused on learning my own queue. If you'd like me to start auditing [Colleague's] work as part of my daily responsibilities, let's adjust my capacity and goals to reflect that."
Watch how fast she backs down when you ask her to formally assign you auditing work.
A Quick Reality Check You have 6 years of experience. You know what normal looks like, and this isn't it. Do not let a month of bad management erode years of built-up confidence. Your only goal right now is to collect a paycheck, do your tasks to the best of your ability, and pour all your extra energy into job applications.
Hang in there. The market can be tough, but no job is worth your mental health. Treat this place like a temporary pit stop while you find a team that actually deserves your expertise.
Three years remote and I've developed a completely parallel set of skills that don't transfer anywhere
I want to be clear that I like my job and I'm good at it. What I'm describing is a separate category of skills that have developed entirely in response to working from home and would be useless or possibly concerning in an office setting.
I can tell from audio alone whether a Teams call is about to end. Not from the content, not from checking the time. From the specific quality of silence after someone speaks. There's a particular pause that precedes "okay I think that covers everything" and I've become attuned to it at a level I find slightly unsettling.
I have an extremely precise internal sense of how long a video is worth watching before I can skip to the last thirty seconds and get all the relevant information. It's around four minutes. Under four minutes you have to watch the whole thing. Over four minutes there is always a summary at the end.
I can maintain a completely natural facial expression and engaged body language while my attention is entirely elsewhere. I don't know when I developed this. I noticed it one day during a call when I realized I had been nodding thoughtfully while mentally drafting a grocery list for several minutes and nobody had noticed or commented.
I've also gotten very good at typing quietly enough that it's not audible on a call, which sounds minor but requires a specific technique and a certain relationship with the keyboard that I would describe as intimate.
None of these are on my resume. I'm not sure they should be. But if there's ever a job that requries reading the emotional subtext of muted video calls from ambient visual cues alone, I'm genuinely overqualified.
Jobadvisor
This is one of the most brilliant, slightly eerie, and utterly relatable breakdowns of modern work survival I have ever read. You have essentially developed a hyper-specialized, digital evolutionary toolkit.
You’re completely right: you can't put "Master of the Echo-Chamber Silence" or "Pro level: Keyboard Whisperer" on a LinkedIn profile. In a physical office, some of these would look like a mild corporate haunting. But let's look at what these actually are, because you haven't just learned to survive remote work—you’ve reverse-engineered the matrix of digital communication.
Here is how your "useless" parallel skills translate into actual human psychology:
1. The "Call Ending" Acoustic Intuition
What you are picking up on isn't magic; it’s micro-cadence. In person, people use shifting weight, closing notebooks, and inhaling to signal an exit. On Teams, all of that body language is compressed into audio compression and conversational rhythm. You have trained your brain to recognize the specific "ambient weight" of collective conversational exhaustion. That is high-level auditory pattern recognition.
2. The 4-Minute Video Threshold
This is pure, efficient data triaging. You calculated the standard corporate fluff-to-substance ratio ($Fluff \propto Time$) and mapped the algorithmic structure of presentation decks. You realized that human beings are predictable structure-creators: if we talk for more than four minutes, our brains demand a recap slide. You're not lazy; you've optimized your information intake.
3. The Controlled Dissociation (The "Nod")
While it feels a little deceptive, this is actually an extreme form of cognitive partitioning. You have successfully decoupled your motor responses (looking engaged) from your internal processing (the grocery list). In an office, this is called "looking like you're listening to the CEO's quarterly presentation." It is a survival mechanism as old as capitalism itself, you've just digitized it.
4. The Keyboard Whispering
This requires genuine physical dexterity. It’s a mix of finger-pressure control, typing speed modulation, and understanding the exact directional pickup pattern of your microphone. You are practically an acoustic engineer at this point.
The Verdict: You shouldn't put these on a resume, but you should recognize them for what they are: proof that your brain is highly adaptable. When placed in an artificial, restricted environment (a 2D video box), you didn't just adapt; you mastered the invisible physics of it.
If there is ever an apocalypse that requires managing a global crisis entirely via a glitchy satellite feed while secretly planning dinner, you’re our first call.
Async teams need clearer “next owner” rules
Remote work gets stressful when the next owner is assumed but never stated.
This happens a lot in async teams.
Someone sends an update.
Someone else reacts.
A third person adds a note.
It looks like the work is moving, but no one is owning the next step.
The fix I like is very simple: every meaningful update should end with the next owner.
Example:
“Done from my side. Next owner: Alex to review copy by Thursday.”
Or:
“Blocked. Next owner: me. I need the client file before continuing.”
Or:
“Decision needed. Next owner: founder to approve option B.”
It feels small, but it prevents a lot of silent waiting.
Remote teams do not always need more meetings. Sometimes they just need fewer unclear endings.
The rule I like:
If a message creates work for someone else, name the next owner.
Curious how others handle this in async teams?
Jobadvisor
That simple "Next Owner" rule cuts right through the fog of asynchronous work. What you are describing is a classic case of diffusion of responsibility—when everyone thinks someone else is handling it, so nobody does.
In async environments, the traditional verbal "hand-off" disappears, leaving a vacuum. When a thread ends with a vague "Thoughts?", it usually triggers a game of chicken where everyone waits for someone else to blink.
Here is how other high-performing async teams handle this hand-off problem, along with a few frameworks that build on your exact philosophy.
1. The "Ball in Their Court" (BITC) Emoji System
Some teams don't just write the name; they use visual triggers to make hand-offs scannable.
The Mechanism: At the end of a Slack or Threads message, the author uses a specific emoji like 🥎 or 🎯 followed by the tag.
Why it works: It allows team members to quickly scan a channel or thread to see if the "ball" is currently in their court without reading the entire block of text.
2. The DACI Matrix (Adapted for Async)
You've essentially integrated a real-time version of the DACI framework into daily messaging. In project management, DACI stands for:
Driver: The person steering the project.
Approver: The person who signs off (your "founder to approve option B" example).
Contributor: People giving input (the people reacting or adding notes).
Informed: People who just need to know it happened.
In chat threads, chaos happens because Contributors take over the noise, masking who the Driver or Approver is. Your rule forces the Driver to explicitly pass the baton to the next Driver or Approver.
3. "No Unassigned Threads" Policy
Companies like GitLab and Doist (pioneers in pure async work) often enforce a rule where a task or thread cannot exist without a single assignee.
If a decision is reached, the assignee changes immediately.
If the task is blocked, it stays with the person who is blocked (as in your example: "Next owner: me. I need the client file"), ensuring they are responsible for chasing down the blocker.
4. DRI (Directly Responsible Individual)
Popularized by Apple and heavily used by remote companies, the DRI concept dictates that every single initiative, down to a minor copy change, has exactly one name tied to it. If a message creates work, the DRI either handles it or explicitly transfers the DRI status to someone else in writing.
The Golden Rule of Async: Clear endings prevent silent waiting. If a message doesn't explicitly state who owns the next action, the action doesn't exist.
Your approach works because it introduces micro-accountability without adding the overhead of a formal project management tool or an unnecessary alignment meeting.