How diverse, invigorating, gratifying, and productive could your day be if you threw away the notion that you had to stick to a daily routine?
On this page, we're detailing what life can look and feel like when embracing a non-linear workday, paired with suggestions on catalyzing your imagination to consider possibilities that simply are not possible in a colocated, synchronous workplace.
In the GitLab Unfiltered video above, Darren M. (GitLab's Head of Remote) and Elisa R. (Founder of The Cowork Experience) discuss the impact and purpose of routines when looking at satisfaction and productivity.
A common recommendation for those new to remote work is to find a routine early on, and stick to it. While this may be sound advice for some, it ignores the reality that remote enables a complete deconstruction of the perceived need for routine.
Routine is a common suggestion not necessarily because it is good, but because it is tradition. Routine is mandated in a colocated environment, where team members are required to commute and work between fixed hours. We have been conditioned to believe that routine keeps us disciplined, when in reality, routine simply makes it easier for colocated companies to keep workers in line.
Remote decouples routine from responsibility. Indeed, managers of one thrive in a remote setting, and exhibit more discipline to work well when no one is looking.
Many people adhere to routines simply because they know no other way. Remote allows another option, thanks to the tremendous benefits of asyncronous workflows, handbook-first documentation, and companywide transparency.
In the video above, GitLab's Head of Remote talks with Megan Dilley (Director, Remote Work Association) about remote work's democritizating power, the importance of community, and projections for what life will look like after the great remote work migration of 2020. Discover more in GitLab's Remote Work playlist.
Perhaps the most useful approach to describing a non-linear workday is to share an example. In transparency, this is an actual example from a GitLab team member.
Darren wakes up at 6:00 AM on a Tuesday in Montana. After a shockingly brief 30 second commute from one room to another, he's ready to start his workday, coffee in hand.
Darren begins work at 6:30 AM, and works until 8:30 AM. He changes his Slack status to a skiier emoji, noting to colleagues that he'll be out through 4:30 PM local time. (This distinction is important, as his company works asynchronously with colleagues across an ever-changing array of time zones. Said another way, time is relative.)
He then cooks breakfast, eats with his family, and packs his ski gear into the car. By 10:00 AM, the family is skiing. There is almost no one on the mountain, as the vast majority of the world is following a typical routine that pulls them into a colocated office by 10:00 AM on any given Tuesday. Lift lines are nonexistant. Lift tickets were heavily discounted — it's Tuesday, after all — and there was no traffic to contend with. All of these are spoils of an off-peak life.
By 3:00 PM, Darren and his family ski back to the car, refreshed after an exhilarating day. Given that they're departing the mountain before rush hour has any impact on traffic, they're back to their rental apartment by 3:30 PM.
After a shower and an early dinner, Darren logs back on to work at 4:30 PM, enthused to tackle ongoing projects and help move issues forward. But first, he shares a few photos he grabbed while skiing — something that is encouraged when you operate in a non-judgemental culture and measure people on results, not hours. Though working remotely with hundreds of colleagues across six continents, this deliberate approach to informal communication creates personal bonds that are, in many ways, deeper than those formed in-office.
Because it's winter in Montana, it's fairly dark outside by 5:00 PM. Darren has maximized his daylight hours, and has time-shifted his working day to primarily occur during darkness. Given that he would likely be indoors during this time anyway, it's more conducive to work. There is no pull to leave and explore the outdoors when it is dark. Instead, it is an ideal time to work, despite the fact that resuming your work day while most others are ending theirs is incongruent with the conventional definition of routine.
We should pause at this point and recognize that time is still relative. When Darren resumes his workday at 4:30 PM, he has six more hours to contribute if working a standard eight-hour day. It is important to not get caught up in local times. 4:30 PM may sound like an absurd time to resume working, but that's morning, afternoon, and night for various other members on his team.
The non-linear workday decouples time from work and acts as a forcing function to embrace asynchronous workflows. Local times are only as important as your company relies on synchronicity to get things done.
The more this bothers you, the further you need to distance your organization from synchronous defaults.
Answering the above will allow you to truly evaluate what elements of routine are beneficial to you, and which are holding you back.
The above skiing example is a maximally efficient day. It was a full working day, and a full day of exploring and spending meaningful time with family. The above team member could've opted to take PTO (paid time off), or opted for a shorter ski session. He could've taken a half-day, thereby extending the ski session or simply providing more buffer time between work and play.
You could swap anything in for skiing and envision how it could apply to you. From participating in midday school activities with your children, to helping with a midday community service event, to being available to serve as support during an important medical appointment for a loved one — the examples are endless.
The point is, a non-linear mindset gives you options to break free from routine and structure each day differently.
In a GitLab Unfiltered conversation, Dani from Ceridian asked GitLab's Head of Remote the following question: "What’s a question that people don’t ask, but you feel they should, about remote work?"
His answer is verbalized in the video above, and partially transcribed below.
What could life look like if I never had to commute again? If I did not have to be in this particular city for work?
What you're seeing en masse (due to COVID-19) is people being thrust into remote, and they're trying to replicate virtually the in-office experience.
I want people to give themselves permission to realize that remote is an entirely new universe. You don't have the commute. You don't have the stigma and office expectations. You can potentially shift your day to work during your peak productivity hours, which opens up hours that have never been accessible to you before.
It's the ultimate blank slate, the ultimate life cheat code. There tends to be remoter's guilt, where you feel like you need to over-produce as a remote employee to compensate for the removal of a commute. The commute was never the employer's to begin with; that was always your time.
You can do something with that. You can be innovative with it. — Darren M., Head of Remote, GitLab
The example detailed here would not have been possible without a few realities already in place.
The obvious question when discussing such examples is this: "How do you leave work during a time when meetings are most likely to be scheduled?"
The not-so-obvious answer is: Create a workplace culture where meetings are a last resort, and ensure that unavoidable meetings can be contributed to asynchronously.
It bears repeating that not every single day will present itself as a natural, meeting-free day. However, the more intentional your company is about ruthlessly minimizing meetings, separating decision gathering from decision making, and insisting that all work begin where it eventually needs to end up (e.g. in a GitLab issue or merge request), the more feasible it will be. You'll also realize benefits on the mental health front.
Anyone can test their knowledge on the non-linear workday of working in an all-remote enviornment 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,200 team members in more than 65 countries. The primary contributor to this article (Darren Murph, GitLab's Head of Remote) has over 14 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.
GitLab believes that all-remote is the future of work, and remote companies have a shared responsibility to show the way for other organizations who are embracing it. 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.