Leading Through RTO Pressure: A CTO's Perspective on Board Demands vs Team Needs

cto_michelle · February 19, 2026, 4:16am

I need to share something vulnerable: Three months ago, my board asked me to implement return-to-office for cost savings.

I said no. And here’s how that conversation went, because I think it’s valuable for other technical leaders facing similar pressure.

The Setup: Board Meeting, October 2025

Context: We’re a mid-stage SaaS company, remote-first since founding in 2020. 50 engineers, scaling to 120 over the next 18 months. Just closed Series B.

The question (from board member, former Fortune 500 COO):

“Michelle, I’m seeing a lot of companies returning to office. Have you considered bringing the team back? There are real cost savings in collaboration efficiency and cultural alignment. Plus, we’re seeing some excellent office space opportunities in Seattle.”

Translation: “Can we do RTO to reduce headcount through attrition and optimize our real estate strategy?”

My Internal Reaction

First thought: Here we go. The RTO pressure I’ve been dreading.

Second thought: I need to make this a data conversation, not a culture war.

Third thought: This is the defining moment of my leadership. How I respond will set the tone for my entire tenure.

The Data I Presented

I didn’t answer immediately. I said: “That’s an important strategic question. Let me come back next meeting with analysis.”

What I prepared over the next two weeks:

1. Current State Metrics

Engineering Productivity (DORA metrics):

Deployment frequency: 4.2 per week
Lead time for changes: 3.2 days
Mean time to recovery: 1.8 hours
Change failure rate: 8.3%
All metrics at or above industry top 25%

Team Health:

Employee Net Promoter Score: +42
Retention: 94% annually (industry average ~85%)
Time to productivity for new hires: 65 days

Business Outcomes:

Feature release velocity: 12 major features/quarter
Customer satisfaction: 8.7/10
Platform uptime: 99.95%

Key point: We’re performing exceptionally well in our current model.

2. Cost Analysis

Remote-first infrastructure:

Tools and platforms: 80K annually
Home office stipends: ,500 per engineer = 25K
Quarterly in-person gatherings: 80K
Security and compliance: 0K
Total: 45K annually

RTO scenario (modeled):

Office space (Seattle, 15,000 sq ft): 50K annually
Office operations: 00K
Reduced remote tooling: -0K
Reduced home stipends: -25K
Reduced gatherings: -00K
Total: 45K annually

Savings: 00K annually

BUT - Attrition costs:

Based on industry research (the BambooHR data that just came out validates this):

Expected attrition from RTO: 20-25% of team = 10-12 engineers
Cost to replace each: 00K-00K (recruiting, onboarding, productivity loss)
Total: M-.6M one-time cost
Timeline to baseline: 12-18 months

Net impact: RTO costs us M and delays our roadmap by 12+ months to “save” 00K annually.

3. Talent Market Analysis

Our recruiting advantage:

Survey of our last 20 hires:

85% cited remote flexibility as top-3 reason for joining
65% would not have considered us without remote option
Our close rate: 73% (vs. industry average 55%)

Competitive positioning:

Mapped competitors on remote flexibility:

Fully remote: 8 companies (our direct competitors)
Hybrid (2-3 days): 12 companies
Full RTO (4-5 days): 3 companies (all struggling to hire)

Market dynamics:

For senior engineers in Seattle market:

Demand: 2.3 jobs per qualified candidate
Remote roles: 68% of postings
Salary premium for office-required: 15-25% (we’d need to raise comp to compete)

Key point: RTO makes us less competitive in talent market.

4. Diversity Impact Analysis

Our current team demographics:

42% identify as women or non-binary (tech average: 26%)
38% from underrepresented racial/ethnic groups (tech average: 28%)
28% primary caregivers
15% have documented disabilities or chronic conditions

Surveyed team about RTO impact:

“If we required 4-5 days in office, how would this affect you?”

52% would likely or very likely leave
Among women: 64% would likely leave
Among caregivers: 71% would likely leave
Among people with disabilities: 83% would likely leave

RTO would devastate our diversity, which took years to build.

5. Strategic Roadmap Alignment

Our Series B pitch was built on:

Aggressive product roadmap (3 major features per quarter)
Scaling engineering from 50 to 120
Maintaining velocity while scaling
Competing on product innovation speed

RTO scenario impact:

Lose 20-25% of team to attrition
6-12 months to backfill
Reduced velocity during transition
Roadmap delays = delayed revenue
Competitive disadvantage

Key point: RTO undermines our Series B growth plan.

The Next Board Meeting

I presented all of this. Took 30 minutes. I walked through every slide, every number, every implication.

Then I made my recommendation:

“We should remain remote-first for the following strategic reasons:”

Performance: We’re executing exceptionally well in our current model
Talent: Remote flexibility is our competitive advantage in recruiting
Diversity: Critical to our culture and product quality
Cost: RTO has hidden costs that far exceed savings
Strategy: Aligns with our growth plan and Series B commitments

“However, I recommend we invest in intentional in-person time:”

Quarterly week-long gatherings for entire company
Dedicated budget for team offsites
Structured agendas for in-person time (architecture planning, team building)
Measure impact rigorously

“This gives us the benefits of co-location when it matters, without the costs of mandatory daily presence.”

The Board Response

Silence for about 30 seconds. (Longest 30 seconds of my career.)

Then the board member who raised it:

“This is exactly the kind of strategic thinking we need from our CTO. I’m convinced. Let’s stick with remote-first and invest in the quarterly gatherings.”

Board member from tech background:

“I’ve seen too many companies lose their best people to RTO mandates. This is the right call.”

CEO (afterward, privately):

“That was masterful. You turned what could have been a culture fight into a business decision.”

What I Learned

Key lessons for technical leaders facing board pressure:

1. Lead With Data, Not Emotions

Don’t say:
“Our team loves remote work and they’ll be upset!”

Do say:
“Our retention is 9% higher than industry average, and surveys show 52% would leave under RTO. Here’s the cost impact.”

2. Understand the Real Concern

The board member wasn’t really asking about collaboration. He was asking about:

Cost optimization
Cultural cohesion at scale
Risk management

Address the actual concerns with alternatives that don’t require RTO.

3. Bring Alternatives, Not Just Opposition

Don’t just say: “RTO is bad.”

Propose: “Here’s how we get the benefits you’re concerned about without the downsides of mandatory office.”

Quarterly gatherings addressed his cultural cohesion concerns without triggering attrition.

4. Know Your Leverage

I had several advantages:

Strong track record as CTO
Clear data showing team performance
Understanding of board member concerns
CEO support (I’d briefed him beforehand)

If you don’t have leverage, build it before the fight.

5. Be Willing to Lose… And Have a Plan

I went into that meeting knowing:

I might not win
I might need to implement something I disagree with
I might need to decide whether to stay

I had my own plan B. Several companies had approached me about CTO roles. I wasn’t going to implement a policy I knew would destroy my team without exhausting every option.

For Directors and Managers Without CTO Leverage

I realize I had positional power. If you’re an engineering director or manager facing RTO from above, here’s my advice:

1. Document Everything

Build the same data case
Share it with your leadership chain
At minimum, you have ammunition for when it backfires

2. Be Transparent With Your Team

Don’t pretend it’s your decision
Share what you’re fighting for
Let them make informed choices

3. Protect What You Can

Flexibility on days when possible
Remote Fridays for focus work
Exceptions for hardship cases

4. Support Departures

Strong recommendations
Network introductions
Don’t take it personally

5. Keep Advocating

Policies can change when costs become obvious
The data will eventually matter
Leadership changes, boards change

The Uncomfortable Truth

Not every leader will win this fight. Some boards are ideological about office presence. Some executives are threatened by remote work.

If you can’t win, you have a choice:

Implement the policy and minimize harm
Leave for an organization that aligns with your values

There’s no shame in either choice. But be honest with yourself about which you’re choosing and why.

Three Months Later: The Results

Since that board meeting:

Retention: 95.5% (improved)
Two quarterly gatherings completed (feedback: extremely positive)
Three senior hires who specifically cited remote-first policy
Productivity metrics: All improved slightly
Team morale: High

Cost of quarterly gatherings: 80K annually

Value preserved by not doing RTO: ~.5M in avoided attrition costs

ROI: 14x

The board member who raised it sent me a note last month: “You were right. Thanks for the pushback.”

My Question for This Community

How are other technical leaders handling RTO pressure from boards or executives?

Specifically:

What data/arguments worked or didn’t work?
How did you build leverage to push back?
For those who couldn’t win the fight, how did you minimize harm?
What happened after - did the policy change when costs became obvious?

I know I was fortunate to have leverage and a receptive board. I want to learn from others’ experiences, especially those navigating this from less powerful positions.

We’re all fighting versions of this battle. Let’s learn from each other.

Technical leadership means being willing to have hard conversations with data and conviction, even when it’s uncomfortable.

eng_director_luis · February 19, 2026, 4:18am

Michelle, I wish I had your leverage. Reading your board presentation made me both inspired and envious - because I tried a similar approach and lost.

My Corporate RTO Mandate Story

Fortune 500 financial services company. The mandate came from three levels above me. I’m a director managing 40+ engineers, reporting to a VP who reports to a CTO who reports to a C-suite that made the call.

I still built the data case, but my audience and outcome were different.

The Data I Presented (To My VP)

I used a similar framework to yours:

Current metrics:

Sprint velocity: 52 story points average
Defect rate: 3.2 bugs per release
On-time delivery: 87%
Retention: 92%

Expected RTO impact:

15-20% attrition based on team surveys
.5M-M replacement costs
6-9 month timeline to backfill
Productivity hit during transition

My VP’s response: “I agree with you completely. I made the same case to the CTO. We lost. Now we have to implement it.”

The Real Reason: Real Estate Politics

Here’s what I learned through back-channel conversations:

The decision wasn’t about engineering productivity. It was about:

Lease commitments: 15-year lease on campus signed in 2019, 0M sunk cost
Executive preferences: C-suite wants to see people in office (“energy,” “culture”)
Political pressure: Some divisions had already mandated RTO, created internal equity issues
Cost cutting: Hope for attrition (the quiet part nobody says officially)

No amount of engineering data was going to override real estate politics and executive preferences.

What I Did Anyway

Even though I lost the big fight, I fought for smaller wins:

1. Flexibility on which days

Corporate mandate: 4 days minimum
My push: Let teams choose which days based on collaboration needs
Won: Teams have autonomy on Mon/Fri, required Tues-Thurs

2. Exceptions process

Created hardship exception request process
Documented criteria (caregiving, medical, relocation hardship)
Partial win: 2 exceptions approved, 3 denied (bureaucracy)

3. Intentional office time

Implemented “collaboration hours” concept
Core collaboration 10am-3pm
Flexibility to arrive early or leave late for commute optimization
Won: Some schedule flexibility

4. Relentless measurement

Tracked every metric before/during/after
Documented the impact
Shared with team (transparency)
Result: Data showing 8% productivity decline, 15% attrition

The Results After 6 Months

Metrics:

Sprint velocity: Down 8% (48 points)
Defect rate: Up 19% (3.8 bugs/release)
On-time delivery: Down to 81%
Retention: Down to 85% (lost 3 senior engineers)

Morale:

Team engagement: 8.1 → 6.9
Recruiting close rate: 68% → 52%
Interview pipeline quality: Noticeably worse

I presented this to my VP. His response: “Keep tracking. I’m building the case to revisit the policy.”

Translation: The political will doesn’t exist yet to admit the policy was wrong.

What I Learned About Fighting From the Middle

Michelle, your board presentation worked because:

You have direct access to decision-makers
You had data BEFORE the policy was implemented
Your board was receptive to business logic
You had CEO support
You had leverage (track record, alternatives)

My situation:

Three levels removed from decision-makers
Policy already decided, I’m just implementing
Political considerations override business logic
My VP agrees but is also powerless
Limited leverage (good director, but replaceable)

The lesson: Position and leverage matter as much as data.

For Other Middle Managers

If you’re like me - trying to fight RTO from director or manager level:

1. Build the data case anyway

You need it for when the pendulum swings
It helps your team know you tried
It protects you when things go wrong (“I told them this would happen”)

2. Fight for micro-optimizations

You can’t change the policy, but you can reduce harm
Flexibility on days, times, exceptions
Make the required office time as valuable as possible

3. Be radically transparent

Tell your team: “This isn’t my decision, here’s what I fought for, here’s what I lost”
Don’t pretend you support it if you don’t
Let them make informed choices

4. Document everything

Metrics, feedback, attrition reasons, replacement costs
When the policy fails, you have the receipts
Helps build case for eventual policy reversal

5. Support departures without resentment

People leave because of the policy, not because of you
Strong recommendations, network introductions
Maintain relationships (they might come back when policy changes)

The Diversity Impact

Michelle, your diversity numbers are impressive (42% women, 38% URM). We were at 28% women, 31% URM.

After RTO? 22% women, 25% URM.

We lost:

Both working mothers on my team
The engineer with chronic illness requiring specific medical access
One engineer who’d relocated to care for aging parents

Who stayed:

Younger engineers without family commitments (mostly)
Engineers who already lived near office
Engineers who couldn’t easily find other roles

We’re now less diverse AND less senior. The policy achieved the opposite of our stated DEI goals.

The Question: When Does the Cost Become Obvious?

Michelle, you asked when costs become obvious enough to change policies.

My pessimistic answer: When it affects executive-visible metrics like revenue or customer satisfaction.

Engineering productivity decline? Not visible enough.
Attrition increase? Seen as “natural optimization.”
Recruiting challenges? “Market is tough everywhere.”
Lost diversity? Not measured quarter-to-quarter.

But when:

Product delays affect revenue targets
Customer escalations increase
Major incidents happen due to knowledge loss
Competitive losses are tied to engineering execution

Then suddenly the policy gets “reevaluated.”

We’re not there yet. But I’m watching and waiting.

My Advice to Other Leaders

If you have Michelle’s leverage: Use it. Push back with data. Make them say no explicitly.

If you don’t have leverage: Fight for what you can control. Document everything. Support your team. Keep advocating.

If you’re getting RTO pressure: Build the case Michelle built, even if you’re not presenting to the board. Your VP or CTO might be.

And most importantly: Be honest with yourself about whether you can live with implementing a policy you disagree with.

I chose to stay and fight from within, minimizing harm where I can. Some of my peers chose to leave. Both are valid.

Michelle, thank you for sharing your success story. It gives me hope that somewhere, data and business logic still win. And it gives me a template for when our pendulum eventually swings back.

Sometimes the best you can do is document the failure, minimize the harm, and be ready for when leadership is finally ready to listen.

vp_eng_keisha · February 19, 2026, 4:18am

Michelle, this is exactly the kind of strategic leadership our industry needs. I had a similar board conversation, and I want to share what worked from the VP Engineering level at a high-growth startup.

My Context: EdTech Startup, Series A, Scaling Fast

Situation:

25 engineers, scaling to 80 over 18 months
Board member (from traditional education background) uncomfortable with remote-first
Post-Series A, pressure to “professionalize” operations

The Question:
“Keisha, as we scale, don’t you think having everyone in an office would help with culture and mentorship?”

Subtext: “Remote work is for small companies. Real companies have offices.”

My Response Strategy (Similar to Michelle’s)

I didn’t fight the culture war. I made it about talent economics.

Data I Presented:

1. Talent Market Reality

I mapped our last 15 engineering hires:

11 were located outside our Austin metro area
8 specifically cited remote flexibility as reason for joining
3 had rejected FAANG offers for our remote-first culture
Our talent pool: Global vs. 50-mile radius of Austin office

Key point: “If we require office presence, we eliminate 73% of our recent hires from consideration. We’re competing with companies offering 00K+ for senior engineers. Remote flexibility is how we win.”

2. Compensation Arbitrage

I showed the math on geographic salary distribution:

Austin-based engineer at market rate: 80K
Same engineer in lower COL (remote): 40K
For 25 engineers, geographic diversity saves ~00K annually
Can reinvest in better tooling, team gatherings, retention bonuses

We’re saving money while accessing better talent.

3. Diversity as Product Strength

Our product serves K-12 education - incredibly diverse user base.

Our team diversity (remote-first):

48% women in engineering (EdTech average: ~30%)
40% from underrepresented backgrounds
Geographic diversity: 12 states, 3 countries
Age diversity: 23 to 58 years old

Surveyed team: “Would you have joined if we required office presence?”

60% said no
Among women: 72% said no
Among caregivers: 81% said no

Key point: “Our diverse team builds better products for our diverse users. Office requirement would have prevented us from building this team.”

4. The Mentorship Myth

Board member was specifically worried about junior engineer mentorship remotely.

I showed our data:

Junior engineer ramp time: 2.5 months (industry average: 3-4 months)
Mentorship satisfaction scores: 8.4/10
Promotion rate for junior → mid: 18 months average

How we do it:

Structured onboarding with assigned mentors
Daily 1:1s for first month (15 min standup with mentor)
Pair programming sessions (scheduled, intentional)
Documentation culture (everything written down)
Monthly career development 1:1s

Remote mentorship works when it’s intentional. Office mentorship fails when it’s assumed to happen osmotically.

5. Competitive Positioning

I showed our recent recruiting losses:

Lost to Google: 1 (compensation)
Lost to Meta: 1 (brand)
Lost to startups requiring office: 0

And our wins:

Beat Stripe (also remote-first, but we offered equity upside)
Beat local Austin companies (they required office)
Beat traditional EdTech (remote + mission)

Remote flexibility is our recruiting superpower.

The Board Response

Board member: “This is compelling data. But how do we maintain culture as we scale?”

My answer: “By being intentional about culture-building, not assuming proximity creates culture.”

What we implemented:

Monthly all-hands (virtual, but structured)
Quarterly in-person gatherings (entire company, 3 days)
Team off-sites (twice yearly per team)
Async culture documentation (handbook, values, practices)
Virtual social events (optional, but fun)

Cost: 20K annually for gatherings and offsites

Alternative: Austin office for 80 engineers = .2M annually + eliminate 60% of our talent pool

Board member: “That makes sense. Keep doing what’s working.”

What I Learned About Framing

Michelle, you’re absolutely right that this needs to be a business conversation, not a culture war.

Don’t say:

“Our team will be upset!” (emotional)
“Remote work is the future!” (ideological)
“Other companies are doing it!” (defensive)

Do say:

“Here’s our talent market data” (factual)
“Here’s the cost comparison” (financial)
“Here’s our competitive positioning” (strategic)
“Here’s how we’re measuring success” (accountable)

Frame it as: “How do we access the best talent most cost-effectively while maintaining high performance?”

Not: “Should we be remote or in office?”

The Advantage of EdTech

I had one advantage: Our industry is education, where remote/hybrid learning is literally our product.

I used this:

“We sell remote learning solutions to schools. Our value proposition is that learning happens effectively when it’s flexible and accessible. If we don’t believe that for our own team, how do we sell it to customers?”

That resonated. Hard to argue we should require office presence while selling remote learning software.

Where I Agree with Luis

Luis mentioned fighting from the middle is different than fighting from VP/CTO level. Absolutely true.

I have advantages:

Direct board access
Decision-making authority
CEO partnership (we’re aligned on this)
Strong track record

If I were a director without this leverage, I’d:

Build the same data case
Present to my VP
Offer to support their board presentation
Document everything
Be transparent with my team

Position matters. But data matters too. Even if you don’t win immediately, you’re building the case for when leadership is ready to listen.

The 6-Month Results

Since we explicitly reaffirmed remote-first:

Talent metrics:

Hired 12 more engineers (now at 37 total)
Close rate improved: 73% → 78%
Geographic diversity: Now 15 states, 4 countries
Women in engineering: 48% → 51%

Performance metrics:

Deployment frequency: Improved 20%
Product velocity: On track for roadmap
Customer satisfaction: 8.9/10
Engineering eNPS: +52

Cost:

Spent 5K on two quarterly gatherings
Saved ~00K vs. office space + commute costs

Board member who raised concern sent note after last gathering: “I get it now. This works.”

My Answer to Michelle’s Question

What arguments worked:

Talent market economics (most compelling)
Cost comparison with full accounting (hard to argue)
Diversity and inclusion data (especially for our product)
Competitive positioning (strategic framing)
Measurement and accountability (“trust but verify”)

What didn’t work in other contexts:

Appealing to what team wants (seen as coddling)
Industry trends (“everyone else is doing it” cuts both ways)
Productivity studies (too mixed to be decisive)

How I built leverage:

Delivered on Series A commitments
Built strong relationship with CEO
Demonstrated measurement and accountability
Hired exceptionally well (remote-first gave us access)

The key: Make it hard for them to say no by making the business case overwhelming.

For Other VPs Facing This

If you’re at VP level:

Use your access - You can have these conversations directly
Bring CEO along - Align before board meeting
Build comprehensive case - Data across talent, cost, performance, strategy
Propose alternatives - Don’t just say no, offer better solutions
Measure relentlessly - Prove it’s working with ongoing data

If your board still mandates RTO after strong data case:

Consider whether you can implement something you fundamentally disagree with
Some battles are worth leaving over
But also: some leaders stay to minimize harm

There’s no one right answer. Know your values and constraints.

Michelle, thank you for sharing your successful pushback. It’s encouraging to see technical leaders using data and strategic thinking to protect their teams and preserve competitive advantages.

The companies that figure this out will win the talent wars. The ones that don’t will keep wondering why they can’t hire and retain great engineers.

VP-level leadership means using your seat at the table to make evidence-based cases for decisions that protect both business outcomes and team wellbeing.

product_david · February 19, 2026, 4:21am

Michelle and Keisha - as a product person who partners closely with engineering leadership, I want to share how I’ve supported my CTO in making the remote-first case to our board.

The Product Lens on Remote Work

My role: VP Product at Series B fintech. I work directly with our CTO on roadmap planning and team scaling.

The dynamic: When our CTO faced RTO questions, I offered to co-present the product impact analysis. Here’s what I brought.

Customer Impact of Team Stability

I mapped our product development to specific engineers:

Payment processing core: 2 senior engineers (combined 9 years institutional knowledge)
API platform: 1 staff engineer (built from scratch)
Security & compliance: 2 engineers (deep regulatory knowledge)
Customer-facing features: 3 engineers (understand user pain points deeply)

Then I modeled attrition scenario:

If we lose 20% of team (8 engineers) to RTO:

65% probability we lose at least one critical knowledge holder
35% probability we lose two or more

Product roadmap impact:

Q1: Already committed features slip 4-6 weeks
Q2: New feature development paused while backfilling
Q3-Q4: Reduced velocity while onboarding

Customer commitments at risk:

3 enterprise deals with specific feature requirements
2 pilots dependent on Q1 launches
Renewal risk for customers expecting continuous innovation

Revenue impact: -4M ARR at risk from delays and churn

I told the board: “RTO doesn’t just affect engineering. It affects our ability to deliver on revenue commitments.”

Competitive Product Velocity

I also benchmarked our velocity against competitors:

Our product release cadence (remote-first):

Major features: 3.2 per quarter
Minor updates: Weekly
Bug fix cycle time: 3.5 days average

Competitor A (hybrid, 3 days office):

Major features: 2.1 per quarter
Updates: Bi-weekly
Bug fix cycle: 5+ days

Competitor B (full RTO recently):

Major features: 1.8 per quarter (down from 2.8 pre-RTO)
Updates: Monthly
Known to be struggling with turnover

Our competitive advantage is partially due to team stability and flexibility.

The Voice of Customer Research

I surveyed 20 of our enterprise customers about vendor selection criteria:

What matters most in vendor selection:

Product roadmap and innovation velocity (82%)
Implementation speed and support quality (76%)
Feature depth and customization (71%)
Price (68%)

What determines renewal:

Consistent product improvement (89%)
Responsive support team (84%)
Minimal bugs and incidents (78%)

All three depend on team stability and institutional knowledge.

I told the board: “Customers choose us because we ship fast and support well. Both require team continuity.”

How Product Leaders Can Support Engineering

Michelle and Keisha showed the engineering case. Here’s how product leaders can amplify:

1. Quantify customer impact

Map product areas to key people
Model delay scenarios
Calculate revenue risk

2. Bring competitive intelligence

What are competitors doing?
How is it affecting their velocity?
Where’s our advantage?

3. Voice of customer

Why do customers choose us?
What do they value?
How does team stability affect satisfaction?

4. Business model alignment

For SaaS: Innovation speed = retention
For marketplace: Quality + speed = network effects
For enterprise: Reliability = expansion revenue

5. Support your CTO’s data case

Co-present when possible
Bring customer voice to engineering discussions
Make it clear: This isn’t just an eng problem, it’s a business problem

What Worked in Our Board Meeting

The combination was powerful:

CTO brought: Engineering productivity, talent costs, retention data
I brought: Customer impact, revenue risk, competitive positioning

Together we made the case:
“Remote-first enables our product strategy. RTO undermines our competitive advantage and revenue commitments.”

Board response: “We invested in this company because of product-market fit and execution speed. Don’t break what’s working.”

My Advice to Product Leaders

If your CTO is fighting RTO:

Offer to support with product data - Revenue impact resonates with boards
Map dependencies - Show which customers/features depend on which people
Model delay scenarios - Make the roadmap risk concrete
Bring competitive intel - Frame as strategic advantage
Stand with engineering - Cross-functional alignment matters

If you can’t win the fight:

Help prioritize which people to retain (customer impact lens)
Adjust roadmap expectations early
Manage customer expectations proactively
Document the product cost for when policy gets reconsidered

The Partnership Model

The best CTO-VP Product relationships I’ve seen:

Shared accountability for delivery
Mutual support in difficult conversations
Complementary perspectives to leadership
Unified front to board/CEO

When engineering says “this hurts team,” product says “this hurts customers,” together it’s a complete business case.

Product strategy and engineering strategy are inseparable. RTO affects both, so both leaders should weigh in.

alex_dev · February 19, 2026, 4:21am

Michelle, reading your board presentation and the responses from Luis, Keisha, and David - I want to add the IC perspective on how leaders fighting for us affects our decisions.

What ICs See and Don’t See

What we see:

The policy announcement
Whether we can comply
Our options in the job market

What we often don’t see:

Leaders fighting for us behind closed doors
Data cases being built
Board pushback attempts

Why this matters: When leaders like Michelle, Keisha, and Luis share their efforts, it changes how we process the policy.

The Difference Transparent Leadership Makes

Scenario A: Policy announced, no context

What ICs think:

“Leadership doesn’t care about us”
“This is a done deal, no one fought it”
“Time to update LinkedIn”
“Don’t trust anything they say going forward”

Scenario B: Policy announced with transparency

Leader says:
“I fought against this policy. Here’s the data I presented. I lost this battle, but I want you to know I tried. Here’s what I can control, here’s what I can’t. I support whatever decision you make.”

What ICs think:

“My manager has my back even when they lose”
“They’re being honest about constraints”
“I can trust them about other things”
“Maybe I stay and see if the policy changes”

Transparency doesn’t change the policy, but it preserves trust.

What Would Make Me Stay Despite RTO

Michelle, Luis, Keisha - your approaches make me think about what would keep me at a company that mandated RTO against my preference.

I would seriously consider staying if:

My manager fought for me and was transparent about it
- Shows they care, even if they lost
- Preserves trust for future decisions
There’s flexibility within the policy
- Choose my days
- Core hours vs. full days
- Exceptions for life circumstances
Outcome-based evaluation remains
- Still measured on delivery, not presence
- No badge-swipe metrics
- Autonomy within constraints
Compensation adjustment
- Recognize commute cost and time
- Market adjustment for loss of flexibility
- Or other benefits (stock, bonus, PTO)
Clear feedback mechanism
- Leadership measuring impact
- Open to reversing if data shows problems
- Team has voice in evaluation
Support if I choose to leave
- Strong recommendations
- Network introductions
- No resentment

I would definitely leave if:

Policy feels manipulative (hoping I quit)
No flexibility or humanity
Manager pretends to support it
Micromanagement increases
Outcome focus shifts to presence focus

How ICs Can Support Leaders Who Fight for Us

David mentioned how product can support engineering. Here’s how ICs can support leaders:

1. Provide data when asked

Commute impact surveys
Productivity self-assessments
Honest feedback on policy effects

2. Document our work outcomes

Make it easy to show our value
Track our contributions
Help build the performance case

3. Be professional even when we disagree

Policy might not be manager’s choice
Separate person from policy
Make their job of advocating easier

4. Communicate our decisions clearly

If we’re leaving, give appropriate notice
If we’re staying, commit to making it work
If we’re uncertain, be honest

5. Recognize their constraints

Not every fight can be won
Position and leverage vary
Appreciate the effort even if unsuccessful

The Question for Michelle and Keisha

You both successfully pushed back at CTO/VP level. What should ICs know about:

1. How we can make your advocacy easier?

What data helps?
How should we communicate concerns?
When should we escalate vs. trust you’re handling it?

2. What’s realistic to expect?

Can all battles be won with data?
When is policy truly unchangeable?
How do we know when to stay vs. leave?

3. How do we support middle managers like Luis?

They don’t have your leverage
But they’re fighting for us
What helps them build their case upward?

Gratitude for Transparent Leadership

Reading these threads over the past few days, I’m struck by how rare this kind of transparent leadership discussion is.

Most companies handle RTO as:

Policy announced
No context given
“Collaboration and culture” justification
No data shared
No acknowledgment of costs

What you all are doing:

Sharing the behind-the-scenes fights
Being honest about wins and losses
Showing the data and reasoning
Acknowledging the human cost

This is what good leadership looks like. Win or lose the specific battle, you’re preserving trust and showing respect.

As an IC evaluating my options, the difference between a company with leaders like you vs. leaders who just implement policies without transparency… that’s the difference between “I’ll consider staying” and “I’m definitely leaving.”

Thank you for fighting for us, even when you lose. And thank you for being transparent about the fight.

ICs notice when leaders fight for us, even behind closed doors. That trust matters when tough decisions come.