Tags: remote working, communication, software development, teamwork
This post was originally published on the surevine blog.
3 months ago, I took the next step in my career and joined Surevine as a Team Lead. There were many things that first attracted me to the company, but one major benefit was that it’s totally remote, and so learning how to work collaboratively whilst remote was a challenge that really interested me.
Sureviner’s are spread all over the country, and my team alone covers a geographical area that stretches from Durham to Plymouth. Although I’m only 3 months in, you learn pretty quickly what works and doesn’t when it comes to remote work. Here’s what I have discovered:
By far the most important thing I’ve found about remote work is that it’s much more necessary to be specific when you communicate. It’s far too easy to misconstrue meaning without body language clues you get from face to face. Here at Surevine the very first thing we do with new starters is talk them through how we communicate. I’ve seen the same thing at remote meetups such as Agile in the Ether.
Establishing ground rules at the beginning makes communication easier and more effective. The only thing that surprises me is that this isn’t more prevalent in traditional work environments. Effective communication is key to shared understanding whether you’re working remotely or not.
Working in your own space with very few distractions does wonders for productivity. I’ve previously found open-plan offices can ruin an agile team’s effectiveness, and when I used to work in an office I would regularly have to work late just to have space and time to get anything done. With remote working, I’m set up just the right way for me; we use statuses a lot to show colleagues our availability meaning that finding the time in the day to get stuff done is not an issue.
There’s no getting away from it, sometimes it’s just necessary to get together face to face. At Surevine we’re not shy about this. If it makes sense to get the team together, then we do. Booking travel and co-working spaces is simple, and we try to book spaces that are relatively central to the whole team.
We have a policy of using trains as much as possible, as public transport is much better for the environment, but it also allows us to continue to work whilst travelling (in fact I’m writing this post on a train right now!)
Because people are taking the time to travel there is much more commitment to making meetings a success — nobody wants to spend a couple of hours on a train for nothing. We prepare clear agenda’s with expected outcomes, for which I tend to use the phrase ‘We will know this agenda item is complete when…’.
On a day to day basis, we are just starting to explore how techniques such as mob programming could work remotely to help improve collaboration, although this needs to be balanced with keeping up our productivity. But as they say, there is nothing more useless than doing something efficiently, that shouldn’t have been done at all.
Once a quarter we get together as a company to collaborate, we call them RLMs (Real Life Meetings), which can seem rather strange, meeting someone in the flesh for the first time who you know well and work with day to day remotely.
Regularly posting what you are up to can feel weird at first, if you have come from a low trust environment it can feel as if you are being watched. Why does everyone need to know what I’m up to? What are you going to do with that data?
That’s not the purpose of status updates, it’s intended to show colleagues your interrupt-ability. If you’re free to take calls, set yourself to free. If you’ve gone to the kitchen to get a cup of tea, or really need to get your head down and concentrate, set an away status. It avoids your colleagues wasting time when you’re not available, and avoids you being interrupted when you need to focus.
Super productivity and laser clear meetings all sound great for a business, but not a lot of fun. I’ve found a few times that I have forgotten to add the human element to meetings. This runs the risk of de-energising the team and I’ve become more aware of the need to inject some fun into some meetings after all happy people are productive people.
We have a few things we do at Surevine specifically: Nic, one of the other team leads, introduced a down tools session to just get together and hang out and get to know one another, which has grown and is now open to the whole company. On Friday’s we run ‘Techcellence’ a chance for Sureviner’s to come along and talk about whatever is of interest them, which, despite the name, can range from tech to history to food.
I have been surprised at how easily distracted I am, but it’s not uncommon. We regularly talk about techniques for getting down and focusing. Some folks like white noise, some like to use the Pomodoro technique, others (like me) like to visualise their work on a board and move things to ‘done.’ The difference from office work is that we actually talk about this stuff and look at ways to improve it. Offices are just as distracting, but rarely have I had a conversation about what I can do to make that better, it’s just accepted as part of office life.
In my first few weeks, I found I wasn’t really leaving the house and I was getting irritable and restless. It sounds obvious, but I just wasn’t spending enough time outside. Now I aim to go for a walk around my local park before starting work, and often at lunch too. The fresh air resets my brain and helps me reconnect with the outside world.
We find that when working with clients who are office-based, often remote calls become a group of people huddled around a laptop. The amount this affects effective communication cannot be understated, even with standalone mics. We, therefore, try to operate a one-person remote, all remote policy to make communication more effective.
We use a whole bunch of VC tools because there’s no perfect one. Primarily we use:
The best thing by far about remote work is that it’s more obvious when things aren’t as effective as they can be. Often in office environments, poor working practices and communication are accepted as the ‘norm’, whereas a remote company is wholly dependent on effective communication and working practices.
This forces remote teams to pay more attention and to adjust and improve. This results in teams who are extremely effective at working together and getting things done.