It's really great that working remotely (anecdotally) works well for your team. It also doesn't work well for some folks. Like any other approach to business, YMMV, but discounting the disadvantages that have been enumerated for you is explicitly ignoring the fact that some people, including those who are top performing employees in their fields, prefer not to work remotely.
It's best to make the decision and your own recommendations acknowledging there are trade offs, no?
Some these can be both! I have been working remote since 2008 and our entire team went remote in 2013
Communication: We are much more streamlined. No more "hallway talk" that doesnt get recorded or followed up on etc. No more "did you get my email?" kinda crap. Much less (I won't say no more!) impromptu meetings gathering way more people than needed in the office that could have been resolved in a simple email
Isolation: I'm going to assume this is different than "loneliness"? I like isolation to work on hard problems, or just be super productive. We still video conf, phone, and chat, but outside of that all the coders love their isolation time
Timezones: This is definitely a challenge at times, but the boss man loves knowing someone is awake somewhere in the world should servers catch on fire.
Discipline: Is the person who doesn't do work at home the same one that would be checking their fantasy sports or hn/reddit/facebook at work? I guess if you were in an open office and everyone could see what you are doing 100% of the time you'd be "forced to work" but do you want that on your team anyways? You know that BS line in most job postings about "self motivated" it could actually apply for remote :)
loneliness: I can definitely see this for some people I've worked with in the past, there is no advantage to being lonely. I would say use your added free time of no commute to go out in the world and do something fun. Sometimes its great to not be around work people and not talk about work
I'm not a very good country music singer. When I sing country music, I feel shame, discomfort, and general depression. Therefore, I don't sing country music.
Even if you are having a successful time hiring great people that are happy remote, how are you going to retain them? A remote software job is much closer to a commodity than a traditional software job. (I read the 37signals book and built a remote team over 5 years; in the end the difficulty finding people that are truly happy remote meant retention was difficult and, overall recruiting and cost of living considered, a remote team was, for me, a net wash).
Edit: after thinking more, it's even worse; you don't know if most applicants can really be happy singing country music for a year, 2 years, or longer... Even those that seem to really value and are excited about the prospect of singing country music may learn before too long that it's not for them.
In the current climate all software [engineering] jobs are commodities from an employee viewpoint.
As an introvert, there is only so much social interaction I can take in a day. The office burns through most of it.
I agree that when it comes to team productivity rather than personal productivity, offices do work better. Especially when people of varying skill levels are involved.
We're all over 30.
Managing a distributed workforce, definitely has challenges. From what I have seen, onboarding new employees can be particularly awkward. It may be different in hip, new startups, but in my experience with less fashionable, old school organizations, it makes accountability, knowledge-sharing and organizational-political navigation more challenging.
I've been working for a 100% remote company for 3 years now. It was an adjustment. But everyone who was here before me gave me advice to do well in this environment. And everyone who was hired after me got the same support and guidance. We also all get together on occasion, and when we do, we brainstorm how to do things better.
I do miss the casual social side of having colleagues in an office from time to time, but I tend to be quite a social person. That, and maintaining delivery over a long period of time requires focus and discipline, no small effort.
The disadvantages are the health problems that occur if a remote worker is sitting at home all day, physically and mentally. These can take years to begin manifesting themselves and are really bad if the remote worker can't self identify them.
Certainly it's made it easier to jump on the home elliptical, lift a few weights, do a few chin-ups, or run outside for 45 mins.
Back when I was in an office downtown, it was an expensive and time consuming project to go out 4-5 times a week to a gym at lunchtime or after work, then need to shower immediately before you can be around your workmates again, etc.
I'm also so much more relaxed now that I don't have to commute. That was a real stressor.
So about two times per year, once for a tech summit we go to , and another we have our own summit, we take over a hotel and hang out. During this time we also gives talks and other things but it is half fun and half work.
I think occasional face to face time and bonding time is super helpful, but not everyone needs that every day, and I think in our case it had made these twice a year meet ups something we all really get excited about and look forward too.
If the entire team is distributed, a lot of those challenges are mitigated. If only a few people are distributed, then you can get problems like unequal access to information, or unequal access to people. Even though my team is used to remote workers and is very conscientious, it is not unusual to have things change direction without anyone thinking to inform me. The "everybody knows" problem is pervasive.
Access to people is even more difficult. When you are working locally, it is easy to brainstorm with someone while walking to the store to buy lunch, for instance. You have a certain amount of influence on the team because conversations are low cost. Remotely, you have to come up with the idea on your own, then send an email, wait for a response, etc, etc. It is not spontaneous, which means that by and large remote workers have much less influence than local workers. Even with hangouts, IRC and slack, it's hard to generate the same banter that you would have locally (especially when you are separated by 9 timezones).
If there is anyone local who is keen on political machinations, you pretty much have to be happy with letting them have their way. You will be outmaneuvered at every turn. This places a much higher requirement for trust on remote workers. You have to trust that people will tell you about things, and then ask for your input and then wait for your reply -- rather than just doing what they wanted to do in the first place.
As I said, if you are a fully remote team, this is less of an issue. However, there are still lots of challenges in this scenario. One of the biggest surprises that I had when I moved from local to remote on my present team was how my attitude towards my team mates changed. When I was local, I went out for drinks with people, and chatted about sports and basically hung out with them. When I was remote, most of my interaction centred around code.
In the local situation, if I was pissed off about a technical issue, or something that somebody did, then my attitude towards the person was tempered by my general good feelings about them as a person. In the remote situation, my interface with people is almost entirely technical, so when someone does something I don't like, I tend to feel badly about the person as well as the issue. This is something that I need to constantly remind myself about -- they are good people doing things I don't like. It is much easier to forget this when you are working remotely, I find.
There are many other challenges as well. It's not that these challenges are insurmountable, though. You need to build a culture where people operate in the way that works for your team. It sounds like you have done that on your team. On our team as well, I don't think there is anyone remote who would rather be local, so from that perspective it works well. There are people on our team who would much rather be local and I can understand their feeling. I suspect there may be one or two people who would rather that there weren't any remote people on the team because it interferes with how they would prefer to work. I respect that too and always try to accommodate my team mates. It's a balancing act.
Super low bandwidth audio/video/screensharing.
Excellent tools like Slack and Speak really help comms. We pair program very often by sshing into a tmux session which makes any lag close to nil. We use Trello for sprints. And Invision for product work. It's extremely efficient.
We have our usual retrospectives and watercooler talk and it feels natural.
Every 6 months we get together for fun.
------
The advantages of being remote far outweigh the disadvantages. Rather than listing all the advantages. What are the disadvantages?
..I'm thinking.