Does remote work hurt culture?

It changes culture. Whether it hurts depends on whether the company invests in the systems that make distributed work function. Companies that treat remote as 'in-office minus the office' produce weak cultures; companies that redesign their operating model produce different but often stronger ones.

Should we pay remote employees less?

This is a philosophical decision, not a technical one. Location-adjusted bands (paying SF rates in SF, lower in low-cost areas) are common but signal 'you're worth less because you live somewhere cheaper.' One-band-nationally is simpler and signals 'we pay for the work, not the zip code' — but is expensive. Both models exist at scale.

How often should distributed teams meet in person?

Twice a year for full-company offsites is a common baseline. Smaller team offsites quarterly. The purpose is trust-building and strategy, not tactical work; running an offsite as a series of long meetings is a wasted trip.

Remote Work Policy: In-Office, Hybrid, or Fully Distributed

A remote work policy defines where and when your team is expected to work — in-office, hybrid, or fully distributed.

Remote Work Policy: Pick a Model and Actually Commit to It

A remote work policy is the explicit statement of where and when employees are expected to work — from 'in-office five days' to 'fully distributed across timezones.' The policy itself is easy to write; the hard part is aligning every downstream system (hiring geography, meeting culture, documentation standards, compensation, career progression) with the choice. Companies that pick a model and commit produce clearer employee experiences than companies that pick a model and quietly undermine it.

The four coherent models

(1) Fully in-office — everyone in the same building most days, decisions made in hallways and whiteboard sessions. (2) Hub-and-spoke — a primary office with satellite hubs; expectation of in-person for hub employees, remote for others. (3) Hybrid with anchor days — everyone remote most days, 1-3 mandatory in-office days per week. (4) Fully distributed — no primary office, async-first, occasional in-person offsites. Each model is internally coherent when the systems below match; problems come from claiming one model while operating like another.

The systems that must match

Hiring geography — fully in-office means hiring in one metro; distributed means hiring anywhere. Meeting culture — in-office defaults to synchronous meetings; distributed requires async by default with meetings as escalation. Documentation — distributed teams live and die by written communication; in-office teams can survive with less writing. Compensation bands — distributed teams face location-adjustment vs. one-band decisions. Career progression — in-office bias in promotions is real; distributed teams need deliberate mechanisms to counteract proximity bias.

The hybrid trap

The most common failure mode: 'hybrid' with no specific requirements. Some people come in daily, some come in weekly, meetings are half-in-room-half-on-video (worst possible meeting format), and decisions get made in hallways that remote people never hear. Hybrid works when anchor days are mandatory and consistent (Tuesday-Thursday for everyone), and when all meetings default to fully remote even when most participants are in the room. Otherwise it's the worst of both models.

Async-first is a discipline, not a slogan

Async-first means the default communication is written and expected to be read on the reader's schedule; meetings are the escalation, not the norm. This requires investment: strong writing culture, canonical documentation, decision logs, and a norm that 'I'll bring it up in the meeting' is not an acceptable answer to a written question. Companies that say 'async-first' but keep a 30-meeting weekly calendar are actually meeting-first with async decoration.

Reversing the policy

Return-to-office mandates after periods of remote work are among the highest-conflict decisions a company can make. Employees hired under a remote policy reasonably view a mandate as a unilateral compensation cut (commute time, relocation cost). If a return is necessary, be explicit about the reasoning, offer generous transition time (6+ months), and expect meaningful attrition. The alternative — quietly pressuring people back — poisons trust without changing office attendance much.

Frequently asked questions

Does remote work hurt culture?: It changes culture. Whether it hurts depends on whether the company invests in the systems that make distributed work function. Companies that treat remote as 'in-office minus the office' produce weak cultures; companies that redesign their operating model produce different but often stronger ones.
Should we pay remote employees less?: This is a philosophical decision, not a technical one. Location-adjusted bands (paying SF rates in SF, lower in low-cost areas) are common but signal 'you're worth less because you live somewhere cheaper.' One-band-nationally is simpler and signals 'we pay for the work, not the zip code' — but is expensive. Both models exist at scale.
How often should distributed teams meet in person?: Twice a year for full-company offsites is a common baseline. Smaller team offsites quarterly. The purpose is trust-building and strategy, not tactical work; running an offsite as a series of long meetings is a wasted trip.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database