30% of Orgs Plan to Kill Remote Work in 2026. GitLab Has 2,000 Remote Employees. Who's Right?

[vp_eng_keisha]

I’ve been watching this industry split in real-time, and I need to talk about it with people who get it.

The divide: 30% of organizations are planning to reduce or eliminate remote work options in 2026. Meanwhile, GitLab has been thriving with 1,300+ employees across 65+ countries—fully remote since 2015. Amazon mandates 5 days in-office and 73% of their engineers immediately started looking for new jobs. Google’s taking a softer approach but still tracking attendance in performance reviews.

And yet: Fully flexible companies grew revenues 1.7x faster than mandate-driven firms between 2019 and 2024. 85% of workers now say remote work matters more than salary. High-performers are 16% more likely to leave if they face an RTO mandate.

So who’s right?

The Data Tells Two Stories

On one hand: 54% of businesses say they’ve been influenced by major corporations’ return-to-office decisions. There’s real executive concern about “cultural erosion” and “communication challenges.” These aren’t stupid people making random decisions.

On the other hand: 80% of companies that implemented RTO mandates have already lost talent because of it. That’s not hypothetical future risk—that’s documented attrition. And 67% of small companies are staying fully remote, which means they’re competing for the same talent pool with a major advantage.

What I’m Seeing in the Trenches

I’m scaling our EdTech engineering org from 25 to 80+ people, and we’ve been remote-first from day one. Here’s what’s actually happening:

It works when you invest in it. We built structured onboarding, async-first documentation, clear communication norms, and intentional team rituals. It required discipline. But our velocity is strong, our retention is excellent, and our talent pool is global instead of “whoever can commute to our office.”

The quality of remote implementation matters more than the decision itself. I’ve seen terrible remote cultures and terrible in-office cultures. The variable isn’t location—it’s intentionality.

Talent is voting with their feet. I’m watching senior engineers choose smaller remote-first startups over FAANG companies with RTO mandates. Not because of money (FAANG still pays more). Because of autonomy and quality of life. That’s not just preference—that’s a competitive shift in the labor market.

The Questions That Keep Me Up

Is this really about productivity? Or is it about management comfort and real estate sunk costs? Because the revenue growth data suggests flexible companies are outperforming, not underperforming.

Are we creating a two-tier system? Big tech can mandate RTO because they’re Big Tech. But the rest of us are competing for talent in a market where 64% of workers prefer remote/hybrid. Can we afford to eliminate our main recruiting advantage?

What does “right” even mean here? Amazon can lose 73% employee intent-to-stay and still fill roles because they’re Amazon. GitLab optimizes for distributed collaboration and builds different systems. They’re solving different problems with different constraints.

What I Actually Believe

I think we’re watching a permanent fork in workplace culture. Some companies will optimize for in-person collaboration, accept the talent pool constraints, and build around that. Others will optimize for flexibility, invest in remote-first practices, and compete on different terms.

Neither is universally “right.” But pretending this is a temporary trend or that one approach works for everyone is wishful thinking.

I’m building for remote-first because:

1. Our talent pool is global and diverse
2. Our retention data is strong
3. Our business metrics support it
4. Our team actually prefers it

But I’m genuinely curious: What are you seeing in your organizations? Is remote working or failing, and what’s making the difference? Are RTO mandates driven by data or by something else?

Because in 3 years, we’ll know who was right. The market will decide. I’m just trying to make sure we’re on the right side of that decision.

[eng_director_luis]

This hits home for me in financial services, where we were deeply skeptical about remote work before the pandemic.

I manage 40+ engineers across multiple time zones—some hybrid, some fully remote—and I’ve spent the last 2 years watching the data contradict the executive concerns.

What Actually Happened in a Regulated, Conservative Industry

We thought remote would kill collaboration and slow us down. Here’s what actually happened:

Our teams hit their targets. Sprint velocity stayed consistent. Production incidents didn’t increase. Customer-facing features shipped on time. If anything, engineers report better focus time for complex work now that they control their environment.

Documentation got better because it had to. When you can’t tap someone on the shoulder, you write things down. Our architecture decision records are clearer. Our onboarding docs are actually maintained. This benefits everyone, not just remote folks.

Async-first requires discipline, but it’s not impossible. We use structured communication: Slack for quick questions, Confluence for decisions, Zoom for complex discussions. It took 3-4 months to build the muscle, but now it’s second nature.

The Talent Equation Nobody’s Talking About

Here’s my contrarian take: If we mandate RTO and GitLab stays remote, who wins the talent war?

We’re competing for the same senior engineers. If I tell a talented developer “you need to relocate to our office or commute 90 minutes” and GitLab says “work from anywhere,” I lose that hire. Every. Single. Time.

And it’s not just about preference. Remote work has opened doors for first-generation college grads who can’t afford Bay Area or NYC rents. Engineers with caregiving responsibilities. People with disabilities who find commuting challenging. We’re tapping into talent pools that in-office mandates automatically exclude.

The Real Question

Keisha asked if RTO mandates are about productivity or something else. I think they’re about measurement failure, not productivity failure.

We struggle to measure knowledge work effectively. Butts-in-seats is easy to measure. Async collaboration quality is hard to measure. So when executives feel uncertain, they revert to what they can see.

But Amazon losing 73% intent-to-stay tells you something: Highly skilled workers have options. And they’re choosing the companies that trust them to manage their own work environment.

I’m not saying remote is perfect. Onboarding juniors is harder. Mentorship requires more structure. Some types of creative collaboration are smoother in person.

But this idea that we can mandate RTO without talent consequences? The data says otherwise. And in financial services—where we’re not exactly known for moving fast—we’re figuring it out. If we can make it work, anyone can.

[cto_michelle]

Leading a remote-first organization through cloud migration with 120 engineers has taught me something important: The implementation quality matters infinitely more than the location decision.

The Business Case Is Actually Pretty Clear

Our CFO loves our office footprint savings. Our retention metrics love remote flexibility. Our revenue growth has been faster remote than my previous companies achieved in-office. It’s hard to argue with all three data points aligning.

But let me be honest about the trade-offs, because pretending remote is universally better does nobody any favors.

Onboarding juniors is legitimately harder. You can’t overhear experienced engineers debugging problems. You can’t absorb team culture through proximity. We’ve had to build structured mentorship programs, pair programming schedules, and explicit knowledge-sharing rituals. It works, but it requires intention.

Serendipitous collaboration is rarer. Those hallway conversations where you connect two unrelated problems and find a solution? They don’t happen as naturally on Slack. We’ve had to create structured “office hours” and “open problem” sessions to replicate that dynamic.

Remote forces architectural clarity. And honestly? This has been a hidden benefit. When your team is distributed, you can’t rely on tribal knowledge or “just ask Sarah.” You document interfaces. You write clear ADRs. You design for asynchronous understanding. Our technical documentation improved dramatically because it had to.

The Amazon Question

Luis mentioned Amazon losing 73% intent-to-stay. Let me add context: Amazon can absorb that because they’re Amazon. Their brand, compensation, and scale let them weather massive attrition.

But can the rest of us? I’m competing with GitLab, Automattic, Zapier—companies that have built entire cultures around remote-first. If I mandate RTO, I’m not competing with Amazon for talent. I’m competing with companies that offer better flexibility and interesting technical challenges.

That’s not a winning position.

What Actually Drives RTO Mandates?

I’ve been in enough executive conversations to know the real drivers:

1. Sunk cost fallacy on real estate. We signed 10-year leases. Now we need to justify them.
2. Management comfort. Some leaders genuinely don’t know how to evaluate performance without seeing people.
3. Cultural nostalgia. “The way we used to work felt better.” (Did it actually produce better outcomes? Often unclear.)

Rarely is it “our data shows remote workers are less productive.” Because most companies don’t have that data. Or if they do, it shows the opposite.

The Permanent Fork

Keisha’s right—we’re watching a permanent split. Some companies will optimize for in-person, accept the constraints, and build around that. Others will invest in remote-first infrastructure and compete on different terms.

Neither is wrong. But treating this as a temporary trend or trying to force one model on everyone is wrong.

I’m building for remote-first because our business metrics support it and our team prefers it. But I’m watching the market closely. Because in 3 years, we’ll have real longitudinal data on which approach produced better outcomes.

My bet: It won’t correlate with location. It’ll correlate with how deliberately you built your culture and systems to match your chosen model.

[maya_builds]

Okay, designer perspective incoming—and I’m probably going to contradict myself, so bear with me.

The Honest Truth About Remote Creative Work

I miss whiteboard sessions. I miss impromptu design reviews where someone walks by, sees my screen, and says “wait, what if we tried this instead?” That serendipity is real, and Zoom doesn’t fully replace it.

But.

My deep work time for component design has improved dramatically since going remote. No interruptions. No “quick question” that derails 2 hours of flow state. I can put on noise-canceling headphones and actually think through complex design systems.

So which matters more? Honestly—it depends on what I’m working on.

What My Failed Startup Taught Me

My startup failed for a lot of reasons, but one was definitely remote collaboration challenges. This was 2019—pre-pandemic tooling, pre-everyone-figuring-out-async-first practices. We tried to replicate in-office culture over Zoom and it just… didn’t work.

But here’s the thing: We were doing remote wrong. We scheduled 6 hours of daily meetings because we didn’t know how else to stay aligned. We didn’t document decisions. We expected synchronous everything.

That’s not a remote problem. That’s a bad remote implementation problem.

What Actually Works (For Creative Roles)

After trying everything, here’s my current hybrid model: Quarterly in-person design sprints + daily async work.

We gather 4 times a year for intensive collaborative work—whiteboarding, rapid prototyping, alignment on vision. Then we go back to distributed work where I can execute without constant interruption.

It gives me the best of both: creative collaboration energy and focused execution time.

The Accessibility Angle Nobody Mentions

One thing that keeps coming up for me: Remote work opened design roles to people with mobility challenges, chronic illnesses, neurodivergent folks who find office environments overwhelming.

When we mandate RTO, we’re not just losing “people who prefer remote.” We’re losing entire categories of talented people who need remote to do their best work.

That feels like a huge competitive disadvantage to choose voluntarily.

Why Are We Making This Binary?

Michelle’s right that implementation quality matters more than location. But I’d go further: Why are we treating this as one-size-fits-all?

Engineering might work great fully remote. Sales might benefit from in-person energy. Design might need quarterly sprints. Customer support might optimize for async-first.

The companies that figure out role-specific flexibility instead of blanket mandates are probably going to win the talent war.

Because the data Keisha shared is pretty clear: talent is voting with their feet. And if you make them choose between “commute 90 minutes” and “work for a fully remote company,” they’re choosing remote. Every time.

My startup failed because we didn’t adapt fast enough to changing reality. I worry that RTO mandates are the same mistake at a bigger scale—fighting the market instead of adapting to it.

[product_david]

I’m coming at this from a non-technical but deeply business-focused angle, and what I’m seeing in the market is fascinating—and a bit scary for companies on the wrong side of this divide.

The Customer Signal You’re Missing

Here’s something that surprised me: B2B customers are starting to ask about our remote work policies during vendor selection.

Not as the deciding factor, but as a data point about our culture and adaptability. They want to know if we’re a “forward-thinking” company or one that’s “stuck in old patterns.” Remote work has become a proxy signal for organizational agility.

That’s… not nothing.

The Talent Pipeline Reality

I hire product managers constantly. Here’s what I’m seeing in recruiting:

Top candidates choose companies based on flexibility, not just compensation. I’ve lost senior PM hires to companies offering $20K less but full remote flexibility. That’s not anecdotal—it’s a pattern.

And when I look at where other companies are recruiting: 67% of small companies staying fully remote while big tech pushes RTO means we’re creating a two-tier labor market.

Tier 1: Large companies with brand power, high compensation, in-office mandates.
Tier 2: Smaller companies with flexibility, interesting challenges, remote-first culture.

Senior talent is increasingly choosing Tier 2. Not universally, but enough to create competitive pressure.

The Revenue Correlation

Keisha mentioned that fully flexible companies grew revenues 1.7x faster than mandate-driven firms from 2019-2024. Let me add product context to that:

Remote teams are often better at async customer communication. When your team is distributed, you build muscles for:

• Clear written communication
• Async collaboration with external stakeholders
• Documentation that customers can actually understand

These are the same skills that make customer-facing teams effective.

I’m watching our remote product teams out-execute our hybrid teams on customer research and user testing velocity. Not because remote is magic, but because they built better processes out of necessity.

What the Market Will Decide

GitLab: 2,000 employees, fully remote, thriving.
Amazon: 5-day RTO mandate, 73% of engineers considering leaving.

In 3 years, we’ll have longitudinal data on:

• Revenue growth by work model
• Talent retention by flexibility level
• Product velocity by location policy
• Customer satisfaction by team structure

The market will decide who’s right. Not executives, not think pieces, not surveys—actual business outcomes.

My Strategic Concern

If big tech mandates RTO while smaller companies stay remote, what happens to competitive dynamics?

Do we see brain drain from FAANG to high-growth startups? Do we see regional tech hubs lose relevance as talent spreads globally? Do we see two distinct labor markets with different compensation structures and career trajectories?

I don’t have answers. But I’m watching our hiring pipeline very carefully. Because right now, the product managers I want are choosing based on flexibility. And if we can’t compete on that dimension, we need a really compelling alternative value proposition.

The Uncomfortable Question

Michelle called out the real drivers: sunk cost on real estate, management comfort, cultural nostalgia. I’d add one more: control.

Some executives just feel uncomfortable not being able to see their teams. That’s a trust issue, not a productivity issue. And if that’s driving RTO mandates, we should be honest about it instead of dressing it up as “collaboration” or “culture.”

Because the data is pretty clear: flexibility isn’t hurting performance. And mandating RTO is hurting talent acquisition.

The companies that figure out how to build high-performing distributed teams will have a significant competitive advantage in the next 5 years. The ones that fight the market will spend a lot of energy swimming upstream.

I know which bet I’m making.