No Headquarters, No Problem: Behind GitHub’s Remote Work Culture

When the world went remote in 2020, most companies scrambled to figure out how to make it work—logistics, tech, schedules. At GitHub, we were already distributed. But even with a head start, the sudden shift still demanded something deeper: clarity. Intention. Shared understanding.

And someone had to write it down.

At the time, I was Chief of Staff working closely with our marketing and communications leader. One of the most meaningful things I got to do was help shape and surface the story of how GitHub worked—especially when no one was in the same room. Not just internally, but externally too.

We weren’t looking to publish a glossy manifesto. We were documenting what was real: how our teams adapted, collaborated, led, and cared for each other through change.

From Conversations to Culture to Content

What became a remote work playbook started with hallway conversations (now Slack threads), shared Google Docs, and thoughtful questions from new Hubbers. It wasn’t about defining “the GitHub way.” It was about noticing what was already working and making it visible—so others could build on it.

As we listened across the org—from engineering and marketing to people ops and design—a series emerged. Not one voice, but many. My role was to help connect those perspectives, shape the message, and partner with contributors to turn ideas into shareable, thoughtful content.

Together, we built what became GitHub’s Remote Work series: a collection of essays on async collaboration, global teamwork, remote-first rituals, and the human experience behind distributed work. These weren’t polished pieces. They were lived experiences, written down in real time, with the hope that they might help others navigate uncertainty with a little more clarity and care.

What I Learned About Writing Remote Culture

Helping shape this series taught me a few things I’ve carried forward:

• Remote work doesn’t work without generosity and documentation. You have to leave trails for others—and assume they won’t see you build it in real time.
• Every team needs a few people who naturally spot patterns and gaps—and help translate them into something useful.
• Culture isn’t what you say. It’s what you operationalize.
• When people feel seen, they share more. And the more you surface what’s already working, the more resilient your culture becomes.

Remote work is no longer a novelty. But writing about it with empathy and specificity is still a differentiator. Especially now, when companies are redefining what hybrid, flexible, and distributed mean in practice—not just in policy.

Telling the Story Was the Work

We talk a lot about scaling systems and strategy. But during that time, what scaled most effectively at GitHub was understanding. The act of writing wasn’t just about comms—it was part of the culture-building itself.

We made the implicit explicit. We gave language to what people were feeling. And we did it in a way that helped others see themselves in the story—across time zones, departments, and disciplines.