Fleep is a distributed team, one of those where people work remotely between two different cities here in Estonia. Most of our backend and mobile client engineers are in Tartu and front-end, UX, design, marketing and customer service has a cozy Fleepcave in Tallinn.
Handling the team of 12 people in itself is not really an issue in a small start-up like Fleep, however… trying to pull all the people together virtually is a challenge in itself already.
Communication, communication, communication…
It can’t be emphasized enough how important daily communications are for remote teams. Especially for the ones that are building a communication tool themselves.
Our day-to-day business, conversations, development, bug chats and discussions all take place in Fleep. We pride ourselves for dogfooding our own product. This helps us understand best if we are building a useful product that would work for start-ups and teams similar to us and helps us pull our remote team together.
Jeff Atwood from Stack Overflow writes: “You need a way to casually ping your fellow remote team members and get a response back quickly. This should be low friction and available to all remote developers at all times. IM, IRC, some web based tool, laser beams, smoke signals, carrier pigeon, two tin cans and a string: whatever. As long as everyone really uses it.”
And that’s the case with us as well. It’s not unusual that conversations in Fleep carry on during non-working hours in the evening or even on weekends. It’s up to the team members to decide whether they’ll respond right away or when the new workday starts, different people have different approaches, but the conversations stay there, always in sight, whenever you sign in.
With Fleep it’s easy to see who has already read the messages and who’s currently active in the chat as well. This adds speed and relevance to the lean development efforts.
Eye-to-eye conversations for longer topics
Regardless of how great the chat application is, it can never really replace human behaviour and honesty in real eye-to-eye conversations. In our team, whenever we see that a chat conversation is taking a wrong turn or misunderstandings arise, we call each other using Skype. Adding audio to your communication adds a special layer of trust and understanding. From someone’s voice you can easily detect if they’re agreeing with you or are hesitant and confused.
“Regular catch-ups and conference calls should be scheduled so that work can be fairly distributed and everyone knows what they are supposed to be doing.” states The Guardian in their article How to manage remote working teams.
It’s the same for us, we have a regular weekly meeting either in-person or via a Skype call with the team during which we discuss topics that need further discussion or clarifications. We also use these opportunities to share what we did during the previous week and what we will be up to in the upcoming one.
Bringing the team together
Staying in touch with the team using chats and calls is not all it takes for remote teams to feel like they’re connected. Every 2nd week we bring the whole team together to Tartu or Tallinn and make sure that people get enough time for those important one-to-one conversations. Oftentimes that is all that it takes to get on the same page and get some of those invaluable insights shared between team members.
“Developers and designers often need long, uninterrupted periods of time to get meaningful work done,” explains Chad Halvorson, CEO of thisCLICKS in the article Are Remote Teams the Future of Work? written by David Hassell.
Apart from design talks and development discussions (read: heated conversations) it’s also crucial to make sure that the junior engineers working in the team get the chance to learn, progress and tackle the more complicated tasks together with the senior engineers who are not always co-located. This works a lot easier if the person who is helping you is sitting right next to you.
Always in touch, but not stuck together
It’s easy to fall out of touch with remote team members if you’re not sitting across the table with them and it’s vital from the start-up culture point of view to make sure people get the feeling of being united, whenever they come to the office or even when they don’t. That’s why we have a continuous Skype call going on day in and day out between the Tallinn and Tartu office TVs. That way we can see if someone is in the office, if they’re currently busy or simply joke about the fact that they’re playing ping-pong on the other end of the line.
Ultimately, the decision about how distributed a team can be comes down to the needs of that team: do you need to talk every day? What type of people are in your team? What are the personal habits of the team members? Once you know all this, you can easily decide which of the solutions works best, or which 2-3 tools you need to make the most out of communication.
Now it’s your turn, tell us what your team habits are? How are you working together remotely and what kind of tools are you using to make sure the team feels united even when there’s a long distance between them? Feel free to ping us via Twitter or Facebook to share your thoughts!