Remote Work as a Culture, Not a Contingency

GitHub has been a remote-first engineering organization since long before the pandemic forced the rest of the industry to catch up. More than 80% of its engineers were already working remotely pre-COVID. The question now, according to VP of Engineering Dana Lawson and VP of Community and Ecosystem Engineering Sha Ma, is maintaining those principles when everyone—not just the distributed veterans—is dealing with the stresses of a global health crisis.

Communication: Write It Down, Say It Again

With personal disruptions piling up for employees, communicating with empathy is the baseline. But beyond that, both leaders emphasize the mechanics of communication. Lawson stresses that even for a company with years of remote experience, current conditions require being highly intentional about how information flows. Information should be written down and repeated across multiple channels—different groups, different audiences, and even to yourself. Predictability matters.

Summary posts after key decisions are a standard practice at GitHub. The company leans on internal repositories for announcements and updates, which helps keep distributed teams aligned without forcing yet another synchronous meeting. Restating a decision in writing can save time that would otherwise go toward scheduling a new call.

Boundaries Are Part of the Job

Working from home requires building artificial structure into your day. Lawson's advice is blunt: develop constraints. It is acceptable to turn off Slack, to set an out-of-office message, and to acknowledge that being home doesn't mean being always available.

Ma puts visible schedule blocks to work out of necessity. She regularly protects time for lunch and 15-minute breaks to keep her two kids at home fed and on schedule. This isn't a fringe habit—it's a cultural signal. For leaders especially, making these blocks public shows the team that it's okay to take care of family and personal health during working hours.

Serving Teams Across Time Zones

For teams spanning many time zones, Lawson suggests borrowing a practice from nurses: shift-change documentation. The outgoing person leaves a clear handoff so the incoming person can pick up the context and continue without waiting for a live debrief. This kind of asynchronous workflow allows team members to work in concert even when their schedules don't overlap.

GitHub also adapts its large-format meetings to regional constraints. All Hands recordings are available globally within 24 hours, accompanied by written highlights. Employee resource groups run roundtable discussions twice—once early in the morning and once in the afternoon—to accommodate people in different zones.

Onboarding New Remote Employees

There's no substitute for a human contact when you're starting out. Ma points to a buddy system as the key practice for new hires: each person is paired with an onboarding buddy who absorbs the "obvious" questions—where to find the org chart, which Slack channel to join—so the new hire can learn team-specific context without feeling lost.

Video presence is another simple but powerful norm. In small group meetings of five or six people, cameras on makes a meaningful difference. For those uncomfortable exposing their home environment, Lawson acknowledges that virtual backgrounds are a fine compromise. The point is to be as open as possible without sacrificing well-being. The goal isn't forced perfection—it's checking in on each other.

The Value of a Global Team

For both leaders, the core benefit of remote work is the diversity of perspective it brings to a single product. Ma recalls an early meeting at GitHub where a single video call carried accents from all over the world—a concrete reminder that the company's reach is genuinely global. Lawson echoes that sentiment: her typical day connects her with colleagues from Africa to Scotland to Colorado.

Lawson draws a direct line from that experience to open source philosophy: people who have never met can work asynchronously and still move human progress forward. The current shift to remote work, in her view, isn't a temporary inconvenience—it's the validation of a model GitHub has been building for years.