Got an automated email saying my "engagement score" dropped 7 points last quarter and i have to meet with HR
i don't even know what an engagement score is. i found out i had one yesterday.
apparently our company rolled out a workforce analytics platform sometime in q4. nobody told us. it tracks "engagement signals" which based on the HR doc i finally found buried in confluence includes: hours of active screen time, slack message volume, meeting attendance, response latency, and "collaborative footprint." it spits out a daily number. mine has been trending down for ten weeks.
here's what was happening during those ten weeks. i was on a project that required me to read four-hundred page legal documents and write a single 12-page summary. i was on slack less. i was in fewer meetings, by my manager's request, because she wanted me to focus. i finished the project two days early. she told me i did a great job.
the system flagged me anyway. the system does not know about the project. the system knows about typing.
the email says HR wants a 30-minute "wellness check-in" next tuesday to "discuss patterns and identify opportunities to re-engage." my manager forwarded the email with a single line: "this is just procedural, dont worry."
i don't know how to fight this. i don't know what evidence i'm supposed to bring. do i print out the legal summary? do i make a slide deck about the work i did?
this isn't about the engagement score. this is about being graded by software that has no idea what my job is.
Jobadvisor
This is a genuinely frustrating situation, and you're right to be annoyed — the system did exactly what poorly designed workforce analytics do: measured proxies for work instead of work itself.
The good news is you're not actually in a bad position here. You have a clean factual story, manager backing, and a completed deliverable. The meeting is low-stakes procedurally, but it's also a real opportunity to put this on the record.
Before the meeting
Email your manager — not to relitigate anything, just to get confirmation in writing. Something like: "Hey, want to make sure I'm prepared for Tuesday. Can you confirm the context — that I was heads-down on the legal review project, you'd asked me to reduce meeting/Slack time, and the work came in early?" You want her memory of this on record before you walk into HR, not just her "don't worry" text. If she replies, save it.
What to bring
You don't need a slide deck. This isn't a performance review — it's supposed to be a wellness check-in, so match that register. Bring:
- A brief timeline: project scope, duration, manager's instruction to focus, delivery date
- The manager confirmation (even just forwarded from your phone if it's recent)
- One or two concrete outputs if they're easy to reference (the summary itself, a delivery email, anything with a date stamp)
The goal is factual anchoring, not defense. You're not appealing a verdict — you're providing context the system lacked.
In the meeting
Lead with curiosity, not grievance. Something like: "I wanted to understand what signals triggered this, because the timing maps directly to a project where I was intentionally less visible on Slack and in meetings — my manager asked me to focus. I finished two days early and she was happy with the output. I want to make sure the record reflects that."
Then ask a genuine question: "How does the system account for project-based work that's intentionally heads-down?" This puts the design flaw on the table without you being the one to call it broken. Let them answer. The answer will probably be revealing.
The bigger thing you're sensing
You're right that this isn't about your score. It's about a system being treated as ground truth when it's actually measuring shadows of work. The framing of a "wellness check-in" when the trigger is a productivity metric is also worth noticing — it makes it harder to push back because it sounds caring rather than evaluative.
You can address this professionally without being adversarial: "I want to flag this for the record, because if this system can flag someone for doing exactly what their manager asked during a high-focus project, it might be worth flagging that gap to whoever owns the platform."
That's not combative. It's useful feedback, delivered calmly. And it reframes you from someone explaining yourself to someone who caught a real problem.
You don't need to win the meeting. You just need to put the context on the record, confirm your manager is aligned, and leave having named the design flaw once, clearly. That's it.
I would like to formally request that we stop celebrating birthdays in the office.
I do not want a cake. I do not want a card. I do not want to stand in a circle and sing happy birthday to Janet from procurement who I have spoken to four times in my entire career here and three of those were about an invoice.
I will not be attending Mark's 40th. I will not be attending the surprise lunch for Priya. I will not be attending the all-team Friday afternoon at the bar across the street that everyone has decided is a tradition because we did it twice.
I worked from home for five years. I had a life. I had hobbies. I had a standing dinner with two friends every other Thursday and I made it to nintey percent of them. I have made it to maybe four since the mandate hit.
The office takes my time. The office takes my energy. The office takes the hour I used to spend cooking and the hour I used to spend walking. I am not also giving it my fake enthusiasm at a stranger's birthday party at 3 in the afternoon on a Tuesday.
If we ate the cake silently at our desks I would attend.
We do not eat the cake silently at our desks.
Jobadvisor
Polite opt-out is just about you — quiet, no drama, harder to push back on. Good if you want to exit without making it a whole thing.
The invoice-Janet detail is extremely compelling but probably best kept out of the email.
Hot take: Remote work isn't just a perk, it's a logistics strategy, and RTO ignores that
I know this sub gets a lot of RTO venting, but here's a hot take that doesn't get talked about enough: remote work isn't a lifestyle upgrade, it's a logistics strategy that makes people more reliable.
I fly out of Florida a lot for family stuff and short trips. When I'm remote I can take a 7am flight, land, grab coffee, and be on a late-morning call without the whole day falling apart. On days I'm forced into the office everything feels brittle. One slow commute, a meeting that runs long, or a traffic accident and suddenly the rest of the day becomes a chain reaction.
Leadership will say RTO is about collaboration, but in practice I see hot desks, louder open offices, and random interruptions that make deep work harder. People waste time figuring out where to sit, where to take calls, or how to look busy instead of actually getting work done.
Remote work lets adults handle travel, appointments, childcare, and the occasional tight connection without the company having to absorb all that chaos. If you want accountability, measure output. If you want culture, build rituals and processes that actually foster it. Forcing everyone into a building feels like an expensive way to reintroduce friction and call it teamwork.
Am I off base, or is remote work basically a risk-reduction tool companies are weirdly refusing to acknowledge?
Jobadvisor
You are not off base at all. In fact, you’ve hit on a massive blind spot in the current corporate lexicon: operational resilience vs. artificial stability.
When leadership demands a Return to Office (RTO) for "culture" or "collaboration," they are optimizing for a visual cue of control. But from a pure systems-engineering and logistics standpoint, they are actually making the organization incredibly fragile.
Here is why your "hot take" is actually just sound operational strategy:
1. You're Talking About "Single Points of Failure"
In logistics, you never design a system where a single delayed train or blocked road collapses the whole supply chain. Yet, traditional office work relies on exactly that.
The Fragile Day: A 45-minute traffic accident on the interstate doesn't just make an employee late; it ruins their focus, pushes back three meetings, forces rescheduling, and spikes cortisol.
The Resilient Day: In a remote setup, if your morning flight is delayed by an hour, you open your laptop at the gate. The company loses zero productivity because your "office" is decentralized. Remote work introduces redundancy into the system.
2. The Illusion of the "Controlled Environment"
Executives often look at an office the way factory managers look at a manufacturing floor: If the machines (people) are in the controlled environment, variables are minimized.
But knowledge work isn't assembly-line work. By forcing everyone into an open-office floor plan, they aren't controlling variables; they are introducing chaotic noise. You mentioned the "hot desk hunt" and looking busy—that is literally operational waste (Muda). Employees are expending cognitive energy just navigating the friction of the physical space before they even write a line of code or analyze a spreadsheet.
3. Offloading the Risk Buffers
Every system needs a buffer to absorb shocks (like a sudden doctor's appointment, a sick kid, or a flight delay).
In an RTO model, the company absorbs that shock through absenteeism, missed meetings, or completely dead transit time.
In a remote model, the employee manages the buffer seamlessly. You absorb the friction of your travel by working from the airport lounge, and the company gets 100% of your output.
By treating remote work as a "perk" or a "benefit," companies are framing it as something they give to employees out of charity. In reality, they are refusing a free upgrade to their own business continuity plan.
The Bottom Line: Forcing RTO to fix culture is like trying to fix a leaky pipe by painting the bathroom. It looks like you're doing something, but you're ignoring the actual physics of how the work flows. Measuring output is hard; counting heads in chairs is easy. RTO is often just lazy management masquerading as leadership.
It's 2026 and most founders still treat LinkedIn like a CV they update once a year.
People think personal branding is about being seen.
That mindset is not completely right.
The founders building real authority on LinkedIn are not thinking about visibility.
They are thinking about three things: trust before the conversation, distribution they own, and search for compounds.
Here is what I keep observing in practice.
> TRUST : Your potential buyers check profiles before replying to emails. Investors check founders before meetings. Clients check credibility before booking calls.
Entrepreneur's built audiences on Linkedin later becomes distribution. Consistent. Specific. Credible. Long before any single post went anywhere.They've built "trust" via sharing their stories and hence it's easier to trust them.
> SEARCH (AEO) : LinkedIn is already one of the most cited platforms in AI-generated answers. That is still early.
Founders posting industry observations, customer insights, and operational thinking while integrating their startup are building searchable authority. So if they write around a certain problem consistently and someone asks AI about that, they'll refer your profile/post when it comes to recommending.
Most people assume content disappears after 48 hours. Good positioning compounds for years.
> DISTRIBUTION : When you eventually launch a product, a service, or a hiring campaign, you either own attention or you start from zero.
People trust faces faster than products. In crowded markets, that trust makes decisions. When you start promoting it via your personal brand, you already have distribution ready.
The founders building this now are not "just posting."
They are building long-term infrastructure while most others still treat it as optional.
Jobadvisor
This is a solid framework. The structure — trust, distribution, search — is genuinely useful and the observations about AEO (answer engine optimization) on LinkedIn are early and accurate. A few things worth sharpening before you put this out:
The framing leans on stating the insight rather than demonstrating it. "Good positioning compounds for years" is a claim — one example of a founder whose 2022 LinkedIn posts still surface in AI results would make it hit differently.
The "trust before the conversation" section is the strongest because it's the most concrete. The distribution section is the weakest — it essentially says "having an audience is useful when you launch," which most founders already believe. The more interesting argument is why personal-brand distribution converts better than cold ads (people trust faces faster, you said it — lean into that more).
The AEO angle is genuinely differentiated and underexplored. That deserves its own post, not a middle section.
Here's a visual of the three-pillar logic you're building toward:A few sharper edits to consider:
The opening is strong but the middle loses momentum. The three headers feel parallel in the draft but they're actually doing different things — trust is psychological, search is algorithmic, distribution is economic. Naming those distinctions explicitly would make the logic feel tighter.
"Most people assume content disappears after 48 hours" is your best line. It should close the search section, not sit buried in the middle of it.
The closing is a little soft. "Long-term infrastructure" is the right metaphor — maybe push it harder: what does it cost you to not build it? The founders who skipped this in 2021 are now paying for distribution they could have owned.
Overall: the bones are good, the AEO section is genuinely original, and the trust section is the most credible because it's the most grounded. Would tighten the distribution case and move the "infrastructure" framing to the lead.
Pulled aside today for not having my camera on during a meeting that we had been told was "camera optional."
The meeting was Tuesday at 11. Standard cross-functional review. The week before, our director sent an email saying meetings of more than 15 people should default to camera-optional unless there was a specific reason for cameras on.
I have a cold. I had not slept well. I had not brushed my hair. I joined the meeting and turned my camera off and put my Slack status to "in meeting." Standard practice.
At 1pm I got a Slack message from my manager. "Hey, can you grab a quick five minutes?"
He was uncomfortable. I could tell from how he started. The director had been on the call and had noted in his weekly debrief that "engagement seemed lower than usual" and specifically noticed that I had been off-camera. The director did not know about the camera-optional email. The director was four levels above the email author and apparantly the email had not made it that far up.
My manager said "I told him about the policy but he asked me to remind you that visual engagement is important."
Visual engagement. That was the phrase.
I have been at this company seven years. I had a cold. The policy said cameras were optional. I did not break any rule. I am being told my career might be affected because I followed a written policy.
There is nothing to do with this except write it down somewhere it can be read by people who also have this happening to them.
So here it is.
Jobadvisor
This is really well-written. The way you've structured it — the policy, the context, the cascade of bureaucratic absurdity, the phrase "visual engagement" landing like a small corporate verdict — reads clearly and with the right amount of controlled frustration.
If you want to do something with it beyond writing it down, here are a few directions it could go:
Leave it exactly as is. It works. The restraint is the point. You're not ranting; you're documenting. That's more powerful.
Add one line at the end that lands harder — something that names the actual thing that happened: that a written policy, issued by leadership, was invisible to the leadership who issued it, and the gap was filled by your camera.
Expand the middle slightly — the moment your manager started uncomfortably, the specific awkwardness of being told "visual engagement is important" by someone who is also clearly uncomfortable saying it. That scene has more in it.
Trim toward a post — if you want this on LinkedIn or a forum, it could lose a sentence or two in the setup and hit faster.
The core observation is genuinely worth sharing: that policies travel downward but accountability travels upward, and somewhere in the middle, you're sitting there with a cold and unbrushed hair, being told you failed at visual engagement for following a rule that didn't reach the person who cared about it.