3
10 Comments

Mythbusting: Biggest Myths about Remote Dev Teams

Myth 1: It’s difficult to recruit the best developers for remote teams

Reality: Opening up remote working options and recruiting remotely can make the process more inclusive, wide ranging and ultimately more successful for the company. Aleksandar Đokić of Toggl – the productivity software run by a fully remote team – thinks this is especially true for developer teams, reflecting that having a larger talent pool “offers great possibilities for creating amazing teams and awesome apps”.

Myth 2: Remote developer teams are hard to manage

Reality: Software automation experts Zapier take a similar stance, believing that micromanaging remote teams is “toxic and counterproductive—you’re basically admitting that you don’t trust your people to get things done otherwise.”

Myth 3: Remote companies don’t grow as fast

Reality: Fully remote working may have once been indicative of an early-stage startup, but if you still think that’s the case then Gitlab would like a word.

Myth 4: Remote dev teams are less productive:

Reality: Back to Gitlab to help dispel this one, with their 2021 Remote Work Report. 3900 remote workers worldwide were surveyed to expose the impact working fully distributed had on work outcomes. The following outcomes were cited as top reasons employers chose to stick with a remote work model:
Increased productivity: 42%
Increased efficiency: 38%
A reduction in bureaucracy and politics: 24%
Improved documentation and process: 20%

Myth 5: Communication and Culture suffers

Reality: “Culture is stronger when everything is written down,” says Ian Tien of Mattermost, “because everyone who joins the company has the same baseline.”

More detail here: https://insights.adadot.com/2022/04/20/remote-working-mythbusting-with-the-top-remote-dev-teams/

on April 20, 2022
  1. 2

    The first 4 myths are busted but I don't agree with the 5th one here: Myth 5: Communication and Culture suffers.

    I'm apart of a 2 remote teams and its obvious to me that the team chemistry ends when the work day ends. I rarely see remote workers willing to take their relationships offline, and this isn't to disparage them, but before the pandemic I remember in-person devs would usually grab a beer or hang out every once in a while. The online nature of dev work now has made the work transactions i.e. people do their work, then they go home. And that's fine, maybe thats a better way for things to work, but culture certainly does suffer in a remote team, especially in startup teams that don't have the funds or money to be able to fly everyone around the world just to hangout for a few days.

    1. 1

      My gut feel is that this is one of those "you get as much as you put in" types of things. And there are definitely a lot of companies that chose remote working as a way to access cheap workers, not as a way to empower their staff. We are flying all of our sales team from the UK to Greece for a few days in the summer to meet some of our devs. Is it expensive? Yes! But we know that you have to be deliberate at building culture when working remotely because you are missing more of the serendipitous office moments.

  2. 2

    I work in several remote teams (as a part-time dev). Myth 4 isn't just a myth, it's an outright lie. Personally I find I'm much more productive when I do async communication. Synchronous communication (scheduled meetings) simply kills me.

    1. 1

      100%! asynchronous comms allow you to remain into a state of flow without as many interruptions. Coding is a far more creative job than most people thing and its very difficult to do well with constant interruptions.

  3. 2

    We have experienced developers who write FAQs for their colleagues - they understand that the exchange of experience at a remote site needs to be encouraged; it will not happen by itself. Meetings three times a week also help.

    By the way, joint programming saves from isolation. The atmosphere is like in the office: you work for a couple of hours. Then someone notices a colleague's poster with a movie on the wall. Everyone discusses the trailer for the new film for a few minutes.

    Have you ever tried it? It's suitable for sharing experiences, too.

    1. 1

      We discovered this about pair programming randomly when we were preparing for a Product Hunt launch. Just be creating a Slack Huddle (like a jump-in audio room) we were able to increase our velocity massively and morale improved!

  4. 2

    Nice post Alex. I agree that it's likely the number of remote teams will continue to increase across all industries where working this way is viable (e.g. excluding jobs like doctors, dentists, chefs etc...who necessarily need to be on-site to perform their jobs).

    But studies like the one you mentioned (Gitlab's 2021 Remote Work Report), always make me wonder what's actually going on in terms of performance. For example, the study found that the majority of workers prefer working remotely. So, it's difficult not to question their methodology, which was:

    "GitLab Inc. surveyed 3,900 adult professionals, aged 21 and older across the
    US, UK, Canada, Australia, South Africa, Brazil, and South Korea, from
    February 12, 2021 to March 10, 2021, who were currently working remotely and
    will continue to after the COVID-19 pandemic."

    If Gitlab knows most people prefer working remotely, surely surveying them to see whether they think their "productivity has increased" isn't the best way to obtain impartial results...of course, they're likely to say their productivity has increased because they want to keep working remotely...

    An analysis of Gitlab's report by Bloomberg found:

    "There's a disconnect between the ostensibly high levels of satisfaction with
    remote work and the actual pain people are feeling day-to-day. While 4 in 5
    would recommend remote working to a friend and 81% of people are satisfied
    with the level of productivity, teamwork across organizations is struggling.
    Just over a third (37%) report that their organization does a good job of
    aligning work across projects."

    So, I'm not saying workers who work remotely aren't largely more productive. I just don't think the report answers the question reliably...are they actually more productive or do they just say they are?

    1. 1

      Some very good points here. The methodology suffers from the same limitations that any survey-based data would. I think there is essentially a difference between the personal productivity angle and the way companies provide the right infrastructure for this to happen.

      For example, not commuting is saving me 4+ hours a day of getting ready and getting trains etc, however, if then the company replaces these with pointless micromanagement and reporting then I would rather have my commute back!

  5. 2

    This comment was deleted 4 years ago

    1. 1

      I spent a decade managing over 200 people across 35 countries for very large businesses that had a hub set-up. Our company is much smaller at the moment (8) but quite distributed. Its not for everyone and for sure the culture aspect is something that needs special attention. Culture in remote does not "just happen" in the same way that it does in person.

      Having had the luxury of building my small company from the ground up the one thing that helped was hiring deliberately people with personalities and previous experience to show that they can work remotely. For example ex-freelancers. Those people were used to being autonomous and greatly enjoy a remote set up. People who love to travel is the other sweetspot because they can appreciate the freedom and they bring a lot of joy with them in meetings etc dialling in from a different country each time.

      Things like pair coding and spontaneous drop-in audio sessions every Friday afternoon helped a lot too. Will that scale well? Only time will tell but these companies are examples that it can be done.

    2. 1

      I resonate with a lot that's been said throughout this thread (I think some generalities are probably fair), but also agree it's very complex and is highly dependent on the individual, team, department, position, tenure, etc. I've seen devs become more productive working remotely and others become less productive. Comms and culture have improved in certain ways and deteriorated in others. I found certain devs easier to work with remotely but others a lot harder.