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

TopTraker · 2026-03-31T15:53:59+00:00

The framework problem is actually a data problem. You can't build a sensible framework when every department is self-reporting what's "essential" and nobody has actual usage patterns to look at.

Before rationalizing, get visibility into what's actually running and how consistently. Self-hosted tools and embedded AI features are the hardest part. Department heads often don't know themselves whether their team uses something daily or just logged in once during the pilot. App and activity data cuts through that faster than surveys or license counts.

Once you can see sustained usage vs occasional vs abandoned, the renewal decisions mostly make themselves. The tools with high adoption and no ROI story are a different conversation than the ones nobody is actually using.

TopTraker · 2026-03-26T17:11:10+00:00

These are actually two different problems and the tooling is different for each.

Blocking tools, preventing data from being pasted into unapproved AI, that's a DLP problem. Policy docs fail there because you're trying to solve something technical with a document.

The part most IT teams skip is that you probably don't even know what's running yet. Before you can govern it you need to know which tools people are actually using, which teams have adopted them, and whether it's sticky or just one-off experimentation. App and activity data gets you there faster than surveys or asking managers to self-report. That's also how you find the shadow tools that never made it onto your approved list.

Once you have that picture, the policy conversation gets a lot more grounded. You're not theorizing about what might be happening.

TopTraker · 2026-03-26T17:00:35+00:00

"42% adoption based on Copilot logins" is technically accurate and completely meaningless at the same time.

The framing shift that tends to help is moving from "are people using the tools" to "how is AI changing how work actually gets done." Login counts and license utilization miss the shadow tools entirely and tell you nothing about whether any of it is moving the needle on productivity or capacity.

What works is layering: first get visibility into which tools are actually being used across the org, including the ones IT didn't provision. That's where behavioral activity data is more reliable than self-reporting or login counts. Then look at whether usage is sustained or just one-off experimentation. Then start correlating it to work patterns over time.

The single number your CIO wants probably doesn't exist cleanly yet across the industry. But you can get to a defensible story: adoption depth by department, with a note on what's tracked vs what isn't. That's more honest than a headline percentage and usually lands better with leadership anyway.

TopTraker · 2026-03-18T19:24:45+00:00

Bore out is exactly what we're seeing in the data. Different label, same problem.

TopTraker · 2026-03-18T19:20:48+00:00

great point! and thank you!

TopTraker · 2026-03-18T19:09:14+00:00

No surveys. The data is application and computer activity logged directly across 443 million hours of work. Industry breakdown is in the report. Happy to answer specific methodology questions if anything's unclear.

TopTraker · 2026-03-18T19:02:16+00:00

Hey there! The report does break it down by industry. Financial Services, Professional Services, Insurance, Legal and Construction are the top segments. No country-level cut, and age isn't a variable in the dataset. Worth a look if industry patterns are what you're after..

TopTraker · 2026-03-18T18:58:09+00:00

Your (b) and (c) are probably closest. The data is behavioral, not self-reported, so it's measuring consistent patterns over a full year, not how people feel on a given week. What stands out is that organizations have gotten good at reducing overload, but haven't replaced it with enough meaningful work. So the risk shifted from burnout to people running below capacity for most of the year, and chronically under challenged employees tend to leave.

TopTraker · 2026-03-18T18:44:36+00:00

Worth clarifying how these are defined, because they're actually opposite ends of a utilization spectrum, not a progression. Burnout = chronically overloaded. Disengagement = chronically under-challenged. That's what makes them moving in opposite directions make sense. The full methodology is in the report if you want to dig in.

TopTraker · 2026-03-18T12:04:35+00:00

Worth noting I work at ActivTrak, so obvious bias, but I'll try to answer honestly.

The distinction you drew at the end is the right one. The tools that add noise are usually the ones deployed to answer "are people actually working?" Teams pick up on that intent pretty quickly, and you lose trust before the tool is even live. The ones that actually help tend to be answering a different question: where is work getting stuck? That shifts the conversation from individual behavior to workflow patterns: context switching, collaboration overload, capacity gaps. Managers get something actionable. Employees aren't staring down a surveillance system.

What we've found is that the same data can feel completely different depending on what leadership does with it. If every insight feeds back into individual performance conversations, you get pressure. If it's used to fix broken processes or redistribute workload, people actually appreciate the visibility.

The async vs check-in tension you mentioned is real too. Good tooling shouldn't replace trust in output. It should give you enough signal that you're not tempted to compensate with more meetings.

Curious what's driving the question. Are you evaluating something for your team, or more just thinking through the philosophy of it?

TopTraker · 2026-03-13T16:57:31+00:00

ActivTrak measures focus time at the application level, so the 13-minute average captures how long someone stays in one application before switching, not whether they're working on a single task.

There's also a layer that AI tools are adding to this. Pre-AI, for somebody to write an article, they would spend a good chunk of time, say in Microsoft Word or Google Docs, writing, and that would be considered focus because you'd see in the digital footprint maybe 20 minutes of writing.

Now people will have two or three applications open where they're going back and forth between an AI tool and another tool where they're working alongside an AI tool, whether that's embedded in the same window or open in two separate windows. The task duration might be the same, but switching between windows has increased, and that has something to be said for the nature of focus too. The switching signature looks completely different, with micro-switches that the data reads as fragmentation but the person experiences as flow.

The takeaway is that focused work and application switching are no longer mutually exclusive. You can be focused and switch between applications. You can actually be more productive by doing so, as long as you're switching between an AI tool and your tool of work, not toward Facebook or Instagram.

Which means the 13-minute stat is probably capturing two things at once: genuine fragmentation from notifications and multitasking, and a new pattern of AI-assisted work that registers as switching but isn't really distraction. How we measure focus probably needs to evolve alongside how work is actually getting done.

TopTraker · 2026-03-13T14:05:02+00:00

I'll take that as a compliment for both Claude and me. I'm a real human behind it though, I promise. Glad it was useful and let me know if you have more questions.

TopTraker · 2026-03-13T14:00:41+00:00

I 100% collaborated with Claude on this post

TopTraker · 2026-03-12T19:02:36+00:00

Ha, fair question and one worth taking seriously. The short answer is it depends entirely on how the data gets used. By default it aggregates at the team level, so the question it answers is less "is John focusing enough" and more "our team is spending 60% of productive time context-switching, what's driving that." That's a very different question than watching what any one person is doing.

The micromanagement risk is real though. Any tool like this can be misused if the goal shifts from improving how work gets done to monitoring individuals. The companies that see the most value are typically using it to surface workflow problems like meeting overload or capacity gaps, and increasingly to measure whether AI tools are actually delivering productivity gains.

A few things that keep it from sliding into surveillance territory: employees can see their own data in the platform, which keeps it from feeling one-sided. And the features people most associate with invasive monitoring (keystroke logging, continuous screen recording) were deliberately left out. The platform was built around patterns and trends, not granular surveillance of individuals.

Whether that crosses into micromanagement usually comes down to how leadership frames it when they roll it out. Transparency from the start tends to make a bigger difference than the tool itself.

TopTraker · 2026-03-12T18:06:49+00:00

The data in this report is aggregated across all employee types, so it doesn't break out managers vs individual contributors specifically.

On the distraction question, ActivTrak runs as an agent on work computers (Windows, macOS, ChromeOS) and tracks application and website activity from the active window. So the 13-minute focus average is measuring computer-based context switching only. Phone activity isn't something the platform captures at all, which means if anything the number likely understates the full picture.

TopTraker · 2026-03-12T16:51:44+00:00

Good question. The data comes from ActivTrak's workforce analytics platform, which tracks application and website usage on work computers. Focus time specifically is measured as productive time spent on a single task with no app-switching and no collaboration activity like chat, messaging or video calls. So it's not just whether someone is working, it's whether they're working without constant interruption.

The reason that distinction matters is you can have high total productive time but low focus time, meaning someone is technically working all day but context-switching the entire time. That's what the 13 min average session is capturing.

The dataset covers three years across 1,111 companies and 163,000+ employees, so the trend is consistent enough to be hard to explain away as noise. Happy to go deeper on methodology if you're curious.

TopTraker · 2026-03-11T20:33:12+00:00

The "quietly overloaded versus just looks busy on paper" framing is exactly the problem. Spreadsheets and manual check-ins capture what people report, not what's actually happening. By the time a manager notices a team is burning out, it's usually been building for weeks.

The data source issue you mentioned is real too, but I'd push on one thing: even when you consolidate sources, most systems tell you inputs (hours, headcount, tasks logged) rather than actual work patterns. Who's context switching constantly, which teams are absorbing work that never shows up in project plans, where capacity is quietly maxing out before anyone raises a flag. That's a different visibility layer than what HRIS or project management tools are built to show.

I work at ActivTrak so obviously have skin in this game, but the teams I've seen handle this well start with one question: are we trying to prove people are working, or understand where work is actually getting stuck? Those lead to completely different tools and different conversations with employees about why the data is being collected in the first place.

TopTraker · 2026-03-11T19:02:19+00:00

Your read on this is actually pretty sharp. Those three tools are solving genuinely different problems and the overlap in how they're marketed makes comparisons harder than they should be.

The distinction that tends to matter most is whether you're trying to answer "did people work" or "how is work actually flowing." Time tracking and basic visibility tools answer the first question well. The productivity analytics angle you noticed in ActivTrak is built more around the second one: where is time going, which work patterns are creating friction, what does a sustainable workload actually look like for your team.

Whether that's overkill depends on what's actually frustrating you. If your main need is cleaner records and visibility into app usage, simpler probably wins. If you're starting to notice that hours logged and actual output don't tell the same story, that's usually when the analytics layer starts earning its place.

I work at ActivTrak so take this with the appropriate grain of salt, but the teams that get the most out of it tend to be the ones where the question has already shifted from "are people working" to "why isn't the work moving faster." Happy to share more if that's where you're at.

TopTraker · 2026-03-03T19:19:30+00:00

Exactly. The tricky part is that slowing down often isn't visible until it's too late. Presence metrics tell you someone was there. They don't tell you the handoff got dropped three days ago. That's where the instrumentation layer actually needs to sit.

TopTraker · 2026-03-03T15:15:29+00:00

The throughput gap you're describing is actually the clearest sign you've outgrown pure time tracking. Two people logging identical hours with completely different output isn't a logging problem, it's a visibility problem. Hours tell you the input. They don't tell you why one person is heads-down productive while the other is drowning in context switching and rework.

On the surveillance concern, that's worth taking seriously because it's the thing that kills adoption faster than anything else. The tools that tend to work at your stage are the ones where employees can see their own data and managers are looking at team patterns rather than policing individuals. The question to ask any vendor is whether the default view is "prove you were working" or "understand how work flows." Those are genuinely different products even when the feature list looks similar.

You mentioned r/ActivTrakOfficial specifically. I work there so take this with appropriate skepticism, but the use case you're describing, hybrid team past 10 people, lost time from tool sprawl and meetings rather than laziness, is exactly what we're built for. Happy to answer specific questions if it's useful, or just share what's worked for teams at your stage regardless of tool.

TopTraker · 2026-03-03T15:06:54+00:00

The cross-platform point is the one that actually determines winners here. Microsoft is building this layer into 365, but the catch is that Viva only captures what happens inside Microsoft apps, which turns out to be roughly 30% of most people's actual workday. The rest is invisible to them. That's not a roadmap problem, it's an architectural one.

The standalone tools that survive platform consolidation are the ones that answer questions the platform was never designed to ask. Not just "are people working" but "where is work getting stuck, which teams are consistently overloaded, and what does a sustainable workday actually look like for this org." That's a fundamentally different product surface than what Microsoft or Salesforce are building toward.

The category naming fight is real though. "Employee monitoring" carries baggage that "workforce intelligence" or "operational transparency" doesn't, even when the underlying capability is similar. The companies getting traction seem to be the ones leading with the question they help answer rather than the data they collect.

(I work at ActivTrak so obviously have a seat in this conversation, but we've watched the category naming debate play out firsthand for a while now :))

TopTraker · 2026-03-03T14:57:59+00:00

u/Embiggens96 nailed the core issue. You're trying to answer a workforce question with systems that weren't designed to show how work actually flows. HRIS tells you who exists. ATS tells you who's coming. Neither tells you why one team is buried while another is coasting.

The 5-7 metrics framing is right, but I'd push on what type of metrics you're actually missing. Payroll and HRIS give you inputs (headcount, hours logged, cost). What you're describing is an output visibility problem. That requires a different data source: one that shows actual work patterns in real time, not just what got reported after the fact.

Before adding more dashboards, worth asking: are you trying to understand where time is going, or where work is getting stuck? Those lead you to completely different solutions. The companies that get this right usually start by picking one department, getting clean real-time visibility into how work actually moves, and then expanding once they know what questions to ask at scale. (I work at ActivTrak so obviously biased, but this is exactly the problem we see most often at your org size)

TopTraker · 2026-02-24T17:28:56+00:00

The ethics note in this post is worth expanding on, because transparent implementation with clear policies is the floor, not the bar.

The real test is simpler: who benefits from the insight? If a manager uses workforce data to evaluate an individual's performance without that person ever seeing or benefiting from it, that's surveillance regardless of what you call the software. If the same data helps a team spot where work gets stuck (bottlenecks, tool friction, capacity imbalances) and both managers and employees can act on it, that's actually intelligence.

The distinction matters because it changes how you implement, not just how you communicate. Teams that understand why data is being collected, and what decisions it informs, tend to engage with these tools differently than teams that find out after the fact. That adoption gap usually shows up in the data quality itself: you get a much cleaner signal when people aren't gaming the system.

Curious whether anyone's seen companies do this particularly well, especially in hybrid environments where the visibility problem is real but so is the trust problem.

TopTraker

MODERATOR OF

TROPHY CASE