Remote Work 2.0 and the Case for Evidence Over Office Mandates

By Slashdot Staff

Remote work debates tend to be loud, confident, and surprisingly light on data.

It’s a documented pattern. Recent analysis of U.S. firm-level data, based on a large-scale working paper by economists Jose Maria Barrero, Nicholas Bloom, and Steven J. Davis, examined more than 150,000 business responses collected through the Business Trends and Outlook Survey between late 2024 and early 2025.

The findings showed that roughly 75% of companies either do not measure remote productivity at all or openly admit they don’t know its impact. Despite this, many organizations still make strong claims that working from home is less effective, often using them to justify return-to-office (RTO) mandates.

Among the minority of companies that do express an opinion, only about 6.6% believe productivity is lower when people work remotely, while an even smaller share (roughly 2.1%) believe it’s higher. The overwhelming majority either see no difference or lack enough data to say one way or the other.

In other words, many decisions about where people should work are being made without meaningful measurement.

At the same time, employee data tells a different story. Findings from The Remote Work Divide report by MyPerfectResume, based on a survey of 1,044 U.S. workers, show that 78% prefer either fully remote or hybrid work, while only 22% prefer fully on-site roles.

When asked about productivity, 39% report feeling most productive when working remotely, compared to 25% who feel most productive in an office. Additionally, 68% say flexible work improves their mental health, a factor closely tied to long-term performance and retention.

These numbers don’t “prove” remote work is superior. But they do show a clear gap between how confident organizations sound and how little they often measure.

Remote Work 2.0 begins by addressing that gap.

What companies actually measure and what they don’t

It’s not that most organizations deliberately ignore productivity data; they’re just relying on what’s easy to observe.

In offices, presence is visible. Attendance can be tracked, and meetings are tangible. These signals create a sense of control, even if they say very little about output or quality.

Remote work removes those signals, exposing how little many companies truly know about how work gets done. As a result, leadership often falls back on assumptions: collaboration must be worse, focus must be lower, productivity must suffer.

But the real problem isn’t remote work. At the end of the day, the real issue is the absence of observability. In engineering, running systems without metrics would be unthinkable, yet when it comes to human work systems, that’s often exactly what happens.

Visibility does not mean surveillance

For technical audiences, any discussion of tracking raises immediate privacy concerns, and rightly so. Historically, many tracking systems were opaque, punitive, and misused.

But there’s an essential distinction between monitoring individuals and understanding systems.

Modern time-use data, when collected automatically and used transparently, can reveal patterns without targeting people. The goal is not to judge effort, but to understand conditions:

  • How fragmented workdays actually are
  • How much uninterrupted focus time exists
  • Where coordination and meetings expand unexpectedly
  • When flexibility starts turning into overwork

Without this visibility, organizations, both at the leadership and employee levels, are left with opinions rather than evidence. In turn, all conversations about work end up based purely on feelings, not facts.

Closing the visibility gap with automatic time tracking

Automatic time tracking tools like DeskTime were built to address this exact blind spot.

Rather than relying on manual time reporting, which is often incomplete and biased, a tool like DeskTime automatically captures time-use data across applications and workflows. This creates a consistent, factual baseline that teams can analyze over time.

The value isn’t in knowing who worked longer hours. It’s in understanding patterns:

  • How remote and office days differ in focus time
  • How interruptions shape the workday
    How workloads shift across teams and regions

When used responsibly, this kind of data replaces guesswork with clarity and reduces the need for micromanagement.

As a manager, you have to ensure that responsibility is enforced through technical controls, not policy alone. With a tool like DeskTime, all data is encrypted in transit and at rest, access is restricted via role-based permissions, and employees retain visibility into their own data. DeskTime operates under GDPR and aligns with ISO 27001 and ISO 27701 standards, which impose formal requirements around access control, data minimization, and auditability.

Privacy safeguards also exist at the application layer. Features like Private time allow tracking to be paused entirely, while optional screenshot blurring reduces exposure of sensitive information when monitoring is enabled. Together, these constraints are designed to provide system-level visibility without turning individual activity data into a surveillance mechanism.

Skrivanek: enabling flexibility through data

A concrete example of this approach is Skrivanek, a global language services company operating across multiple countries.

Skrivanek adopted DeskTime well before remote work became widespread, specifically to support flexible work arrangements. The goal wasn’t tighter supervision; it was confidence. Management wanted to allow people to work from different locations while still understanding workload distribution and capacity.

As expected, there were initial concerns around privacy. These were addressed through transparency: employees could see their own data, understand what was tracked, and know how it would be used.

Over time, automatic time tracking enabled Skrivanek to:

  • Support remote and flexible work without relying on assumptions
  • Identify overwork and imbalance early
  • Have data-based conversations instead of subjective ones

In this case, time-use data didn’t restrict flexibility. On the contrary, it made it manageable.

Planning with evidence instead of memory

Planning is one area where visibility makes a tangible difference.

Sprint estimates and capacity planning often rely on recollection and intuition. Historical time-use data doesn’t make estimates perfect, but it anchors them in reality.

Teams can see:

  • How long similar work actually took
  • How much time was consumed by coordination and interruptions
  • When workloads quietly became unsustainable

This shifts discussions away from blame and toward learning, something most engineering teams value.

Why RTO mandates often oversimplify the problem

Many RTO mandates are framed as solutions to productivity or collaboration issues. But without clear metrics, it’s difficult to know whether those problems exist or whether office presence addresses them.

Mandating location without measurement is a blunt instrument. It may change behavior, but it doesn’t explain causes.

A more constructive approach is to ask:

  • What outcome are we trying to improve?
  • How will we measure it?
  • What tradeoffs are acceptable?

Sometimes the answer may still involve office time. Other times, data may point to entirely different issues, such as meeting overload or unclear priorities.

Remote Work 2.0 is about informed decisions

Remote Work 2.0 isn’t about declaring remote work universally better than office work. It’s about replacing assumptions with observation.

The data already shows two things clearly:

  • Most companies don’t measure remote productivity
  • Most workers want flexibility, and many feel more productive with it

Automatic time trackers like DeskTime can serve as a compromise to help close that gap. Leadership gets the security and visibility it needs to make informed, evidence-based decisions, and employees get flexible work options.

In engineering, we don’t optimize systems we can’t observe. Work should be treated with the same rigor.

Related Categories