GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsOn this page, we're detailing considerations for in-person interactions within a remote company. Humans are social creatures, and research has shown that there is value in in-person interactions. While there are tremendous advantages to operating a 100% remote company, leaders should consider being intentional about planning in-person elements, even if they're optional for team members.
GitLab Head of Remote Darren Murph shares on GitLab's intentional approach to in-person interactions (and business travel's purpose in a remote company) in a TripActions blog and podcast.
GitLab Commit Brooklyn 2019 recap reel.
Organizing customer and/or community meetups around the globe is a great way to ensure team members meet each other in person, while also providing business and branding benefits. Meetups serve as incubators for what could come next, and provide a safe space for feedback to flow. Not only do they allow customers to put a face to a company they are engaging with, but it creates opportunity for team members to travel and meet each other while supporting a company initiative.
In an all-remote setting, meetups have psychological benefits as well. While colocated companies may struggle to garner deep support from team members who must plan, execute, and attend a meetup, all-remote team members tend to view meetups as special opportunities to do something they aren't able to do on a daily basis: interact with colleagues in the same physical space.
Perception plays a major role in quality of execution. In colocated settings, team members are required to commute and spend much of their waking hours with colleagues in a shared space. This could make the notion of spending added time, likely outside of their normal working hours, seem more like a burden and less like a bonding opportunity.
Conversely, team members in an all-remote setting have precious few opportunities to see one another face-to-face. In turn, may be easier to rally support for meetups given the underlying perk of in-person bonding and networking.
Learn more about how GitLab organizes community events in the GitLab Meetup Guide.
GitLab CEO Sid Sijbrandij and General Catalyst Managing Director Kyle Doherty kick off Making Remote Work. Photo by Slava Blazer Photography
It is common for colocated companies to send a lean contingent to work-related conferences, which is rational given the relative high costs involved. In colocated settings, work conferences add marginal bonding benefit given that attendees already spend a significant amount of time together in a shared physical office.
In remote-first and all-remote settings, the value proposition is drastically different. Conferences serve as an opportunity to send a team of colleagues to not only execute on business objectives, but also to spend time bonding with one another as humans.
Colleagues together at GitLab Commit London 2019
Consider supporting team members who wish to arrive early or stay late in order to spend time getting to know colleagues on a face-to-face basis, but be mindful not to judge or penalize those who opt out. Family commitments and personal preference should be honored. Choosing not to arrive early or stay late at a conference for bonding should not be viewed as indifference towards the company.
As an example, GitLab Commit — a series of user conferences — doubles as an excellent mechanism to bring colleagues together for a purpose, while also serving the greater community.
GitLab Contribute 2019 recap reel.
While virtual events and ongoing touch points through informal communication mechanisms are vital for a team's growth, all-remote companies should consider a regularly scheduled gathering or summit for the entire company.
These gatherings should be optional, though encouraged, and should focus primarily on bonding. Hosting a summit only to inundate colleagues with presentations is not recommended. At GitLab Contribute, for example, numerous excursions are planned throughout the week in order to bring people together in the same physical space for non-work activities.
With no central office, these are remarkably flexible. Your company may choose a different location for each occurrence, or perhaps support a voting system where colleagues can offer up suggestions for ideal locations.
In all-remote settings, these known touch points are critical for morale. Team members can plan their year around these seminal moments, with a period of in-person experiences giving them fresh perspective when engaging in the future through Zoom or phone.
Celebrations at GitLab Commit London 2019
As an all-remote team scales, you may find that certain regions of the world are home to multiple team members. At GitLab, we encourage colleagues to join Location Channels in Slack, which allow them to easily connect with others who live relatively nearby.
This creates an easy path for gathering in a central location to bond. Common reasons for scheduling a get-together are holidays and milestone celebrations, though active local communities may consider coming together on a regular basis (monthly, quarterly, etc.) simply to maintain a physical connection.
Being a 100% remote company creates unique opportunities for these gatherings. A team may consider rotating who picks the venue or locale to meet at, creating a diverse calendar of events. Those who are comfortable doing so may even consider inviting local team members to their home or neighborhood.
GitLab recognizes that not everyone can or will prefer to work from their home. In turn, fees associated with coworking spaces are reimbursable. Through location channels, team members who live close to one another can easily arrange dedicated coworking days and shared events, covering everything from dining together to supporting a local charity as a unit.
In the GitLab Unfiltered video above, Darren (GitLab) and Elisa (The Cowork Experience) discuss the merits of a company subsidizing and encouraging travel to visit other colleagues.
Savings on real estate — and the litany of associated costs with operating one or more offices — is a key financial reason for a company to organize itself as completely remote. Consider returning some of those savings to employees by subsidizing travel costs associated with visiting colleagues around the globe.
GitLab's Visiting Grant incentive is one such example. While some colleagues may prefer to stay put, there is value in transparently encouraging colleagues to spend time with one another in a physical space. When a colleague travels to visit someone else, they are immersed in a new place and new culture, which leads to greater empathy and understanding.
This also reinforces a company's ability to create a more geographically diverse and inclusive work environment.
The Cowork Experience assists remote companies with planning excursions that bring colleagues together in the same physical space.
As an all-remote company scales, it becomes more challenging to get the entire company in one place during the same window of time. As the once-a-year company annual becomes a standard offering (and less a differentiator) for remote companies, there is opportunity to host smaller, more frequent excursions and retreats.
The Cowork Experience, for instance, develops bespoke programs with more intimate engagements at the team or regional level to foster deeper trust amongst colleagues. These usually include team-building activities as well as non-work excursions. They present an opportunity to bring colleagues together in a unique, refreshing locale, catalyzing things like planning while enabling personal bonds to be built.
Leadership should be mindful of personal strain placed on team members when they are asked to leave their home for extended periods of time, with covered childcare or similar assistance ensuring that undue burdens are not placed on caregivers.
Anyone can test their knowledge on considerations for in-person interactions in a remote company by completing the knowledge assessment. Earn at least an 80% or higher on the assessment to receive a passing score. Once the quiz has been passed, you will receive an email acknowledging the completion from GitLab. We are in the process of designing a GitLab Remote Certification and completion of the assessment will be one requirement in obtaining the certification. If you have questions, please reach out to our Learning & Development team at learning@gitlab.com
.
Return to the main all-remote page.