GitHub Vet on 13 Years of Remote Work
A GitHub veteran shared lessons from thirteen years of successful remote work, attributing the company's productivity to a culture of high trust and deliberate investment in asynchronous collaboration. The key isn't just tools, but establishing clear communication protocols and defined decision rights, which is critical for scaling distributed teams.
Ben Balter's role as Director of Hubber Enablement at GitHub places him at the center of refining the company's renowned asynchronous communication patterns for its distributed workforce. His work involves not just promoting these practices but also driving employee engagement and productivity through deliberate strategies, including fostering AI fluency and orchestrating global offsites to complement remote collaboration. This focus on intentional remote work culture has been a cornerstone of GitHub's operations, with a majority of its employees, including senior leaders, working remotely for years. The philosophy underpinning GitHub's success with remote work is a deep-seated preference for asynchronous communication, a principle borrowed from the open-source community. This approach is designed to eliminate the "you had to be there" aspect of traditional corporate workflows, making information accessible and allowing for contributions across different time zones without the need for immediate responses. It prioritizes deep work by reducing interruptions, a practice Balter advocates for, suggesting that knowledge workers are most productive with large, uninterrupted blocks of time. For communication with senior leadership, the asynchronous model is adapted to be concise and digestible. Balter has mentioned using short-form written briefings, proposals, and updates that summarize information captured in more detailed, asynchronous forms like GitHub Issues. This approach ensures that executives receive the necessary context without having to delve into the granular details of every discussion, while still maintaining a transparent and documented decision-making process. Influencing cross-functional teams and stakeholders in this environment relies heavily on the ability to communicate with clarity and provide comprehensive context upfront. The emphasis is on written communication that allows for thoughtful, rather than immediate, responses. This creates a more inclusive environment where all stakeholders can contribute to decisions, regardless of their location or working hours. The goal is to make "writes" (the initial communication) rich with context so that "reads" (consumption of the information) are efficient and require minimal back-and-forth. While specific metrics on the direct impact of asynchronous communication on productivity are not publicly detailed, the longevity and success of GitHub's remote-first model serve as a testament to its efficacy. The company's culture is built on trust and the principle of judging work by its output rather than the hours spent online. For aspiring leaders in large tech organizations, the key takeaway from GitHub's experience is the importance of intentionally designing a communication structure that scales and supports a distributed team, rather than simply replicating in-office practices remotely.
