On this page, we're detailing considerations for transitioning a colocated or hybrid-remote company to 100% remote, as well as tips for introducing remote team members to a historically in-office organization.
We maintain a separate guide with blueprints and examples on transitioning from a primarily colocated environment to a hybrid-remote environment.
For more, visit GitLab's guide to understanding the phases of remote adaptation.
In the GitLab Unfiltered video above, Darren (GitLab) and Janice (Groupdesk) discuss the potential of transitioning a hybrid-remote company to all-remote.
In general, a company seeking to transition to fully remote should actively avoid or remove common hybrid-remote pitfalls by whatever means necessary. Moreover, it's important for leaders to put themselves in the shoes of a prospective job seeker who will ask very specific questions to determine how prepared a company is to thrive in a 100% remote setting.
Much of it boils down to changing whatever elements you need in order to become the remote company that you would want to work for. This requires old habits to be left behind, and intentional effort to be made on areas such as documentation, informal communication, and working well asynchronously.
If existing leadership is not equipped to understand these nuances or lead such a transformation, consider recruiting a Head of Remote with deep experience working in remote settings and leading globally distributed teams. Andreas Klinger aptly articulates this role as being "at the intersection of optimizing internal tooling, processes, transparency, collaboration, efficiency, inclusivity, onboarding, hiring, employer-branding, culture and communication overall."
The specific answer to this question will vary from company to company, and will be impacted by the following attributes.
The quickest way to send the clearest signal that remote is the future is to start at the top of the organizational chart. Julien Dollen, Director of Engineering at Oracle, explains below.
If you want remote to work, start by cutting off the head. When the chief is remote, all of a sudden everybody is remote and everybody starts writing down everything. What used to be ephemeral and on a whiteboard became written down and stored. — Julien Dollon, Director of Engineering at Oracle
Cédric Fabianski, co-founder and CTO at Bearer, reiterated that he saw this work well at FreeAgent, too. He notes that by moving the executive suite out of the office, it removes any doubt about leadership's intentions to complete the transition.
In the GitLab Unfiltered video above, Darren (GitLab) and Anna-Karin (Because Mondays) discuss a number of challenges and solutions related to remote work, transitioning a company to remote, working asynchronously, and defaulting to documentation.
Companies considering a transition to fully remote should ask themselves if they could function if every team member chose to work from their home tomorrow. To get an idea of what needs to be in place from a tools and technology standpoint, consider the following questions in light of the aforesaid scenario.
Companies that rely on in-office meetings will likely need to embrace a new paradigm, leveraging Zoom and Google Calendar. Too, they should resist the urge to default to meetings, relying instead on asynchronous communication wherever possible.
Enabling access to systems and files across a fully remote company can be very different, and may require a new approach to security.
If you do not have a living, evolving company handbook, start one now. Embracing the notion of "if it's not documented, it isn't actionable," is key to detaching from colocated norms and positioning for success with all-remote. Manage expectations that this handbook will never be complete, and it may take months or years to even feel comprehensive.
Ideally, updating the handbook with policies and processes is something that the entire company is empowered and encouraged to do. For existing companies who do not have the luxury of starting their handbook as they start their business, consider hiring an arbiter to kickstart its creation and development. Former journalists and documentarians are great candidates for such a role.
Consider each aspect of your company culture that is unwritten or implied, and document each one. In a fully remote setting, there are no daily in-person interactions where cues are absorbed. Hence, it is vital to over-communicate not just in daily work, but in explaining and detailing values that company culture is built upon.
GitLab uses GitLab to build, sustain, and evolve its company handbook. GitLab is a collaboration tool designed to help people work better together whether they are in the same location or spread across multiple time zones. Originally, GitLab let software developers collaborate on writing code and packaging it up into software applications. Today, GitLab has a wide range of capabilities used by people around the globe in all kinds of companies and roles.
You can learn more at GitLab's remote team solutions page.
If at all possible, close the office. Shuttering an office (or multiple offices) offers the clearest signal that you're all-in with remote, and leaders are serious about ensuring that no one is treated — consciously or otherwise — as an outsider.
While remote work is liberating and empowering, it can be jarring and isolating for those who are not equipped to manage the change. In an all-remote or remote-first company, team members are well aware of what to expect even before they apply for a role. In fact, many remote companies receive outsized interest in roles specifically because of their remote nature.
It's vital for leadership to understand that there may be resistance to a remote transition from employees who would prefer not to work remotely, or are anxious about the lifestyle change.
Clear and proactive internal communication is essential to removing fear and instilling excitement about the increased autonomy.
In the GitLab Unfiltered video above, Darren (Head of Remote, GitLab) and Gabe (Senior Product Manager, GitLab) talk on the topic of going slow to go fast, as well as the importance of a "handbook-first" approach to companywide documentation.
All of leadership needs to understand the importance of documentation — not just with lip service. A true, genuine understanding of its value. If they truly understand the value of it, they'll emanate that to their direct reports.
For companies looking to transition to fully remote, a helpful step for leadership is to say: "OK, we're going to be remote-first as a start." This means that a company in transition would optimize everything in its physical office space to be remote-first. Instead of optimizing conference rooms with lots of tables, for instance, you have each employee sit in their own office and wear headsets all day. This is how you prevent remote employees from feeling disconnected and isolated.
This is going slow to go fast. Lots of energy up front — you go slow — but that accelerates things dramatically a year or so down the road. — Gabe W., Senior Product Manager, GitLab
Expect bumps along the road. As with any significant business transformation, it's wise to communicate proactively to team members, customers, and investors that obstacles will emerge. Transitioning a company to fully remote, while still running the business, is not easy. It's a long-term bet that the short-term pain will be worthwhile.
Leadership should be completely transparent with team members as the transition unfolds. Share headaches and roadblocks as well as successes. This should occur in an agreed channel so that discussion and feedback is centralized, and action items can be clearly disseminated.
Iteration is a core value at GitLab, and we strive to apply iteration to everything — from building a product to shaping our workspaces. This applies to business transformation as well. Implement the smallest viable change, solicit feedback, and tweak or revert if needed. By taking this approach to transforming your business, you're setting the example for how day-to-day tasks should be managed in a fully remote setting.
The cost of cross-team coordination is difficult to track; in many enterprises, this leads to delays and cost overruns. A sudden remote transition is an opportunity to address always-evolving policies for new applications, procurements, projects, and/or vendors.
The ability to charge forward and deliver capabilities is a combination of a few key activities:
Attempting to transition to a remote working environment while maintaining the gatekeeping effects of the system administrators and security teams may hinder aspirational values such as bias for action. Do not provide access to sensitive data sets or applications to unverified vendors or take any unnecessarily risky approaches, but try to shrink guard rails and take inventory of what is truly sensitive and/or confidential.
Leadership must foster creativity and intentionally seek progressive, two-way door approaches. Once a technique or application is proving itself out in the experimental phase, mature it with security evaluations and reliability. Importantly, any experiments that don't pan out won't have wasted months or years.
Organizations should consider hiring a Head of Remote Work. This may be titled Director of Remote Work, VP of Remote Work, Chief Remote Officer, or a variety of alternatives. Longer-term, this role may evolve into a Head of Workplace Experience, Head of Culture, or similar. Below is a series of fundamental questions that leaders must answer when transitioning to remote. It is unlikely that an existing team will be capable of directing adequate attention to these needs without backfilling for other responsibilities.
Finding a leader with extensive remote experience and a history of successful business or culture transformations will be difficult. Suddenly-remote companies may consider hiring a Chief Documentarian to establish a regimented documentation strategy, and morph this role into a more encompassing one over time. Former editors and publishers may be suitable for such a role.
A sample of questions to be answered by a Head of Remote Work:
Transitioning to remote work is not a binary switch that is flipped. While many organizations were thrust into their homes overnight, that is only the first of many steps. Remote is a journey of iteration — a tireless, evolving trek that demands a leader, or else your firm risks falling back into conventional habits or creating a fractured culture where no one is clear on what is expected.
The larger your organization is, or the more deeply it is entrenched in colocated tradition, the more significant the challenge and compensation expectations. This role will be far more complex in a hybrid-remote setting compared to an all-remote setting, as you're answering every question twice.
While GitLab believes that all-remote is the best structure to ensure that our values are lived and no one is treated as a second-class team member, the reality is that most companies formed to date have at least one physical office.
In many instances, it is not feasible to transition entirely to all-remote, though leaders and recruiters are starting to realize that remote work is the future. Stripe, for example, has stated that its "fifth engineering hub is remote."
Stripe has engineering hubs in San Francisco, Seattle, Dublin, and Singapore. We are establishing a fifth hub that is less traditional but no less important: Remote. We are doing this to situate product development closer to our customers, improve our ability to tap the 99.74% of talented engineers living outside the metro areas of our first four hubs, and further our mission of increasing the GDP of the internet. — David S., CTO at Stripe
Jack Dorsey, CEO at Twitter, has shared that remote is the company's future.
In instances where a company intends to maintain at least one physical office, but will allow remote hires for certain roles, added care must be taken. There is effectively nothing that can be done to completely remove bias that comes from seeing someone in the same physical space day after day, so leadership must be intentional about considering remote employees for input, feedback, promotion, and mentorship.
Added care must be taken to ensure that the usual downsides of hybrid-remote are not tolerated. Conversely, employees considering a hybrid-remote role must be prepared to gracefully manage said challenges should they arise.
Above all, a company which intends to begin hiring remotely (or allowing existing employees to optionally transition from colocated to remote) must structure the company as if every single team member were remote.
This means that any hallway conversations must be documented and disseminated for all who were not present to hear, and it means that in-office workers must each use a single webcam and microphone to join a group call (as opposed to in-office colleagues gathering in a conference room with a sole camera).
It means, for example, that colleagues who are sitting side-by-side must use a public Slack channel to communicate, as vocalizing a conversation would be unfair to team members who are remote.
This requires tremendous effort, day after day, from every member of the company.
Anyone can test their knowledge on Transitioning a Company to Remote 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
GitLab is the world's largest all-remote company. We are 100% remote, with no company-owned offices anywhere on the planet. We have over 1,300 team members in more than 65 countries. The primary contributor to this article (Darren Murph, GitLab's Head of Remote) has over 15 years of experience working in and reporting on colocated companies, hybrid-remote companies, and all-remote companies of various scale.
Just as it is valid to ask if GitLab's product is any good, we want to be transparent about our expertise in the field of remote work.
Making remote work well, particularly in companies with colocated roots, is a shared challenge. If you or your company has an experience that would benefit the greater world, consider creating a merge request and adding a contribution to this page.
Return to the main all-remote page.