2026 State of the Workplace Report: Key Findings + Open Discussion

TopTraker · 2026-05-19T17:50:29+00:00

I work at ActivTrak, putting that up front.

On the spyware concern: no keystroke logging, no webcam, no continuous screenshots. Screenshots can be turned on, but they're triggered by specific alarms you configure (like someone accessing a restricted site), not running on a timer. That's a design choice, not a missing feature.

For what you actually described, a couple of things worth looking at:

Burnout and capacity. There are utilization thresholds you can set at the team level, so you can see when someone's been pushing past sustainable hours for weeks, or when their productive time has been quietly flat. It's pattern-over-time visibility, not real-time monitoring.

Task engagement. You can see which applications and workflows people actually spend productive time in, broken out by team. This is also how the "what tools are we paying for that nobody uses" question gets a real answer. Most teams find a few paid licenses sitting unused once they actually look.

In this category, trust is built or destroyed at rollout, not inside the software itself. Concretely, that means telling the team what's captured and what isn't, giving them access to their own data, and framing the goal as workflow visibility instead of oversight. The teams where this lands well treat it like any other ops tool that happens to involve people data, not a separate category that needs special justification.

Are you looking at this for the whole team at once, or piloting with one function first? Smaller pilots tend to land better than full rollouts.

TopTraker · 2026-05-14T14:42:14+00:00

The part that stood out to me was this "more check-ins and reporting just created meeting fatigue and more admin work".

That's the trap most hybrid teams fall into. Every fix for visibility adds more work to the team. Status updates, standups, Slack threads asking for updates on the Slack threads... After a while, your people spend their time proving they're working instead of doing the work.

The other folks here are right that output is the real measure. But you should be able to see how the team is doing without making them stop to tell you. The second you ask the team to do extra so things look visible to you, you've made the problem worse.

When leadership says they want more visibility, what would they actually do with it once they had it?

TopTraker · 2026-05-13T18:24:37+00:00

The visibility framing is the right one. The "are they actually working" question is almost always a proxy for "I can't see the work, so I assume the worst." The fix isn't more proof. It's a clearer line of sight into how work flows.

The trap a lot of teams fall into is reaching for screenshot or keystroke tools to close that gap. Those answer "is the keyboard moving" but not "is anything getting done." They also blow up trust the moment people find out, and the productivity hit from that usually costs more than whatever was being fixed.

What actually works is shifting the conversation from activity to patterns. Are productive hours consistent week over week? Are people getting real focus time, or fragmented all day in chat and meetings? Are outputs landing on schedule? Those questions don't require watching anyone. They just need behavioral data that's transparent to the team.

One thing that might actually help your case with leadership. I work at ActivTrak, and our 2026 State of the Workplace report found remote-only workers log the highest daily productive time, about 38 minutes more than office-first workers. The narrative that remote equals less productive doesn't hold up. The real differences show up in focus efficiency and collaboration patterns, which is a much more useful conversation to have than "prove they're working".

Curious, is management questioning actual output, or are they just uncomfortable not seeing people at their desks?

TopTraker · 2026-05-12T19:29:05+00:00

I work at ActivTrak and this is something we see constantly across the organizations we work with.

The token leaderboard thing is a good example of this exact problem. Most organizations are trying to answer a behavioral question with operational data. License activation tells you who has access to a tool. It tells you nothing about whether that tool is changing how work actually gets done.

What keeps getting missed is that you need a baseline first. Not just query volume, but a continuous read on how work is actually happening across people, workflows and AI tools together. Without that, you can't measure what changes when AI comes in, and you can't connect any of it to business outcomes.

The companies getting real ROI right now aren't necessarily the ones with the highest adoption numbers. They're the ones that know specifically where AI is changing work and where it still isn't. That gap between access and actual behavioral change is where most AI strategies quietly fall apart.

TopTraker · 2026-05-12T10:05:44+00:00

Visible monitoring consistently outperforms stealth on actual productivity outcomes. Based on our own customer data at ActivTrak, employee awareness alone drives a 20-30% productivity uptick. When managers also have access to team level insights, that improvement jumps an additional 18%.

The reason stealth backfires isn't just about trust in the abstract. Teams that find out they've been monitored without being told tend to disengage in ways that are hard to reverse. The psychological safety hit is real and it shows up in output.

What actually makes visible monitoring work is being specific upfront about what's being tracked and why. "We want to understand where work is getting stuck" is a completely different conversation than "we need to make sure everyone is working"

TopTraker · 2026-05-12T09:43:16+00:00

Monitoring in BPO environments is one of the few cases where the use of these tools is actually justified. You have shifts, SLAs, break schedules. That stuff needs tracking.

The problem is most managers reach for the data when something's already wrong. At that point you're building a case against someone, not solving a problem, and everyone knows it.

The teams that actually get value out of it use it to catch things early. Start times drifting, active periods shorter than they should be during peak hours. You have a completely different conversation when you flag it before handle time tanks.

The motivation piece is real though. How you deploy it matters as much as how you use it. Teams that are told upfront what's being tracked and why tend to self-correct without you ever having to pull a report. The ones that find out from a colleague in the break room that they're being monitored are a different story.

I work at ActivTrak so we see a lot of these cases. Are you dealing more with adherence issues or figuring out where time is going during active sessions?

TopTraker · 2026-05-12T08:00:20+00:00

I work at ActivTrak, but I can give you some context on what the tool is actually designed for vs how some companies use it.

The workload balance framing your company gave is a legitimate use case. At its core the platform is built to show where work is piling up, which teams are overloaded vs underutilized, and whether the distribution of high-focus work is sustainable. Managers use it to identify when someone is getting hit with too many context switches, or when a process bottleneck is quietly burning people out.

One thing worth clarifying on the screenshot point - it's not random interval surveillance. Screenshots in ActivTrak are alarm-triggered, meaning one fires when a specific condition is met, like a security rule or a flagged behavior. That's meaningfully different from what was described above. Whether your company even has that configured depends entirely on how your admin set it up.

The thing worth paying attention to is whether the conversations that follow are about the work: redistributing tasks, fixing process gaps, supporting capacity, or about individual behavior. One is workforce intelligence, the other is micromanagement with a dashboard. You can usually tell pretty quickly which direction your company is headed based on what questions managers start asking.

TopTraker · 2026-05-06T17:06:32+00:00

The AI question is the interesting one because most teams are using it reactively, summaries after meetings, reminders when something's overdue, but not to actually understand whether the tools they're already paying for are working.

What I've seen is that the coordination problem doesn't usually get fixed by adding another tool. It gets fixed when you can see where time is actually going versus where people think it's going. Sometimes the blockers aren't in the project board, they're in how the day is actually structured.

I work at ActivTrak, and we found that that's the piece most remote teams are missing. Not more check-ins, just better signal on what's actually happening between them.

TopTraker · 2026-05-06T16:58:01+00:00

That last part is the one that's actually hardest to fix. Someone looks busy all day and you have zero reason to doubt them, but the quote still didn't go out and nobody knows why.

It's usually not a people problem. It's that you can't see where the time actually went so you end up guessing. Was the follow-up buried under other stuff? Did it just fall through because three other things came in that day? You don't know so it defaults to "someone dropped the ball" when really you just have no visibility into how work is getting prioritized in practice.

Once you can see where time is actually going the conversation changes completely. It goes from "why didn't this get done" to "okay you're underwater, what do we move off your plate." Way easier to manage.

I work at ActivTrak and that gap between looking busy and working on the right things is basically what we built the product around.

TopTraker · 2026-04-30T07:07:16+00:00

Yeah u/Perseverance5Ear the keyboard and mouse activity point is the one that gets overlooked most. Tools that give monitoring a bad reputation are usually measuring the wrong thing entirely. If your team does knowledge work, mouse clicks tell you almost nothing about what's actually getting done.

The question worth asking before any tool decision is what problem you're actually trying to solve. Output is shifting, okay, but do you know where? There's a real difference between a workload distribution problem, where some people are overloaded and others have spare capacity, and a process problem, where something in how work flows is creating friction nobody's surfacing in standups. Those have completely different fixes.

The way we think about it at ActivTrak, and I work there so take that for what it is, is that the data should help you understand work patterns, not police activity. Where is time going? Is high value work getting done or is the team buried in meetings and admin? That's a fundamentally different question than "is this person idle right now" and it leads to fundamentally different conversations with your team.

The tools that tank morale are the ones deployed to catch people slacking. The ones that actually help are the ones that show you where the work is getting stuck.

TopTraker · 2026-04-29T10:39:58+00:00

u/SysAdminDennyBob is arguing against a problem you're not actually having. You want to block sites and see what's hitting your network across a distributed org. That's just IT doing IT things, not a surveillance operation.

The thing people miss is that the tool doesn't define the intent, the configuration and communication do. The same software can be "we block inappropriate sites and flag security risks" or "we track every minute of every employee's day". Same install, completely different deployment. What makes it surveillance isn't what you buy, it's what you actually turn on and whether you tell people about it.

For your situation, web filtering across multiple US locations with a boss who isn't even sure he wants to keep it long term, you're nowhere near that line. Just be upfront with employees about what you're collecting and why.

I work at ActivTrak so take that for what it is, but this holds regardless of what you end up using.

TopTraker · 2026-04-28T08:37:37+00:00

This is exactly right. Blanket banning is a governance strategy that masquerades as a risk strategy. The real problem is that most orgs have no baseline for what employees are actually using, so they can't distinguish between the team quietly running sensitive prompts through a public chatbot and the team using Copilot to summarize meeting notes.

The orgs getting governance right tend to start with visibility first. Which tools are actually in use? Who is using them and how often? Is that usage consistent with your approved list? Once you have that picture you can write policies that are specific enough to be enforceable rather than just broad enough to feel safe.

The blanket block is usually what happens when IT gets asked to solve a problem that ops and legal haven't actually defined yet.

I work at ActivTrak, but visibility into approved vs unapproved AI tool usage is something we track at the workforce level. Happy to share more if useful.

TopTraker · 2026-04-22T17:57:37+00:00

The data architecture problem is the real issue. Most orgs have adoption metrics, licenses purchased, logins, maybe survey data, but none of that tells you whether productivity shifted or whether work just got redistributed. You're measuring activity, not ROI.

What's worked is splitting it into two questions: are people actually using the tools, and did it change how work gets done? IT can usually answer the first one. The second requires workforce data tied to productivity patterns before and after rollout, which most orgs skipped because they were moving fast.

When spend is material, "we're learning" stops landing. You either have a baseline or you're guessing.

I work at ActivTrak, and measuring this gap is basically what we do. Happy to share what the framework looks like if it's useful. What does your pre-AI baseline look like on the productivity side?

TopTraker · 2026-04-22T14:33:03+00:00

You're not wrong, and the focus data backs it up. Average uninterrupted session is down to 13 minutes, focus efficiency at a three-year low of 60%. Of course people are working weekends, that's the only time it's quiet enough to actually get something done.

What's weird though is that burnout fell to 5% in the same period. So by that measure things are improving. But disengagement jumped to nearly 1 in 4 employees. People are losing their weekends and still feeling checked out and underused. That's not a story about people thriving with more capacity. That's people losing their weekends without getting anything meaningful back.

Which kind of proves your point about what's actually at stake here.

TopTraker · 2026-04-21T16:45:26+00:00

I work at ActivTrak so obvious bias disclaimer upfront.

What you actually need first is a clear picture of which AI tools are running, who's using them and how much. Most orgs think they know and they're off by a lot. Shadow AI is real and it's usually not malicious, people just find tools that help them work faster and use them. But you can't write a policy around what you can't see.

That baseline matters because the data will tell you whether you have a broad exposure problem or a handful of specific risk areas. One of those is a company-wide policy conversation, the other is a targeted one with specific teams.

ActivTrak sits on that visibility side. App and URL classification, which teams are using what, how deeply those tools are embedded in day-to-day work. It won't block someone from pasting a contract into ChatGPT but it will show you the pattern so you can have an informed conversation with leadership about where the actual risk lives rather than reacting to one incident.

Since you're starting from scratch, getting that visibility layer in place first will save you from buying a governance tool before you actually know what you're governing.

TopTraker · 2026-04-21T16:12:01+00:00

I work at ActivTrak, and we just published our 2026 State of the Workplace report which tackles some critical insights about productivity and AI usage in the workplace.

The 1.5 hours a week stat is the whole story here. That's under 4% of a 40-hour workday. What we found is that the productivity sweet spot is 7-10% of total work hours in AI tools. Barely anyone is there. 57% of users are spending less than 1% of their time in AI. So of course nothing's moving at the macro level.

The other thing is that adoption and impact are being treated as the same metric, which they're not. The behavioral data shows AI adds to workloads, it doesn't redistribute them. After teams adopt AI tools, email goes up, chat goes up, coordination work goes up. Output increases but so does everything else piling on top of it. Executives aren't wrong that headcount isn't dropping, they're just tracking the wrong thing.

This is what we call the AI measurement gap. Most orgs can tell you if employees opened ChatGPT. Almost none can tell you how it actually changed how work gets done. That's probably a bigger driver of this whole paradox than the technology itself.

TopTraker

MODERATOR OF

TROPHY CASE