🏢 The Great RTO Showdown: What SF Tech Week Reveals About Remote Work in 2025

Just attended 3 days of “Future of Work” panels at SF Tech Week and I’m processing some uncomfortable truths. The remote work debate isn’t over - it’s entering a new, messier phase. :roller_coaster:

Events attended:

  • CXAI “The Future of Work: Employee Experience, AI, and the Hybrid Revolution”
  • WeWork “Who Will Decide the Future of Work?” panel
  • a16z “Managing Distributed Teams” roundtable
  • Y Combinator “Startup Culture in the Hybrid Era” session

My context: Engineering director, 45-person team, been doing hybrid (3 days in office) since 2023

The Data Bomb That Dropped

From CXAI panel - Fortune 100 research presented:

2023 vs 2025 office mandate comparison:

2023:

  • Fully in-office: 5% of Fortune 100
  • Hybrid: 78%
  • Fully remote: 17%

2025:

  • Fully in-office: 54% of Fortune 100 (!!)
  • Hybrid: 41%
  • Fully remote: 5%

That’s a 10x increase in full RTO in just 2 years.

Major tech companies (Oct 2025 status):

  • Amazon: 5 days/week mandate (started Jan 2025, 350K employees)
  • Google: 3 days/week (but Sundar said “stays flexible if productivity high”)
  • Meta: 3 days/week for hybrid employees
  • Microsoft: 3 days/week (starting Jan 2026)
  • Apple: 3 days/week
  • Salesforce: 3-4 days/week depending on role

The trend is clear: Remote is losing.

The Talent Exodus Reality

Data shared at WeWork panel (from Glassdoor analysis):

Companies with 5-day RTO mandates:

  • Employee turnover: +13% higher than flexible companies
  • Glassdoor rating drop: -0.5 stars average
  • “Would recommend” drop: -12 percentage points

Employee response to 5-day RTO mandate (survey data):

  • 44% would comply
  • 41% would job hunt
  • 14% would quit immediately (!!!)

8 out of 10 companies admitted losing talent due to RTO policies.

But here’s the twist (from a16z panel): Most of those employees who said they’d quit… didn’t. Because the job market in 2025 is tough.

Reality check: Employers have more leverage now than in 2021-2022.

My Team’s Experience (Real Numbers)

Our RTO journey:

2020-2022: Fully remote

  • Productivity: High (shipped 3 major features)
  • Morale: High (flexibility loved)
  • Turnover: 8% (below industry average)
  • Hiring: Easy (could hire anywhere)

2023: Hybrid 2 days/week

  • Productivity: Stable
  • Morale: Some complaints, mostly adapted
  • Turnover: 12% (normal)
  • Hiring: Still good (flexibility marketed)

2024: Hybrid 3 days/week (company mandate)

  • Productivity: Slightly down (more time in meetings)
  • Morale: Mixed (parents struggling most)
  • Turnover: 18% (concerning)
  • Hiring: Harder (candidates ask about remote first)

2025: Considering 4 days/week (CEO pressure)

  • Team response: “Do it and we’ll start looking”
  • Morale: Lowest I’ve seen
  • Productivity: Actually UP (fear of layoffs)
  • Hiring: Very difficult (losing candidates to remote-first companies)

The uncomfortable truth: My team is more productive out of fear, not because office mandates work.

The Productivity Paradox

The big question at every panel: “Does in-office actually improve productivity?”

The data is… inconclusive.

From CXAI research (analyzing Fortune 500 performance):

Companies with 5-day RTO vs. Companies with flexible policies:

  • Stock performance: No significant difference
  • Revenue growth: No significant difference
  • Employee engagement: Flexible policies win by 22%
  • Innovation metrics: No significant difference

Translation: Being in office doesn’t automatically make companies perform better.

But…

From a16z founder roundtable - startup data:

Early-stage startups (pre-Product Market Fit):

  • In-person teams: 18% higher chance of reaching PMF
  • Remote teams: 15% more likely to die (correlation, not causation)
  • Hybrid teams: Middle ground

Growth-stage companies (post-PMF):

  • No statistically significant difference in performance
  • Remote actually slightly better (lower costs, global talent)

Pattern: In-person matters MORE when figuring things out, matters LESS when executing known playbook.

The Real Reasons for RTO (Unspoken)

What CEOs SAY (from panels):

  • “Collaboration is better in person”
  • “Culture needs physical presence”
  • “Innovation happens in spontaneous hallway conversations”

What data actually shows (from WeWork panel economist):

Reason 1: Real estate commitments

  • Many companies locked into 10-year leases
  • Empty offices = wasted money = board questions
  • Average: $500/month per employee for unused space

Reason 2: Management comfort

  • 72% of executives prefer in-office (vs 32% of ICs)
  • Managers feel more in control when they see people
  • “Butts in seats” = work getting done (perception)

Reason 3: Performance management

  • Easier to monitor in-office
  • Harder to fire remote workers (documentation burden)
  • 86% of CEOs said they’ll “reward” office attendance (KPMG survey)

Reason 4: Justified headcount reductions

  • RTO mandate → voluntary attrition → no severance costs
  • Amazon example: Some estimate 10-15% quit after 5-day mandate
  • Quiet layoffs without calling them layoffs

Controversial take from one panelist: “RTO mandates are a backdoor layoff strategy.”

The Generational Divide

Data from We Work Remotely 2025 survey:

Gen Z (entered workforce during pandemic):

  • 67% prefer remote or hybrid
  • 41% would take 10% pay cut for full remote
  • 58% say they’re more productive at home
  • Major concern: “I don’t know how to network in person”

Millennials (established pre-pandemic):

  • 72% prefer hybrid (not full remote)
  • 35% miss office social aspects
  • 52% say productivity same remote vs office
  • Major concern: “I need boundaries between work and home”

Gen X / Boomers (leadership roles):

  • 54% prefer in-office 4-5 days/week
  • 62% believe in-person builds better culture
  • 48% think remote workers are less committed
  • Major concern: “I can’t tell if my team is working”

At the WeWork panel, a Gen Z founder said: “My biggest competitive advantage is offering remote work. I can hire senior talent from FAANG companies who don’t want to RTO.”

Boomer executive response: “You’ll learn why culture matters when you try to scale.”

The room got tense.

The Hybrid Trap

From a16z roundtable - “Why hybrid is hardest”:

Problems with hybrid:

1. The “proximity bias” effect

  • People in office get more visibility
  • Remote days = out of sight, out of mind
  • Promotions favor office-goers (data: +15% more likely)

2. The meeting hell problem

  • Hybrid means: Some in room, some on Zoom
  • Zoom people are second-class citizens in discussion
  • Result: Schedule all meetings for in-office days
  • In-office days become 6 hours of back-to-back meetings

3. The coordination nightmare

  • “Let’s sync on Tuesday” - half team not in office
  • Core hours required → defeats flexibility purpose
  • Social cliques form among people with same in-office days

4. The “worst of both worlds”

  • Lost flexibility of remote
  • Lost spontaneity of full in-office
  • Added: Commute some days (still need to live close)
  • Added: Maintain home office + desk in office

My experience: Hybrid is hardest to manage. It’s not a middle ground, it’s a different (harder) mode.

The Cost Analysis Nobody Talks About

From my own calculation (shared at roundtable):

Per employee annual cost:

Full remote:

  • Salary: $150K
  • Home office stipend: $2K
  • Equipment: $3K amortized
  • Total: $155K

Hybrid (3 days/week):

  • Salary: $150K (same)
  • Office space: $6K ($500/month allocated)
  • Home office: $1K (still need some)
  • Equipment: $3K (need both setups)
  • Commute subsidy: $2K
  • Total: $162K

Full in-office:

  • Salary: $165K (need to pay more, less competitive otherwise)
  • Office space: $10K ($833/month allocated)
  • Equipment: $3K
  • Commute subsidy: $3K
  • Total: $181K

For a 50-person engineering team:

  • Remote: $7.75M
  • Hybrid: $8.1M (+$350K)
  • In-office: $9.05M (+$1.3M vs remote)

ROI question: Is that $1.3M difference worth it for “better culture”?

Depends on who you ask.

What Actually Works (Real Examples)

From Y Combinator session - successful models:

Model 1: “Remote-first with offsites”

  • Example: GitLab, Zapier, Automattic
  • Daily: Fully remote, async-first
  • Quarterly: Week-long team offsites
  • Cost: ~$3K/employee/quarter for offsites
  • Employee satisfaction: Very high
  • Productivity: High (measured by output)

Model 2: “Hub-and-spoke”

  • Example: Coinbase, Stripe
  • Offices in 3-4 cities
  • Teams choose their hub
  • No mandate for specific days
  • Cost: Lower than traditional (smaller offices)
  • Flexibility: High (choose your hub)

Model 3: “Core days”

  • Example: Atlassian, Salesforce
  • Tuesday-Thursday required in office
  • Monday/Friday flexible
  • Everyone knows when team will be together
  • Cost: Can reduce office space (not everyone Mon/Fri)
  • Balance: Predictability + flexibility

Model 4: “Results-only” (most controversial)

  • Example: Some YC startups
  • Zero mandates
  • Measured purely on deliverables
  • Annual performance review decides if it’s working
  • Cost: Lowest (minimal office)
  • Risk: Requires strong performance culture

The YC partner’s take: “Remote works if your culture and processes work. If they don’t, RTO won’t fix that.”

My Biggest Takeaways

1. The “return to 2019” is impossible

People have restructured their lives:

  • Moved to cheaper cities
  • Took on caretaking responsibilities
  • Built home offices
  • Adjusted lifestyle

You can’t just undo 5 years.

2. One-size-fits-all policies fail

Different roles need different setups:

  • Early-stage founders: More in-person helps
  • Senior ICs: Remote is often better (deep work)
  • Managers: Need some in-person (relationship building)
  • Parents: Flexibility matters most

3. Trust is the real issue

If you don’t trust your team to work remote, you have a hiring problem or a management problem, not a location problem.

4. The market decides

In tight labor markets: Employees win (2021-2022)
In loose labor markets: Employers win (2024-2025)

Right now, employers have leverage. But that won’t last forever.

The Uncomfortable Prediction

From multiple panelists (consensus forming):

Next 2-3 years:

  • More companies will mandate 4-5 days in-office
  • Employees will comply (job market is tough)
  • Talent will quietly leave when they can
  • Companies with flexible policies will win the talent war

5-10 years:

  • Pendulum swings back toward flexibility
  • Younger generation enters leadership
  • Companies that stayed flexible will have built remote-capable cultures
  • Companies that forced RTO will struggle to compete for talent

One panelist: “RTO mandates in 2025 are optimizing for short-term control at the expense of long-term talent strategy.”

Another panelist (CEO): “We’re optimizing for survival. Long-term doesn’t matter if we don’t make it to long-term.”

Both are right.

What I’m Doing

My plan (shared this with my CEO):

Pushing back on 4-day mandate:

  • Showed him the turnover data (18% is expensive)
  • Showed him the hiring difficulty data
  • Made the cost argument ($1.3M difference)

Alternative proposal:

  • Keep 3 days/week hybrid
  • Mandate Tuesday-Wednesday-Thursday (core days model)
  • Make Monday/Friday no-meeting days for deep work
  • Quarterly team offsites (add intentional culture time)
  • Results-based performance (ship or don’t, location doesn’t matter)

His response: “Let me think about it. Board wants butts in seats.”

Translation: I’ll probably lose this fight.

My backup plan: Start building relationships with remote-first companies, just in case my team starts leaving.

Questions for the Forum

For other engineering leaders:

  1. What’s your company’s RTO policy?
  2. How is it actually going (honest assessment)?
  3. Have you seen productivity changes?
  4. What’s your turnover like?

For ICs:

  1. How many days/week are you in office?
  2. Would you leave for a remote role?
  3. Do you actually collaborate better in-person, or is it just meetings?

For founders:

  1. How did you decide your remote policy?
  2. Would you change it if you could?

Luis :bar_chart:

SF Tech Week - Future of Work panels

Sources:

  • Fortune 100 RTO Analysis (July 2025)
  • Glassdoor Employee Satisfaction Study (2025)
  • KPMG CEO Survey (2025)
  • We Work Remotely State of Remote Work Report (2025)
  • a16z Startup Performance Data

@eng_director_luis - From the IC trenches, let me tell you what the data doesn’t show. :laptop:

My situation:

  • Senior engineer, 8 years experience
  • 3 days/week in office (Tue/Wed/Thu mandate)
  • 45-minute commute each way
  • Single parent (6-year-old daughter)

The Reality vs. The Narrative

What executives say:
“We need people in the office for collaboration and spontaneous innovation.”

My actual experience:

Tuesday (office day):

  • 7:00 AM: Wake up, rush daughter to before-school care
  • 8:00 AM: Commute (stressed about being late)
  • 9:00 AM: Arrive, grab coffee, check Slack missed overnight
  • 9:30 AM: Stand-up meeting
  • 10:00 AM: “Quick sync” that could’ve been a Slack message
  • 11:00 AM: Finally sit down to code
  • 11:15 AM: Tapped on shoulder for “quick question”
  • 11:45 AM: Actual coding
  • 12:00 PM: Lunch (optionally social)
  • 1:00 PM: Design review meeting
  • 2:30 PM: Back to desk
  • 2:45 PM: Another “quick question” interruption
  • 3:30 PM: Sprint planning
  • 5:00 PM: Rush to leave (need to pick up daughter)
  • 5:45 PM: Pick up daughter
  • 6:30 PM: Home, dinner, bedtime routine
  • 8:30 PM: Daughter asleep, check if anything urgent
  • 9:00 PM: Too exhausted to do anything

Code written: Maybe 2 hours of actual focused work

Wednesday (office day): Basically same pattern

Thursday (office day): Same again

Monday (remote day):

  • 7:00 AM: Wake up, daughter to school (15 min drive)
  • 7:30 AM: Back home, coffee, start work
  • 8:00 AM: Standup (video)
  • 8:30 AM: Deep work (no interruptions!)
  • 12:00 PM: Lunch break
  • 12:30 PM: More deep work
  • 3:00 PM: Pick up daughter
  • 3:30 PM: She does homework, I continue working
  • 5:30 PM: Dinner
  • 7:00 PM: If needed, finish up work
  • 8:00 PM: Family time

Code written: 6+ hours of focused work

Friday (remote day): Similar to Monday

My productivity:

  • Monday + Friday remote: 60% of my actual output
  • Tue/Wed/Thu office: 40% of my actual output

But I’m “expected” to be in office 3 days for “collaboration.”

The Proximity Bias Is Real

From SF Tech Week panels - they talked about this, let me confirm it:

Last 6 months at my company:

Promotions announced:

  • 8 people promoted to senior/staff level
  • 7 of them: In office 4-5 days/week (even though only 3 required)
  • 1 of them: Strict 3 days (that was me, took 2 years)

High-visibility projects:

  • “Critical customer escalation” → Goes to person in office
  • “Presenting to exec team” → Goes to person in office
  • “Represent eng in product meetings” → In-office people

Why: Because managers see you. They assume you’re working harder if they see you at your desk.

The irony: The person at their desk might be on Twitter. I’m actually shipping features from home.

But perception > reality.

The Meeting Hell Luis Mentioned

Let me elaborate on the hybrid meeting problem:

Scenario: Design review with 10 people

  • 6 people in conference room
  • 4 people on Zoom

What happens:

  1. In-room people start talking
  2. Zoom audio is bad, can’t hear everything
  3. Someone draws on whiteboard
  4. Can’t see it on camera
  5. Side conversations happen in room
  6. Zoom people miss context
  7. Decision gets made
  8. Zoom people: “Wait, what did we decide?”

Every. Single. Time.

The fix: Make everyone join Zoom individually, even if in office.

What actually happens: “Just join from the conference room, it’s easier.”

Result: Hybrid meetings suck for remote participants.

The Cost Nobody Counts

@eng_director_luis showed company costs. Here’s MY cost:

Working 3 days in office:

Financial:

  • Commute: $200/month (gas + parking)
  • Before/after school care: $600/month (need coverage 7-6pm)
  • Lunch out: $300/month (cafeteria isn’t free anymore)
  • “Office appropriate” clothes: $100/month amortized
  • Total: $1,200/month = $14,400/year

Non-financial:

  • Commute time: 1.5 hours/day Ă— 3 days = 4.5 hours/week
  • That’s 234 hours/year = 29 full work days
  • Sleep lost (earlier wake up): ~1 hour/night Ă— 3 = 3 hours/week
  • Stress: Unquantifiable but REAL

For remote work:

  • Commute: $0
  • Childcare: $0 (school hours match work hours)
  • Lunch: $150/month (cook at home)
  • Clothes: Pajamas are free
  • Total: $1,800/year

I’m paying $12,600/year out of pocket to work in the office 3 days a week.

And I’m not even getting paid more than fully remote companies offer.

Why I Haven’t Quit (Yet)

The honest reasons:

1. Job market is tough

From SF Tech Week conversations and personal experience:

  • Applied to 15 remote roles in last 6 months
  • Got 2 interviews
  • 0 offers
  • Most common response: “Hundreds of applicants”

2021-2022: Companies begged me to interview
2025: I’m lucky to get a rejection email

2. Golden handcuffs

  • Equity vests over 4 years
  • I’m in year 3
  • $80K unvested equity
  • Can’t walk away from that

3. Team is good

  • Like my manager (even though I disagree with policy)
  • Like my teammates
  • Interesting work
  • Don’t want to start over

4. Family stability

  • Daughter’s school and friends are here
  • Can’t relocate easily
  • Remote jobs that pay same as my comp: Rare

But…

I’m updating my resume.

I’m taking recruiter calls.

If a good remote opportunity comes up after my equity vests, I’m gone.

And I’m not alone. At least 5 people on my team (45 people total) have told me they’re looking.

That’s 11% of team actively job hunting.

Management doesn’t know this. Or they don’t care.

What Actually Works for Collaboration

The “spontaneous hallway conversations” argument:

In 18 months of hybrid, I’ve had meaningful spontaneous collaboration: 3 times.

3 times in 18 months.

Meaningful planned collaboration (Zoom or in-person): 40+ times.

The best collaboration sessions I’ve had:

  1. Scheduled 2-hour deep dive with another engineer on architecture
  2. Async design doc with 10+ people contributing over 3 days
  3. Weekly office hours where anyone can drop in with questions

None of these require being in office 3 days/week.

What I’d actually benefit from:

  • Monthly team offsite (full day, intentional collaboration)
  • Quarterly all-hands in person
  • Annual company gathering

That’s 15 in-person days/year, not 156.

The Generational Gap Luis Mentioned

I’m a millennial (35 years old). Let me confirm the data:

Older colleagues (45+):

  • Love being in office
  • “I need the separation of work and home”
  • “How do you know people are working if you can’t see them?”
  • Often: Empty nest, no kids at home, larger houses with dedicated offices

My generation (30-40):

  • Want flexibility
  • “I have family responsibilities”
  • “I’m more productive at home”
  • Often: Young kids, smaller living spaces, balancing a lot

Younger colleagues (Gen Z, <30):

  • Actually MORE want to be in office than I expected
  • “I live in a studio apartment, I need to get out”
  • “How do I network and learn if everyone’s remote?”
  • “I feel isolated at home”

But here’s the key: Gen Z wants the OPTION. They want to come in when it helps them. They don’t want it MANDATED.

One junior engineer told me: “I’d come in 4 days a week if it was my choice. But being forced 3 days makes me resent it and want to come in 0 days.”

Psychology is weird.

What Would Make Me Happy

My ideal setup:

Core collaboration days:

  • Tuesday and Wednesday required in office
  • Everyone on team is there
  • Schedule all meetings, planning, design reviews
  • Intentional collaboration

Focus days:

  • Monday, Thursday, Friday: Remote optional
  • These are for deep work
  • No meetings allowed (team agreement)
  • Come in if you want social time, work from home for focus

Quarterly offsites:

  • 2-3 days offsite
  • Mix of work and social
  • Build relationships intentionally
  • Not just “required office attendance”

Measure outcomes, not presence:

  • Did you ship your features?
  • Did you help your teammates?
  • Did you improve the codebase?
  • Location doesn’t matter if you’re delivering

This would:

  • Give me back 2 commute days/week (save $500/month, 15 hours/month)
  • Let me choose when I need office vs. home
  • Actually improve collaboration (intentional vs. forced)

But instead: Rigid 3-day mandate that helps nobody.

The Trust Issue

@eng_director_luis said it: “Trust is the real issue.”

Let me confirm from IC side:

Every RTO mandate sends this message:
“We don’t trust you to work unless we can see you.”

It’s insulting.

I’ve been at this company 5 years.
I’ve shipped 3 major products.
I’ve mentored 4 junior engineers.
I’ve gotten “exceeds expectations” every review.

But apparently I can’t be trusted to work from home more than 2 days/week?

The cognitive dissonance is real:

  • Company: “We hire the best talent!”
  • Also company: “We need to watch you to make sure you work!”

Pick one.

My Prediction

Based on conversations at SF Tech Week and with peers:

Next 12 months:

  • Companies continue RTO mandates
  • Employees comply (market is tough)
  • Quiet resentment builds
  • Productivity stays same or drops (malicious compliance)
  • Best performers start leaving (they have options)

12-24 months:

  • Job market improves (economic recovery)
  • Great resignation 2.0
  • Companies with rigid RTO lose talent fast
  • Emergency policy reversals (“We’re going hybrid again!”)
  • Too late, trust is broken

3-5 years:

  • Flexible work becomes standard again
  • In-person 5 days becomes rare (except finance, maybe)
  • Companies that stayed flexible have competitive advantage
  • Companies that forced RTO have cultural damage

I’ve seen this movie before. After 2008, companies cut benefits. Then talent left when economy recovered. Took years to rebuild trust.

Same pattern.

To Other ICs

If you’re in similar situation:

1. Document your productivity

  • Track what you ship
  • Show that you deliver regardless of location
  • Data helps when negotiating

2. Build your runway

  • Save money
  • Update resume
  • Build side projects (show you can work independently)

3. Set boundaries

  • If they mandate office days, leave on time
  • Don’t compensate by working nights
  • Let the productivity data speak

4. Find allies

  • Talk to other ICs feeling same way
  • Strength in numbers
  • Collective feedback is harder to ignore

5. Vote with your feet

  • If policy doesn’t change and you have options, leave
  • Companies that don’t listen to employees don’t deserve them

To managers like @eng_director_luis who are trying:

Thank you for fighting for us. We see it. We appreciate it. Even if you lose the battle, knowing you tried matters.

David :laptop:

SF Tech Week observations from the IC perspective

Adding the executive perspective from the WeWork “Who Will Decide the Future of Work?” panel. I’m the “bad guy” in this debate. :necktie:

My role: CTO, 200-person engineering org, Series C startup

Our policy: 4 days/week in office (Mon-Thu), started Jan 2025

Why I’m responding: Because @eng_director_luis and @product_david are both right about the individual trees, but missing the forest.

Why We Mandated RTO (The Honest Version)

What I told the company:
“We need better collaboration, culture, and innovation. Our remote-first setup wasn’t working.”

The full truth (shared at SF Tech Week panel):

Reason 1: Productivity WAS down

Not for everyone. Not even for most people. But for enough people that it mattered.

Our data (6 months pre-RTO):

  • 15% of engineers: Clearly productive (PRs, delivery, communication)
  • 70% of engineers: Hard to tell (some good work, some invisible)
  • 15% of engineers: Red flags (low output, slow response, concerns)

The problem: In remote setup, it took 6-9 months to identify and address low performers.

In office: We spot issues in 2-3 months.

Why: In-person, you overhear conversations. You see who’s stuck. You notice patterns. Remote, everything is hidden until quarterly review.

Cost of keeping low performer for 9 months: ~$150K salary + opportunity cost

We had 3 people we should’ve managed out after 3 months. Took 9 months remote.

Cost: $450K that should’ve been spent on better hires.

Reason 2: Junior engineers were struggling

Our data:

  • Junior engineers (0-2 years) promoted in 18 months: Pre-pandemic 40% → Remote era 18%
  • Time to productivity for new grads: 3 months → 7 months
  • Satisfaction scores from juniors: 3.2/5.0 (concerning)

Why: Juniors learn by osmosis.

  • Overhearing senior engineers debug problems
  • Watching how experienced people handle difficult conversations
  • Quick “hey, how do I…” questions

Remote, all of this becomes scheduled, formal, heavyweight.

Senior engineers don’t want to hop on Zoom for “quick questions” 5 times/day. So juniors stay stuck longer.

Our best junior engineers literally asked for more office time.

Reason 3: Culture was fragmenting

What we noticed (soft data, but real):

  • Teams that worked together pre-pandemic: Still cohesive
  • New teams formed during pandemic: Struggling to gel
  • Cross-team collaboration: Down 30% (measured by PR reviews across teams)
  • “Us vs. them” forming between teams

Example:
Backend team (mostly in SF) vs. Frontend team (distributed) started having tension. Slack messages getting terse. Meetings became confrontational.

Root cause: They never spent time together. They were just usernames on Slack.

After RTO: They got drinks after work once. Tension dropped 80%.

Humans need in-person connection to trust each other.

Reason 4: The real estate

Yes, @eng_director_luis, you’re right. We have $2.5M/year lease through 2029. It’s empty. Board asked: “Why are we paying for this?”

I gave the collaboration/culture answer. But truthfully, the empty office was embarrassing.

Could we have subleased? Maybe. But that takes time and we’d still lose money.

Reason 5: Competitive pressure

From SF Tech Week panel discussion:

When Amazon, Meta, Google all mandate RTO, there’s peer pressure.

Board members ask: “Why are we different? What do we know that they don’t?”

VCs asked: “Are you sure remote is working? Everyone else is going back.”

I had to defend remote setup constantly. It was exhausting.

RTO mandate stopped those questions.

What Happened After RTO

The results (8 months in):

Positive:

  • Junior engineer satisfaction: 3.2 → 4.1/5.0
  • Time to productivity for new hires: 7 months → 4 months (better but not pre-pandemic)
  • Cross-team collaboration: Up 25% (back to pre-pandemic)
  • Low performer identification: Faster (spotted 2 issues in 3 months)

Negative:

  • Voluntary attrition: 12% → 22% annually (!!!)
  • Employee satisfaction (overall): 4.0 → 3.4/5.0
  • Recruiting: 30% harder (candidates decline over RTO policy)
  • Cost: +$500K/year (office upgrades, subsidies, etc.)

The 22% attrition is the killer.

Who left:

  • 8 senior engineers (out of 25)
  • 3 engineering managers (out of 12)
  • 2 staff engineers (out of 4)

Pattern: Best performers left. They had options.

Who stayed:

  • Mid-performers (happy or can’t get other jobs)
  • People with golden handcuffs
  • True believers in company mission

Net effect on team quality: DOWN.

Was it worth it? I’m not sure anymore.

The Data That Haunts Me

From CXAI panel - research I wish I’d seen before our RTO mandate:

Companies that mandated RTO:

  • Glassdoor ratings: -0.5 stars average
  • “Would recommend”: -12 percentage points
  • Turnover among top performers: +25%
  • Turnover among women: +30%
  • Time to hire replacement: 4-6 months
  • Cost of turnover: $150K-250K per senior engineer

For us:

  • Lost 8 senior engineers
  • Cost: $1.2M - $2M (conservative estimate)
  • Replacement time: Still hiring (some roles open 6 months)
  • Team morale hit: Significant (remaining engineers see friends leave)

Meanwhile:

  • Junior engineers are happier (+0.9 points)
  • Cross-team collaboration is better (+25%)

Trade-off: Helped juniors, hurt seniors.

Was it worth losing 32% of senior engineers to help juniors? That’s the question that keeps me up.

What I’d Do Differently

If I could rewind to Jan 2025:

Instead of 4-day mandate, I’d do:

Tier-based policy:

  • Juniors (0-2 years): 4 days/week encouraged, resources to support
  • Mid-level (2-5 years): 2 days/week required (core days)
  • Seniors (5+ years): Flexible, results-based

Rationale:

  • Juniors benefit most from in-person
  • Seniors are self-directed, trust them
  • Mid-level needs some structure but not full-time

Quarterly offsites:

  • Entire eng org together 2-3 days
  • Mix of work and social
  • Build cross-team relationships
  • Budget: $150K/quarter vs. $2.5M/year real estate

Results-based performance:

  • Clear deliverables per engineer
  • Measured on output, not input
  • Monthly check-ins on progress
  • Location doesn’t matter if you’re delivering

This would have:

  • Kept senior engineers happy (flexibility)
  • Helped junior engineers (support)
  • Reduced real estate waste (smaller office)
  • Cost less than full RTO

But I didn’t have this data. I made the decision with pressure from board, peer pressure from other companies, and incomplete information.

I own that mistake.

The Trust Problem (From Executive Side)

@product_david said RTO sends message: “We don’t trust you.”

He’s right. And here’s the uncomfortable truth:

I don’t trust everyone.

Not because of location. Because we have 200 engineers and I can’t personally know all of them.

I trust:

  • People I’ve worked with for years
  • People with proven track record
  • People who communicate well

I don’t know if I trust:

  • New hires I’ve never met in person
  • People on teams I don’t work with directly
  • People who are quiet in meetings

In office, I run into people. I overhear things. I get signals.

Remote, I only see what they choose to show me.

That’s scary when you’re responsible for 200 people’s performance.

Is this a me problem? Probably.

Is it also a real problem? Yes.

Solution isn’t RTO mandate. Solution is better systems for visibility and communication.

But building those systems is hard. RTO is easy.

I took the easy path. And it cost us senior talent.

The Economic Reality

From SF Tech Week panels - why RTO is happening now:

2021-2022: Tight labor market

  • Employees had leverage
  • Companies competed on flexibility
  • Remote work was recruiting advantage

2024-2025: Loose labor market

  • Employers have leverage
  • Layoffs, hiring freezes
  • Employees scared to leave
  • RTO mandates with less pushback

The data:

  • 44% of employees would comply with 5-day RTO
  • 41% would job hunt (but not necessarily leave)
  • 14% would quit immediately

Only 14% would actually quit.

That’s the calculation:

  • Lose 14% of workforce (worst performers self-select out)
  • Keep 86% (save on severance)
  • Cheaper than layoffs

One panel had CEO who literally said: “RTO is a productivity-based voluntary layoff.”

The room gasped. But he’s not wrong.

Companies are using RTO to trim workforce without severance costs.

Are we doing that? Honestly, it’s a side benefit we didn’t expect.

What I’m Seeing in the Industry

From a16z roundtable - CTO peer group data:

Startups (pre-Series B):

  • 70% have some form of RTO mandate
  • Rationale: “Need to move fast, easier in-person”
  • Attrition: High, but startups always have high attrition

Growth companies (Series B-D):

  • 60% have RTO mandates
  • Rationale: “Building culture, preparing for IPO”
  • Attrition: 20-30% spike after RTO

Public companies:

  • 85% have RTO mandates
  • Rationale: “Shareholder value, real estate, tradition”
  • Attrition: Lower (people more locked in with equity)

Fully remote companies (GitLab, Zapier, etc.):

  • 100% still remote (obviously)
  • Recruiting advantage: HUGE
  • Hiring from FAANG engineers who don’t want RTO
  • Productivity: High (they built systems for it)

The bifurcation is happening:

  • Companies going all-in on in-person
  • Companies going all-in on remote
  • Hybrid is becoming rare (hardest to execute well)

My Advice to Other CTOs

If you’re considering RTO mandate:

1. Be honest about why

Don’t hide behind “collaboration” if it’s really about real estate or control.

Your team will see through it. Trust will erode.

2. Measure everything

Before RTO:

  • Baseline productivity (PRs, velocity, delivery)
  • Baseline satisfaction (surveys)
  • Baseline attrition

After RTO:

  • Track same metrics
  • See what actually changes
  • Be willing to reverse if data is bad

3. Different policies for different roles

Juniors benefit from in-person. Seniors often don’t. One-size-fits-all will hurt someone.

4. Invest in alternatives

Before mandating RTO, try:

  • Better async communication tools
  • Regular offsites
  • Intentional culture building
  • Clear performance metrics

RTO is easy. These are hard. But these might work better.

5. Prepare for attrition

You WILL lose people. Budget for:

  • Severance (some will negotiate exit)
  • Recruiting costs
  • Knowledge transfer time
  • Morale hit

If you’re not willing to lose 15-20% of team, don’t do RTO mandate.

What I’m Doing Now

Our situation (8 months post-RTO):

Problems:

  • Down 8 senior engineers (25% of senior talent)
  • Recruiting is slow
  • Remaining seniors are updating resumes (I can tell)

Options:

Option A: Double down

  • Keep 4-day mandate
  • Accept attrition
  • Hire replacements (cheaper, junior-heavy)
  • Focus on the 78% who are happy or compliant

Option B: Reverse course

  • Go back to flexible
  • Admit mistake
  • Try to win back trust

Option C: Compromise

  • Reduce to 2-day mandate (core days)
  • Keep quarterly offsites
  • Rebuild trust slowly

I’m advocating for Option C with CEO and board.

CEO response: “We already made the change. Reversing looks weak.”

My response: “Losing more senior engineers is weaker.”

We’ll see what board says next month.

To @eng_director_luis

Your proposal (3 days with core days, quarterly offsites) is exactly what I wish I’d done.

Fight for it. Show the attrition data. Make the economic argument.

If your CEO won’t listen, at least you tried. Your team will remember that.

To @product_david

I’m sorry. Not personally (I don’t know you), but as a representative of executives who made decisions that hurt good engineers like you.

We’re not evil. We’re making decisions with incomplete information, under pressure, trying to do what’s best for company.

Sometimes we get it wrong.

Your point about trust is right. We should trust proven performers.

The challenge is: Systems that work for 10 people don’t work for 200 people. We need structure. We need visibility.

But RTO mandate isn’t the answer.

Better systems are. I just don’t know what those look like yet.

The Uncomfortable Truth

What I learned at SF Tech Week:

There’s no universal answer to remote vs. in-office.

What works:

  • Remote for companies that built systems for it
  • In-office for early-stage startups figuring things out
  • Hybrid for companies willing to do the hard work of making it work

What doesn’t work:

  • Forcing people back without reason
  • Mandating one-size-fits-all policies
  • Ignoring the data when it’s bad

We forced people back without good enough reasons.

We mandated one-size-fits-all.

We’re now seeing the data is bad (22% attrition).

And we might be too proud to reverse course.

That’s on us.

Michelle :bullseye:

SF Tech Week - “Who Will Decide the Future of Work?” panelist

Sources:

  • Internal company data (anonymized)
  • CXAI “Future of Work” research
  • a16z CTO roundtable insights

Adding the design perspective because remote vs. in-person hits different for creative work. :artist_palette:

My situation:

  • Product designer, 6 years experience
  • Fully remote since 2020
  • Company went hybrid (3 days) in 2024, now considering 4 days in 2025

Design Work Is Different

@eng_director_luis @product_david @cto_michelle - all great points, but design work has unique challenges:

For engineering:

  • Deep work: Coding alone
  • Collaboration: Code reviews, technical discussions
  • Output: Measurable (PRs, lines of code, features shipped)

For design:

  • Deep work: UI design, prototyping (alone)
  • Collaboration: CONSTANT (PMs, engineers, stakeholders, users)
  • Output: Subjective (hard to measure “good design”)

The remote vs. in-person trade-off hits different for us.

My Productivity Breakdown

Solo design work (Figma, prototyping):

  • Remote: 10/10 (focus, no interruptions, comfortable setup)
  • In-office: 6/10 (interruptions, worse monitors, commute exhaustion)

Remote wins massively.

Collaborative design work (brainstorming, feedback, iteration):

  • Remote: 6/10 (Figjam works, but missing energy)
  • In-office: 9/10 (whiteboarding, rapid iteration, reading body language)

In-office wins significantly.

Client/stakeholder presentations:

  • Remote: 8/10 (screen-sharing is great, can show prototypes)
  • In-office: 8/10 (both work fine)

Tie.

User research/testing:

  • Remote: 7/10 (can test with anyone, recording is easy)
  • In-office: 8/10 (better for in-person observation, but limited to local users)

Slight edge to in-office.

Net: I need BOTH. But in different ratios than engineers.

What Actually Works for Design

My ideal setup:

Monday-Tuesday-Friday: Remote

  • Solo design work
  • Execution on designs already decided
  • User research sessions (video call)
  • Async feedback loops

Wednesday-Thursday: In-office

  • Design critiques (need whiteboard)
  • Brainstorming sessions
  • Cross-functional planning
  • User testing in office

Quarterly offsites:

  • Design team bonding
  • Vision/strategy sessions
  • Portfolio reviews

This would give me:

  • 60% deep work time (remote)
  • 40% collaborative time (in-office)
  • Intentional culture building (offsites)

Instead, I’m being forced 3 random days/week that don’t align with my actual collaboration needs.

The Design Team Attrition Story

Our team (12 designers):

Pre-RTO (2020-2023): Fully remote

  • Attrition: 10% annually (normal)
  • Hiring: Easy (could hire anywhere)
  • Team satisfaction: 4.5/5.0

Post-RTO (2024-present): 3 days/week mandate

  • Attrition: 40% (!!!) - 5 out of 12 designers left
  • Hiring: Impossible (candidates ask about remote-first)
  • Team satisfaction: 2.8/5.0

Who left:

  1. Senior designer with 2 kids (moved to Austin, got remote job)
  2. Lead designer (went to Figma - fully remote)
  3. Mid-level designer (moved to competitor with 1-day/week policy)
  4. Junior designer (burnout from commute)
  5. Senior designer (me? Not yet, but considering)

Why they left (exit interviews):

  • 4 out of 5: RTO policy was primary reason
  • 3 out of 5: Had remote offers paying same or more
  • 2 out of 5: Relocated during pandemic, can’t move back

Cost to replace 5 designers: $500K+ (recruiting, ramp-up time, lost productivity)

Was it worth it to have people in office 3 days?

Management says yes (better collaboration).

Reality: We lost half our team.

The Collaboration Myth for Design

Management’s argument:
“Designers need to collaborate in person. Whiteboarding can’t happen remotely.”

My experience:

Tools that work great remotely:

  • Figma (real-time collaboration, better than in-person)
  • FigJam (digital whiteboarding, saves everything)
  • Miro (brainstorming, dot voting, workshops)
  • Loom (async video feedback)
  • Zoom (screen sharing, annotations)

Things that ARE better in person:

  • Reading body language in critique
  • Energy of group brainstorming
  • Spontaneous “let me show you” moments
  • Building trust with new stakeholders

But I don’t need 3 days/week in office for these.

I need:

  • 1-2 focused collaboration days/week
  • Quarterly in-person workshops
  • Async-first culture with intentional sync time

The 3-day mandate gives me:

  • Lots of interruptions
  • Meetings that could be async
  • Commute exhaustion
  • Resentment

The Gender Angle Nobody Talks About

From CXAI panel - data that hit hard:

RTO mandates increase turnover disproportionately for:

  • Women: +30% turnover vs. men
  • Parents: +25% turnover vs. non-parents
  • Caregivers: +35% turnover

Why:

  • Women still bear majority of childcare (unfair but true)
  • Elder care often falls on women
  • Flexibility matters more for caregivers

Our design team:

  • Pre-RTO: 60% women (7 out of 12)
  • Post-RTO: 40% women (3 out of 7 remaining)

We lost 4 women, 1 man.

This isn’t explicitly sexist. But the IMPACT is gendered.

RTO mandates are quietly reversing diversity gains.

I pointed this out to HR.

HR response: “Interesting data. We’ll keep an eye on it.”

Translation: Nothing will change.

What Remote-First Design Teams Do Better

I interviewed at 3 remote-first companies (Figma, GitLab, Zapier). Here’s what they do that my company doesn’t:

1. Async-first feedback

  • All design work posted in Figma with clear asks
  • Comments are detailed and thoughtful (not rushed in meetings)
  • People can respond when they have time to think
  • Better feedback quality

2. Intentional sync time

  • Design critiques are scheduled, not spontaneous
  • Full hour with no interruptions
  • Everyone comes prepared
  • Much more productive than “hey can you look at this real quick?”

3. Documentation culture

  • Every decision is documented
  • Design systems are thorough
  • New designers can onboard without shadowing
  • Knowledge doesn’t live in people’s heads

4. Regular offsites

  • Quarterly team gatherings
  • Mix of work and social
  • Build relationships intentionally
  • Return with renewed energy

5. Higher pay

  • Can hire globally
  • Save on office costs
  • Invest savings in higher salaries
  • Attract top talent

Result: Remote-first design teams at these companies are HIGH performing, despite never being in office.

Difference: They built systems for remote. We just went remote by accident (pandemic) and never fixed our processes.

The Real Reason for RTO (Design Edition)

What management says:
“Designers need spontaneous collaboration.”

What I think is actually happening:

Creative directors are lonely.

Senior leadership (mostly older, mostly male, mostly empty-nesters) LIKE being in office.

They feed off the energy. They like hallway conversations. They like feeling like they’re at the “center of things.”

They’re projecting their preferences onto everyone.

Evidence:

  • Our Chief Design Officer is in office 5 days/week
  • He “drops by” people’s desks constantly
  • He calls these “spontaneous check-ins”
  • We call them “interruptions”

He LOVES in-office work. So he assumes we do too.

But I’m 32, I have a partner and a dog, I live 45 minutes away, and I don’t want to be “spontaneously checked in on” 5 times a day.

Different life stages, different preferences.

But policy is one-size-fits-all.

My Decision Point

I’m currently:

  • Updating my portfolio
  • Interviewing at remote-first companies
  • Figma, GitLab, and a startup have reached out
  • All offer remote + similar or better pay

What would make me stay:

  • Reduce to 2 days/week (core collaboration days)
  • Quarterly offsites
  • Invest in async design culture
  • Stop the “spontaneous” interruptions

What will make me leave:

  • Increase to 4 days/week
  • Mandate is inflexible
  • Management doesn’t listen to feedback
  • Another designer on my team leaves (morale will collapse)

I give it 3 months. If nothing changes, I’m out.

And I’m one of the 3 most senior designers left. My leaving would hurt.

Advice for Other Designers

If you’re in similar situation:

1. Document your productivity

  • Track what you ship
  • Show output is same or better remote
  • Data helps in negotiations

2. Build async skills

  • Learn to give feedback in Figma comments
  • Record Loom videos instead of meetings
  • Write design docs
  • These skills make you valuable to remote companies

3. Network with remote companies

  • They’re hiring
  • They value async communication
  • They pay well (save on office costs)

4. Know your worth

  • If you’re good, you have options
  • Don’t stay somewhere that doesn’t value flexibility
  • Life is too short for 2-hour daily commutes

To Leadership

If you’re reading this:

You’re losing your design talent.

Not because we don’t like the work.

Not because we don’t like the team.

Because the RTO policy doesn’t match how design work actually happens.

We need SOME in-person time (1-2 days/week).

We don’t need 3-4 days of mandated office presence.

The 5 designers who left? All doing great at remote companies.

The 7 of us remaining? Updating our portfolios.

You have maybe 6 months before you lose more of us.

Then you’ll spend $1M+ recruiting and training replacements who will also leave when they realize the policy sucks.

Or you could just listen to us now.

Your call.

Maya :artist_palette:

SF Tech Week observations + personal experience

Sources:

  • CXAI panel data
  • Personal interviews with remote-first design teams
  • Our company’s actual attrition numbers