71% of Gen Z Choose Hybrid, Only 6% Want Full In-Office—But 54% of Businesses Influenced by Major Corp RTO. Whose Strategy Are You Following?

General
1

I’ve been managing a team of 40+ engineers for the past five years, and I’ve noticed something interesting about our Gen Z engineers: they actually ask to come into the office more often than our senior engineers. Not five days a week—but definitely more than the Millennials and Gen X folks who are perfectly happy staying remote.

This tracks with the data. According to recent research, 71% of Gen Z workers prefer a hybrid model—they want some office time, but not full-time. Only 6% want to be in the office every single day.

But here’s what’s bothering me: 54% of businesses say they’ve been influenced by major corporations’ return-to-office policies. Companies like Amazon, Meta, TikTok, and Microsoft are mandating 4-5 days in the office, and everyone else seems to be following along like lemmings.

The Herd Mentality Problem

When Amazon announced their 5-day RTO mandate, 91% of their employees said they were dissatisfied with it. 73% said they were considering quitting. That’s not a policy success—that’s a retention crisis waiting to happen.

Yet nearly half of all companies are now demanding employees be in the office at least 4 days a week, with 28% phasing out remote work entirely. The statistic that really gets me: Among Fortune 100 companies, 54% of employees are now fully in office, compared to just 5% two years ago.

Are we making these decisions based on our own data, or are we just copying what Amazon does because they’re Amazon?

What Gen Z Actually Wants (And It’s Not What You Think)

Here’s the nuance that gets lost: Gen Z is more likely than older generations to want office time—but they still prefer hybrid over full-time in-office. They come to the office for mentorship, for collaboration, for building relationships. Not because they’re more productive there.

On my team, our Gen Z engineers come in 2-3 days a week by choice. They schedule those days around team design sessions, architecture reviews, and mentoring conversations. The other days? They’re heads-down coding from home, often putting in their best work.

When I ask them why, the answer is always some version of: “I need the office for the people, not for the work.”

Our Approach: Data Over Fashion

We built our hybrid policy based on actual performance data from our teams, not based on what Meta is doing. We tracked:

  • Deployment frequency and quality metrics
  • Employee satisfaction and retention
  • Cross-team collaboration effectiveness
  • Onboarding success for new hires

The data told us that 2-3 days of intentional in-office time produced the same outcomes as 5 days, with significantly better retention and satisfaction scores.

So that’s what we do. Not because it’s trendy—because it works for our team, in our context, with our business model.

Questions for the Community

I’m genuinely curious:

  1. Are you building your own strategy or following industry leaders? If you’re mandating more office time, is it based on your data or on what Amazon/Meta are doing?

  2. How do you balance Gen Z’s need for mentorship and community with their preference for hybrid flexibility? They clearly want both—how are you designing for that?

  3. What metrics are you actually tracking? Beyond “days in office,” what outcomes are you measuring to determine if your policy is working?

I get nervous when I see 54% of businesses being “influenced” by major corporations. Influenced is just a polite way of saying “copied without thinking.” We’re all operating in different talent markets, with different business models, serving different customers.

Maybe the question isn’t “What’s Amazon doing?” Maybe the question is “What works for the team we have, building the product we’re building, in the market we’re competing in?”

What’s your take?

Sources:

2

Luis, you’ve hit on something that’s been frustrating me for months: the assumption that “industry leaders” are actually leading in a direction we should follow.

When I was scaling our EdTech startup from 25 to 80+ engineers, I had board members pointing to Amazon and Meta as examples we should emulate. My response: “We’re not Amazon. We’re not Meta. We don’t have their brand recognition, their compensation packages, or their business model. Why would we copy their HR policies?”

“Industry Leaders” Aren’t Representative

Amazon can afford to lose 73% of employees who are “considering quitting” because they receive 1 million+ job applications per year. They’re optimizing for real estate utilization and managerial control, not for retention.

Meta has golden handcuffs (RSUs) that make it financially painful to leave, even if you hate the RTO policy.

Most of us don’t have those luxuries. If 73% of our engineers started looking for new jobs, we’d be facing an existential crisis.

Gen Z Wants Office for Outcomes, Not Inputs

You’re absolutely right that Gen Z wants office time for mentorship and collaboration. Here’s what I’ve learned from our Gen Z engineers: they’re optimizing for career growth, not for location preferences.

They come to the office when it serves a purpose:

  • Pairing with senior engineers on complex problems
  • Whiteboarding architecture decisions
  • Building relationships that lead to stretch projects
  • Getting face time with leadership

They don’t come to the office to sit on Zoom calls or write code that could be written anywhere.

The Question We Should Be Asking

Instead of “How many days should people be in the office?” I think the better question is: “What outcomes are we trying to achieve, and what’s the most effective way to achieve them?”

If the outcome is “junior engineers get mentored effectively,” the solution might be 2 days/week of intentional pairing, not 5 days of proximity hoping mentorship happens by accident.

If the outcome is “team cohesion and collaboration,” the solution might be quarterly offsites and weekly team syncs, not daily commutes.

If the outcome is “managers feel in control,” well… then we need to talk about why we’re hiring managers who can’t lead distributed teams.

That’s the conversation I wish more companies were having. Not “What’s Amazon doing?” but “What are we actually trying to accomplish?”

Are we optimizing for control or for outcomes?

3

As a product leader, this RTO conversation drives me crazy because it’s strategy by imitation instead of strategy by customer value.

Here’s what I mean: We spent months analyzing whether our hybrid policy was hurting customer outcomes. We tracked:

  • Product velocity (features shipped per quarter)
  • Customer satisfaction scores
  • Bug rates and production incidents
  • Time to resolve customer issues

Guess what? Our hybrid product team (2-3 days in office) performed identically to our fully in-office sales team on every metric that mattered to customers. Actually, customer satisfaction improved slightly because our engineers were less burned out and more responsive.

The 54% Statistic Should Terrify Us

When I see that “54% of businesses have been influenced by major corporations,” I don’t see strategic thinking. I see cargo cult management.

Copying Amazon’s RTO policy without understanding Amazon’s business model is like copying their AWS infrastructure without understanding their scale requirements. It’s strategy cosplay.

Ask yourself:

  • Do you have Amazon’s real estate commitments?
  • Do you have Amazon’s talent pipeline?
  • Do you have Amazon’s brand that makes people willing to endure policies they hate?

If the answer is no, why are you copying their playbook?

The Real Estate Theory

Here’s my controversial take: I think many RTO mandates are about sunk cost fallacy on office leases, not about productivity.

Companies signed 10-year leases in 2019. Now those offices are sitting empty, and CFOs are looking at $500K/month in rent with 15% utilization. So they mandate RTO to justify the expense, then reverse-engineer a productivity narrative to sell it to employees.

I’m not saying that’s every company. But I am saying that when leadership can’t articulate clear business outcomes that require full-time office presence… it makes you wonder what the real driver is.

What Customer Outcome Are You Optimizing For?

Luis asked great questions. Here’s mine: What customer outcome improves when your team is in the office 5 days instead of 2-3 days?

If you can answer that with data, you have a strategy. If you can’t, you’re following fashion.

Our customers don’t care where our engineers sit. They care about:

  • Feature velocity
  • Product reliability
  • Responsiveness to feedback
  • Innovation that solves their problems

We measured all of those. Hybrid didn’t hurt any of them. So we stayed hybrid.

That’s not ideology. That’s product management.

4

This conversation is playing out in every board room I’m in. Last quarter, an investor literally said to me: “If Amazon thinks 5 days is necessary, why are you doing 3 days?”

My response: “Amazon has different talent dynamics, different retention economics, and different real estate constraints than we do. Should I also copy their compensation structure? Because I don’t have $500K/year to pay senior engineers.”

That ended the conversation.

The Data That Changed My Mind

I’ll be honest: Two years ago, I was skeptical of hybrid. I thought we’d see productivity drops, collaboration failures, culture erosion.

So we tracked it. Religiously. For 18 months.

  • Deployment frequency: No change
  • Incident rates: Actually improved (engineers had more focus time)
  • Employee satisfaction: Up 23%
  • Retention: Up 18% compared to our previous in-office policy
  • Recruiting pipeline: 3x more candidates willing to interview

The data was unambiguous. Hybrid wasn’t just “fine”—it was better for our business in our context.

The Amazon Retention Risk Is Real

Luis mentioned Amazon’s 73% “considering quitting” stat. As a CTO, that number keeps me up at night.

Here’s what most people miss: Amazon can weather that storm because of their brand and their pipeline. We can’t. If even 20% of my engineering team started looking, we’d be in crisis mode.

The companies copying Amazon’s 5-day mandate without Amazon’s brand are playing with fire. You’re betting that your engineers will accept a policy they hate because… why exactly? Because you have unlimited PTO and free snacks?

My Framework for RTO Decisions

When I talk to other CTOs about this, I share a simple framework:

1. Know your talent market
Are you competing for talent against companies offering full remote? Then your 5-day mandate is a recruiting handicap.

2. Know your retention goals
Can you afford 20-30% attrition? If not, you can’t afford to ignore employee preferences.

3. Know your performance data
Does your team actually perform better in the office? Or do you just feel like they do?

If you can’t answer those three questions with data, you’re not making a strategic decision. You’re following fashion.

The Gen Z Angle

Luis is right that Gen Z wants more office time than older cohorts. But “more than remote” doesn’t mean “five days a week.”

Gen Z engineers on my team come in for:

  • Design reviews where whiteboarding matters
  • Pairing sessions with senior engineers
  • Team events and culture building
  • Career conversations with leadership

They don’t come in to sit on Zoom calls with distributed partners or to write code in an open office while wearing noise-canceling headphones.

The question isn’t “office or remote.” The question is “What work requires co-location, and what work requires focus?”

Final Thought

Following Amazon’s playbook without Amazon’s advantages is a strategy for mediocrity at best, disaster at worst.

Build your own strategy. Use your own data. Optimize for your own business model.

That’s what leadership actually is.

5

Oh man, this hits close to home. My failed startup had a full-remote policy, and I thought I was being progressive and forward-thinking. Turns out, I was just copying what other startups were doing without understanding whether it worked for our work.

Spoiler: For creative collaboration and rapid iteration, full-remote was a disaster. We spent more time on Figma comments and Loom videos than we did actually designing together. Our best work happened during the rare moments we were in the same room.

But here’s the thing: The lesson isn’t “remote doesn’t work.” The lesson is “copying without context doesn’t work.”

My Overcorrection

After that startup failed, I swore I’d never do full-remote again. Then I joined a design consultancy that does hybrid—3 days in office for collaboration, 2 days remote for deep work.

And it’s perfect. For our work. For the way design happens. For the balance between creative collaboration and focused execution.

The Gen Z designers on my team have taught me something important: They don’t want to come to the office to check email and attend Zoom calls. They want to come to the office when the office enables something that remote doesn’t.

Creative brainstorming sessions? Office.
Whiteboarding user flows? Office.
Prototyping workshops? Office.
Writing documentation? Home.
Refining designs? Home.
Client presentation prep? Home.

The 54% Are Making My Mistake

Luis, when you said 54% of businesses are being “influenced” by major corporations, I saw my past self in that statistic.

I was influenced by what other startups were doing. I copied their full-remote policies without asking: “What does our actual work require?”

Now I’m watching companies make the opposite mistake—copying Amazon’s 5-day mandate without asking the same question.

Both are wrong. Both are examples of strategic mimicry instead of strategic thinking.

What Work Mode Serves Your Actual Work?

Here’s the question I wish I’d asked myself back then: What work mode serves the work we’re doing, not the industry fashion we’re following?

If you’re writing code that requires deep focus and async collaboration, maybe full-remote is perfect.

If you’re doing rapid design iteration with constant stakeholder feedback, maybe you need more co-location.

If you’re managing distributed teams across time zones, maybe hybrid is a compromise that serves everyone.

The answer depends on your work, not on what Amazon is doing or what Y Combinator startups are doing or what “industry leaders” are doing.

Gen Z Gets This

What I love about the Gen Z folks on my team: They’re pragmatic about it. They’re not ideological about remote vs office. They just want to know: “What’s the best way to do great work?”

When I explain that Wednesday is our collaboration day because we’re workshopping user flows, they show up.

When I explain that Thursday and Friday are deep work days for refining designs, they’re happy to work from home (or a coffee shop, or wherever).

They’re not asking for full remote as a lifestyle perk. They’re asking for intentional hybrid as a productivity tool.

The Meta-Lesson

If you’re copying Amazon’s RTO policy, you’re making the same mistake I made with full-remote: You’re following fashion instead of understanding your context.

The question isn’t “What’s trendy?” The question is “What works for the team we have, doing the work we do, serving the customers we serve?”

That’s a question only you can answer. Amazon can’t answer it for you.