30% of Companies Eliminating Remote Work by 2026—Are RTO Mandates Data-Driven or Just Executive Preference?

General
1

I keep seeing headlines about major tech companies dragging employees back to the office. Amazon forcing 350,000 people back full-time. Instagram mandating 5 days starting February. Even Google—relatively flexible—still requires 3 days in office.

Here’s what bothers me as a product person: the numbers don’t add up.

The Data Disconnect

Resume Builder’s latest survey shows 30% of U.S. companies plan to eliminate remote work entirely by 2026. Meanwhile, 76% of workers say they’d quit if remote options disappeared. That’s not a small gap—that’s a business continuity crisis.

Let me put this in product terms: If I told my CEO we’re launching a feature that 76% of users say would make them leave our platform, I’d be laughed out of the room. Yet somehow when it’s workplace policy, we’re calling it “strengthening culture”?

What Problem Are We Actually Solving?

When companies announce RTO mandates, they cite three reasons:

  • 64% say it’s to strengthen company culture
  • 62% say it’s to improve productivity
  • 45% say it’s to maximize office space

But here’s where it gets interesting. A quarter of C-suite executives admitted they hoped for voluntary turnover from RTO policies. Nearly 40% of managers reported doing layoffs because not enough workers quit from RTO.

So which is it? Are we building culture, or are we cutting costs without paying severance?

The Evidence Gap

As product leaders, we’re taught to be customer-obsessed. We measure everything. We A/B test button colors. We track retention metrics obsessively. We demand data before making product decisions.

Yet when it comes to RTO, where’s the data?

  • 80% of companies lost talent due to RTO mandates (not exactly a productivity win)
  • 67% of companies under 500 employees remain fully remote (small companies competing on flexibility)
  • Only 20% of LinkedIn job listings are remote, but they get 60% of applications (talent wants flexibility)

If Amazon, Meta, and others have productivity data showing in-office work drives better outcomes, I haven’t seen it. What I have seen is 91% of Amazon employees expressing dissatisfaction with the mandate.

The Small Company Advantage

Here’s what’s fascinating: while Fortune 500s are mandating returns, 67% of smaller companies are staying fully remote—and using that as a competitive hiring advantage.

They’re hiring the talent that quits Amazon over RTO. They’re accessing global talent pools. They’re running leaner operations without expensive office footprints.

Are they making better decisions than tech giants? Or are they just more honest about the tradeoffs?

So What’s Really Happening?

I can think of three possibilities:

  1. Large companies have productivity data that smaller companies don’t - possible, but if so, why not share it?
  2. RTO is about sunk costs in real estate - commercial leases are expensive, optics matter
  3. RTO is about managerial preference for control - easier to see butts in seats than measure outcomes

My bet? It’s mostly #2 and #3, with a dash of “we’ve always done it this way.”

The Product Lens

If I managed RTO like a product decision, here’s what I’d do:

  1. Define clear success metrics - not “days in office” but actual business outcomes
  2. Run experiments - different teams, different policies, measure results
  3. Listen to users - when 76% say they’d quit, that’s signal, not noise
  4. Iterate based on data - optimize for outcomes, not executive preferences

Instead, we’re seeing top-down mandates with no clear success criteria and employee backlash being dismissed as “resistance to change.”

The Question

So here’s what I want to know from this community:

What would “data-driven” RTO actually look like? What metrics would justify a mandate? And if we don’t have those metrics, why are we pretending these decisions are anything other than executive preference?

Because from where I sit, this feels less like strategic decision-making and more like hoping nostalgia for 2019 will solve 2026 problems.

Sources:

2

David, you’re asking the right questions. From my seat managing 40+ engineers in financial services, I see this playing out differently than the headlines suggest.

The Compliance Excuse

In fintech, we hear a lot about compliance and security requiring in-office presence. But honestly? That’s often a smokescreen. Our distributed teams meet the exact same regulatory requirements as our office-based teams. The difference isn’t location—it’s process maturity.

What I’ve noticed is that “culture” and “security” become convenient justifications when what leadership really means is: “We’re not comfortable managing teams we can’t see.”

The Real Data From My Teams

Here’s what I can share from actual measurements:

  • Distributed teams hit the same sprint velocity as our Austin-based teams
  • Knowledge transfer happens faster when we’re forced to document instead of relying on hallway conversations
  • Retention is higher on distributed teams (20% better over 18 months)
  • Time-to-productivity for new hires is comparable (4-6 weeks regardless of location)

The catch? We had to invest heavily in async communication practices, better documentation, and intentional team-building. That investment was uncomfortable for middle management.

The Middle Management Problem

I’ll say the quiet part out loud: a lot of RTO pressure comes from middle managers who haven’t adapted their leadership styles to remote work.

Managing by walking around doesn’t scale. Managing by Slack status doesn’t work. You need to manage by outcomes, clear goals, and trust—which requires a completely different skill set.

When execs say “culture is eroding,” sometimes what they mean is “our managers don’t know how to lead remotely, and retraining is harder than mandating RTO.”

Where I Agree With RTO Advocates

I’ll be honest—remote work isn’t a silver bullet:

  • Building trust with new team members is harder remotely. We solved this with structured onboarding and regular 1:1s, but it takes more intentionality.
  • Creative whiteboarding sessions lose something over Zoom. Though Miro helps, and honestly, how many companies were doing productive whiteboarding sessions anyway?
  • Junior engineers need more support. We implemented mentorship rotations and “office hours” for technical questions.

But these are process problems, not location problems. Throwing everyone back in an office is using a sledgehammer when you need a scalpel.

The Real Estate Question

Let’s be real: a lot of companies have multi-year leases on expensive office space. When your CFO is staring at millions in sunk costs, suddenly “culture” becomes a very convenient justification for filling those seats.

I’m not saying that’s the only reason, but if we’re being data-driven, we should acknowledge financial incentives shape these decisions as much as productivity metrics.

What Data-Driven Would Look Like

If we were truly being scientific about this:

  1. Run controlled experiments: Some teams remote, some hybrid, some in-office. Measure: productivity, retention, quality, employee satisfaction, hiring pipeline.
  2. Publish the results: If RTO improves outcomes, show us. Amazon has 350,000 employees—that’s a massive sample size. Where’s the A/B test data?
  3. Let teams choose based on outcomes: If data shows in-office teams ship better products, great. If not, optimize for talent retention and hiring pool size.

Instead, we’re seeing executives make gut calls and then cherry-pick anecdotes to justify them.

The Talent Market Reality

Here’s my biggest concern as someone who has to recruit engineers: RTO mandates shrink our talent pool by 60-70%.

When I can hire remotely, I get applications from experienced engineers in lower-cost-of-living areas, caregivers who need flexibility, and diverse candidates who may not want to relocate. When I’m limited to a 30-mile radius around Austin, my hiring pipeline collapses.

If Amazon wants to compete on local talent only, that’s their choice. But smaller companies like mine will happily hire the people who quit over RTO—and we’re getting incredible talent because of it.

TL;DR: RTO decisions feel less like evidence-based strategy and more like middle management’s discomfort with async leadership—dressed up in “culture” language to justify expensive real estate.

3

Both of you are circling around what I think is the core issue: whose definition of “culture” gets to win?

I’ve scaled engineering teams from 25 to 80+ people at our EdTech startup—entirely remote since 2021. And I’m going to push back hard on this narrative that remote work erodes culture.

Culture Is Not Proximity

Culture is built through shared values, behaviors, and accountability—not through shared office space.

When leaders say “we’re losing culture,” what I often hear is: “We’re losing the specific kind of culture that executives are comfortable with.”

And let’s be honest about what that often means:

  • Culture where leadership can casually observe who’s “working hard” by seeing them at their desk at 7pm
  • Culture where access to power comes from who gets face time in the hallway
  • Culture where promotions go to people who are most visible, not necessarily most impactful

None of that is culture. That’s proximity bias dressed up as values.

The Data Doesn’t Support RTO

David cited this statistic: 70% of engineering teams report higher productivity when given office vs remote choice. Not mandates—choice.

Yet Amazon, Meta, Dell are pushing 5-day mandates. If the data shows choice drives better outcomes, why are we eliminating choice?

Here’s my hypothesis: this isn’t about performance. It’s about control.

Executives are uncomfortable with distributed authority. They want to see teams, walk the floor, “feel the energy.” And rather than adapting their leadership to the data, they’re changing the policy to match their comfort level.

What We Built Remotely

Let me share what we’ve accomplished at our EdTech startup, 100% remote since inception:

  • Built the most inclusive engineering team I’ve ever led: 48% women, 35% underrepresented minorities. Many wouldn’t have joined if we required relocation.
  • Retention rate of 94% over 3 years: compared to industry average of 78%. People stay because they have flexibility.
  • Shipped 4 major product releases on schedule: remote didn’t slow us down; it forced us to get better at planning and communication.
  • Hired top talent from 15 different states: including senior engineers who left FAANG companies over RTO mandates.

None of this happened by accident. It happened because we intentionally built culture through values, rituals, and accountability—not through office badge scans.

The Bias Question

Luis mentioned the talent pool shrinking with RTO mandates. Let me add a layer to that: who gets excluded by RTO?

  • Caregivers (disproportionately women) who need flexibility
  • People with disabilities for whom commuting is a barrier
  • Underrepresented groups who may not want to relocate to expensive tech hubs
  • Experienced professionals in second-act careers who value autonomy

When we mandate RTO, we’re not making a neutral “culture” decision. We’re making a demographic decision about who gets to participate in tech leadership.

And then we wonder why our industry has diversity problems.

Transparency Is the Real Issue

Here’s what bothers me most: if RTO is truly about productivity, why won’t companies share the data?

Amazon has 350,000 employees. Meta has detailed performance analytics on every engineer. Google literally invented OKRs and data-driven management.

If they have evidence that in-office work drives better outcomes, publish it. Run the study. Share the metrics. Let the industry learn from it.

The fact that they’re not sharing data suggests there isn’t data to share.

What “Culture” Really Means

When I talk about culture with my team, here’s what we focus on:

  • Psychological safety: Can people raise concerns without fear?
  • Accountability: Do we deliver on commitments?
  • Growth: Are people learning and developing?
  • Inclusion: Do diverse voices shape decisions?
  • Impact: Does our work matter?

None of those things require physical proximity. They require intentional leadership and clear values.

The executives pushing RTO are confusing familiarity with culture. Just because it’s how we’ve always worked doesn’t mean it’s the best way to work.

The Real Cost

David asked what data-driven RTO would look like. Here’s my answer: measure what matters.

Don’t measure badge scans. Measure:

  • Employee engagement scores
  • Retention rates by team/location
  • Delivery velocity and quality
  • Hiring pipeline strength
  • Diversity metrics

And then compare teams with different policies. Run actual experiments. Publish the results.

But here’s what I predict: companies won’t do that study because they’re worried the data won’t support the mandates they’ve already made.

The Power Dynamic

Let’s name what this really is: a power struggle between executives who are comfortable with 2019 and employees who have experienced a better way to work.

76% of workers say they’d quit over RTO. That’s not resistance to change—that’s a clear signal that the change we experienced during COVID worked for most people.

The question is whether leadership is willing to listen to that signal or whether they’ll double down on nostalgia.

Bottom line: If your culture falls apart when people work remotely, you didn’t have a strong culture—you had convenient proximity. Build culture through values and accountability, and location becomes irrelevant.

4

Okay, can I just say this from the design/craft perspective? Remote work forced us to get better at our jobs, and I think that’s what makes executives uncomfortable.

The Documentation Revelation

Before COVID, our design system documentation was a disaster. Why? Because we could just walk over to someone’s desk and ask questions.

Remote work forced us to write things down. And you know what happened?

  • New designers onboarded 40% faster because everything was documented
  • Cross-team collaboration improved because we couldn’t rely on tribal knowledge
  • Decisions were more thoughtful because we had to write design rationale, not just sketch on a whiteboard

The “hallway conversations” everyone romanticizes? Half of them were just covering for the fact that we hadn’t documented our systems properly.

The “Coffee Machine Chat” Myth

I keep hearing executives talk about missing “spontaneous coffee machine chats” that spark innovation.

Let me tell you about my startup experience: those chats didn’t save my company.

We had all the coffee machine conversations you could want. Beautiful office in Austin. Ping pong table. The works. We still failed because we were building the wrong product for the wrong market.

What saved the companies that did succeed? Ruthless focus on customer feedback and execution. None of which requires physical proximity.

Also, let’s be real: how many “innovative coffee machine chats” were happening at companies with 500+ people anyway? At that scale, you’re not bumping into the CEO at the coffee machine—you’re standing in line with the same 8 people from your floor.

The idea that serendipitous innovation requires offices is survivorship bias wrapped in nostalgia.

What Remote Actually Revealed

Here’s the uncomfortable truth: remote work revealed which “collaboration” was actually just synchronous waste.

Pre-COVID:

  • 6-person meetings where 4 people said nothing (could’ve been an email)
  • “Quick syncs” that derailed someone’s deep work for 30 minutes
  • Design reviews scheduled for everyone’s convenience, not the reviewer’s focus time

Remote forced us to ask: Does this actually need to be synchronous?

Turns out, a lot of it didn’t. The stuff that really needed real-time discussion became obvious. Everything else became async Slack threads or Loom videos—and work got better.

The Junior Designer Problem

I’ll admit the one thing that’s genuinely harder remote: mentoring junior designers.

Early-career folks benefit from watching how experienced people work, seeing how they think through problems, getting quick feedback on iterations.

But here’s the thing: that’s a process problem, not a location problem.

What we did:

  • Pair design sessions over Figma (works better than over-the-shoulder anyway because you can both control the canvas)
  • Recorded design critiques so juniors could rewatch and learn
  • Office hours for questions instead of hoping to catch someone at their desk

Did it take more intentionality than just sitting near someone? Yes. But you know what? It probably should have. Osmotic learning is just a nice way of saying “inconsistent knowledge transfer.”

The Tooling Gap

David asked about data-driven RTO. Here’s my question: Are companies investing in remote tools as much as they invest in office space?

Because if you’re spending millions on office leases but won’t pay for:

  • Miro/Figjam for collaborative whiteboarding
  • Loom for async video updates
  • Good webcams and audio for everyone
  • Reliable VPN and security tools

…then you’re not really testing whether remote works. You’re just half-assing it and blaming the model when it fails.

The Bad Culture Hypothesis

Keisha said something that hit me: “If your culture falls apart when people work remotely, you didn’t have a strong culture.”

Let me extend that: If your culture relied on physical presence, you probably had a bad culture even when everyone was in the office.

Companies with bad remote culture:

  • No clear values or mission
  • Poor communication habits
  • Unclear decision-making authority
  • No documentation practices

Guess what? Those companies had the exact same problems in-office. Proximity just masked it.

The Design Systems Proof Point

I lead design systems now, and here’s what I’ve learned: good systems work regardless of location.

If your design components are well-documented, versioned properly, and have clear usage guidelines, it doesn’t matter if your product team is in Mumbai or San Francisco. They can implement correctly.

If your systems require physical presence to use, they’re not systems—they’re just files with an expert dependency.

Same applies to company culture and processes.

What I Think Is Really Happening

My hot take: executives are uncomfortable with the loss of ambient awareness.

When everyone’s in the office, leadership can walk around and feel like they know what’s happening. They see who’s at their desk, who’s talking to whom, what the energy feels like.

Remote takes that away. You have to trust metrics, async updates, and outcomes instead of vibes.

And for leaders who rose through the ranks in office environments, that shift is deeply uncomfortable. So rather than learning new leadership skills, they’re trying to recreate the old environment.

The Generational Divide

One more thing: there’s a generational component here.

Executives in their 50s and 60s spent entire careers in offices. Remote work challenges their mental model of what “work” looks like.

But designers and engineers in their 20s and 30s? We’ve seen remote work work. We’ve proven we can ship products, collaborate across time zones, and build meaningful relationships with people we’ve never met in person.

The data David cited—76% would quit over RTO—isn’t just about flexibility. It’s about a fundamental disagreement over what work should look like in 2026.

My view: RTO mandates are executives choosing familiarity over evidence. And the companies that figure out how to build great remote-first culture are going to win the talent war over the next decade.

5

Let me cut through the rhetoric and talk about what this actually is from a CTO perspective: business strategy disguised as workplace policy.

Everyone’s dancing around it, so I’ll say it plainly.

This Is About Cost Reduction

Remember what David cited? 25% of C-suite executives admitted they hoped for voluntary turnover from RTO policies. Nearly 40% of managers reported doing layoffs because not enough workers quit.

Let’s do the math:

Scenario 1: Traditional Layoff

  • Severance packages (typically 2-4 weeks per year of service)
  • WARN Act compliance (60-day notice for mass layoffs)
  • Unemployment insurance premium increases
  • Potential wrongful termination lawsuits
  • Reputation damage in talent market

Scenario 2: RTO Mandate

  • Announce “return to culture”
  • 20-30% quit voluntarily (no severance)
  • Remaining employees understand the implicit threat
  • Real estate costs justified on balance sheet
  • PR spin: “strengthening our collaborative culture”

Which do you think CFOs prefer?

The Real Estate Component

Maya touched on this, but let me make it explicit: many companies are locked into multi-year office leases at pre-COVID rates.

WeWork’s collapse didn’t eliminate those lease obligations. Companies are sitting on:

  • 10-year leases signed in 2019-2020
  • Millions in sunk costs on office buildouts
  • Contractual penalties for early termination

When your board asks, “Why are we spending M/year on empty office space?” saying “everyone’s remote” is a harder sell than “we’re bringing people back to strengthen culture.”

It’s not about productivity. It’s about justifying the P&L line item.

The Talent Market Calculation

Now let’s talk about the 5-year strategic cost of losing 76% of your workforce who’d quit over RTO.

What you lose:

  • Institutional knowledge (especially painful in complex technical systems)
  • Top performers who have the most options in the job market
  • Diversity (Keisha nailed this—RTO disproportionately impacts caregivers and underrepresented groups)
  • 6-12 months of productivity during hiring/onboarding cycles

What you gain:

  • Lower headcount (fewer salaries)
  • Justification for office real estate
  • Workforce that’s more compliant with future mandates

For companies doing quiet layoffs, this math works. For companies trying to compete on innovation and talent, this is strategic suicide.

The Cloud Infrastructure Parallel

Here’s what’s ironic to me as a CTO: we’ve spent the last decade moving infrastructure to the cloud precisely because geographic distribution is more resilient, scalable, and cost-effective than centralized data centers.

Yet somehow, when it comes to human resources, we’re arguing that centralized (everyone in one office) is better than distributed (remote teams).

The same executives who approved multi-million dollar cloud migrations are now mandating RTO. The cognitive dissonance is stunning.

If distributed systems are the future for infrastructure, why are they the past for teams?

What Data-Driven Actually Means

David asked what data-driven RTO would look like. As a CTO, here’s my answer:

Measure outcomes, not inputs.

Don’t measure:

  • Badge scans
  • Hours in office
  • Calendar utilization
  • Zoom meeting attendance

Measure:

  • Product velocity: Features shipped per quarter
  • Quality metrics: Bug rates, customer satisfaction, system uptime
  • Employee effectiveness: Delivery against OKRs
  • Retention: Especially of high performers
  • Hiring pipeline: Time-to-fill, quality of candidates

Then run controlled experiments:

  • Team A: Fully remote
  • Team B: Hybrid (3 days)
  • Team C: Full-time office
  • Team D: Employee choice

Run for 6-12 months. Compare results. Follow the data, not the executive preference.

But here’s why companies won’t do this: they’re worried the data will show remote or hybrid performs as well or better—and then they’d have to justify the RTO mandate anyway.

The Honesty Test

If leadership were being honest, here’s what the RTO announcement would say:

“We have expensive office leases we can’t exit. We need to reduce headcount but don’t want to pay severance. We’re uncomfortable managing distributed teams and would rather change the workforce than change our management practices. So we’re mandating RTO and calling it ‘culture.’”

Instead, we get PR statements about “collaboration” and “innovation”—with no data to back them up.

The Competitive Landscape

Luis mentioned that 67% of small companies are staying fully remote and using it as a hiring advantage.

From a strategic perspective, this is a massive market opportunity.

If I’m a startup CTO competing against Amazon, Meta, or Google for engineering talent, I’m thrilled they’re mandating RTO. It means:

  • Larger talent pool for my company
  • Experienced engineers looking for exits
  • Competitive advantage on flexibility
  • Lower geographic salary constraints

Amazon can mandate RTO because they have market power. Smaller companies that copy them without that power are making a strategic error.

The 5-Year Outlook

Here’s my prediction:

Companies that execute RTO mandates well:

  • Have strong business justifications (manufacturing, hardware, healthcare where physical presence is required)
  • Invest heavily in making office experience genuinely better than remote
  • Accept smaller talent pools and higher salary costs
  • Measure and optimize for outcomes

Companies that execute RTO poorly:

  • Use it as disguised layoffs
  • Don’t invest in office experience
  • Lose top talent to competitors
  • End up with less engaged, less productive workforce

My bet: most companies fall into the second category.

The Bottom Line

David framed this as “data-driven vs executive preference.”

From where I sit, it’s neither. It’s financial strategy.

RTO mandates are about:

  1. Reducing headcount without severance costs
  2. Justifying real estate expenses
  3. Maintaining traditional management hierarchies

The “culture” and “productivity” arguments are post-hoc rationalizations.

If companies were serious about culture, they’d invest in it regardless of location. If they were serious about productivity, they’d measure it rigorously and follow the data.

Instead, they’re making financial and political decisions and dressing them up as operational ones.

My advice to engineers, designers, and product leaders: If your company announces RTO, ask for the data. Ask what success looks like. Ask how they’ll measure whether it worked.

If they can’t answer those questions, you know it’s not about performance—it’s about something else entirely.