As a CEO, I often ponder how I can help the team be as productive and happy as possible. As part of our decision to be a distributed team at Buffer, there have been a number of amazing advantages this has brought as well as it making a fun team to be part of due to the many different cultures and locations of team members. Recently I’ve seen quite a number of articles about remote working, and I’m excited so many are sharing their insights. I wanted to share some insights into how we do things at Buffer.
The decision to be a distributed team
During the few months I spent focused on the decision of whether to commit to Buffer being a distributed team, I sought advice from many people. Some of the best advice I received was from David Cancel, who I had the chance to sit down with and chat over coffee. His key insight was that in his experience founding a number of companies so far, he has found that two scenarios work well, while one doesn’t work too well.
He advised that we either be fully distributed, or have everyone in the same office. David said that the time he had a main office with the majority of people there and only one or two people working remotely, that didn’t work so well.
With this insight and further thinking, I made the decision and we became a fully distributed team. We immediately hired a number of people working remotely to quickly balance out the team and ensure we were fully distributed rather than a team in one location with just one or two remote workers. This was an immediate benefit to us especially as a team focused on outstanding customer support, since we quickly covered all timezones.
The delicate nature of a distributed team
The interesting thing I’ve found with a distributed team is that I believe it is a very delicate balance to ensure that everyone who is away from the main base location feels just as much a part of the team. What you don’t want is to end up with a scenario with people feeling like “second class citizens” if they are not in the base where the office is.
There are no advantages for people who come into the office, no disadvantages to staying home to get your work done.
I think this a super important quality of a great distributed team, and it is one we consistently keep in mind and something that causes many of the questions and choices around our distributed team.
Questions often in my mind while we grow as a distributed team
As a result of these difficult and important choices to ensure a distributed team works well, I often have some interesting thoughts and questions in my mind which to some could seem petty, but which I believe are essential to get right in order to thrive as a distributed team. Some of these questions we now have a confident stance on, others are things which still linger in my mind. I believe being a distributed team and figuring out the best path is a journey that will last the lifetime of the company.
Is it appropriate to have a base location?
This is a question I spent quite a number of months pondering. During the time, we were traveling the world having been unable to get visas to stay in the U.S. (we have visas now).
In the end, we realized that there are advantages to having a base location, depending on what your startup does. For us, we are in the social media space and we are regularly doing integrations with other startups. It just so happened these startups and the big social networks were all mostly based in San Francisco or Silicon Valley. Proximity to them was a huge advantage in order to secure partnerships.
Is it right to have an office in the base location?
For some time, we avoided having an office at all. By early 2013 we had a team of 9 with 4 in San Francisco. Some felt less productive working from home and coffee shops than they would in an office. We spent a number of months sharing an office with the awesome Storify guys and the team grew a little more, too.
We also started to focus even more on culture, and the whole team started to love the fact that the Buffer way was rather different to the norm. Being part of Buffer felt unique, and we wanted to embrace this further by having an office we could call our own.
I think most distributed startups have an office: GitHub and 37signals come to mind as good examples. Another key reason we got our own office is that while a large portion of the team are not in San Francisco, we do plan regular retreats to get the whole team in the same place. We decided we needed a sizable office to work together for the first 10-day gathering in san Francisco.
In-person meetings or everything via HipChat, Hangouts and Email?
With an office, if team members are in San Francisco it can be easy to delay meetings until all team members are in the office. I thought a long time about this and bounced the dilemma off Leo, too.
The conclusion we came to is that we should always do the thing we can do immediately. If we need to quickly have a meeting and we’re not in the same place, we should jump onto a Hangout, even if we are in the same city. In a similar fashion, we try our best to have a real bias towards chatting on HipChat and sending each other emails even if we sit across from each other in the same office. By doing this we are really embracing the goal of there being no advantage to being in the office, and it also allows other team members to jump in and share their ideas in discussions.
What perks are appropriate when you have a distributed team?
At Buffer we’ve had a lot of fun coming up with some perks that are individual to us. We believe that perks are not something you can take and apply to any company. Rather, they need to be an extension and enhancement to an already ingrained culture.
Most technology companies pride themselves on perks such as free meals and snacks at the office, as well as Ping Pong tables and other ways to take a little time out and refresh. The most interesting thing I’ve noticed is that the perks are almost entirely focused around what is provided within an office. A nice exception that comes to mind is Evernote, which provides all employees with house cleaning twice a month and also pays employees to take vacation.
At Buffer, our answer to this dilemma is that we try to focus on “everyone included” perks which are not tied to a physical office. With our culture of self improvement, one of our most interesting perks is that everyone on the team (and their partners and families, if they so choose) is gifted with a Jawbone UP, and this triggers great discussion around getting good sleep and being active. We give everyone a Kindle Paperwhite, and team members and family can get any Kindle book free of charge with no limits or questions asked. In the future, I can imagine other “everyone included” perks such as free gym membership and house cleaning.
What if people want to move to San Francisco?
The final question I want to share is a very interesting one: how do you manage having the right balance of people away from your base location of San Francisco if many who join find that they want to relocate to San Francisco?
This is something we’ve started to encounter which I never imagined could happen. So far Leo, Carolyn, Andy, Brian and I have moved to San Francisco, and Daniel is moving this week. (On the opposite end of the spectrum, Sunil moved away from San Francisco earlier this year.)
I don’t feel like I can force people to stay where they are. As the CEO of a company where we have chosen not to delay happiness, and with a journey so far where we have found a way to travel the world while growing the company 300% year over year, I think it is my duty to help people move wherever they will be happy, whether that is SF or elsewhere in the world. It just so happens that San Francisco seems to be one of the most attractive places to be in the world.
My answer to this one right now is to keep hiring outside the Bay Area. This seems to work well since it is very hard to find people in the Bay Area anyway!
This is a portion of the questions I’ve recently had on my mind. I feel it is a huge privilege to be able to shape the company and grow a distributed team. I’d love to hear any experience or thoughts you have!
Try Buffer for free
140,000+ small businesses like yours use Buffer to build their brand on social media every monthGet started now
With so many years of being remote, we’ve experimented with communication a lot. One conversation that often comes up for remote companies is asynchronous (async) communication. Async just means that a discussion happens when it is convenient for participants. For example, if I record a Loom video for a teammate in another time zone, they can watch it when they’re online — this is async communication at its best. Some remote companies are async first. A few are even fully async with no live ca
Like many others, I read and reply to hundreds of emails every week and I have for years. And as with anything — some emails are so much better than others. Some emails truly stand out because the person took time to research, or they shared their request quickly. There are a lot of things that can take an email from good to great, and in this post, we’re going to get into them. What’s in this post: * The best tools for email * What to say instead of “Let me know if you have any questions” a
At Buffer, we’ve long had teammates who have side projects in addition to working at Buffer. It’s pretty common for our team to run their own blog, we have several published authors on the team, and many of our engineers run apps that have nothing to do with their regular work. Though some companies prefer that anyone on their team not have side projects and actively discourage it, that has never been our way at Buffer. In fact, working at Buffer means you get a free Buffer account, making it e