I still don't agree. In my experience, the added productivity gains from working in a Peopleware-ideal office, where I could occasionally stop by a colleague's office to ask a question, were not much greater than what could be accomplished through video and chat. The personal "comradery" gains were slim to nil as well.
The negatives are tremendous. Wasting time traveling to the office. Wasting time appearing to work, which is probably 50% of the average office workers day if we're being honest. Having to arrange your life around work instead of the other way around.
If nothing else, I think a fully broken-down cost analysis of your office layout plus the higher cost-of-living expenses built into employee wages when hiring in a big city would convince you that remote is the way. Probably looking at 30-50k per employee savings for hiring remote vs SF, and getting happier, more productive employees.
You make many good points. However, I find that some of them still affect remote work too. For example, people still make efforts to "appear" to be working. They will make spurious commits to version control. They will ration out a series of questions or emails that could be more concisely sent together. And god forbid the company uses Agile/Scrum, which is a Pandora's Box of ways to appear to be working without working at all.
Still, your points are well taken. On the other hand, if a company is really looking at fully-remote work as a way to avoid paying higher wages, that would be a red flag for me. I'm very good at what I do, and even if I'm not co-located in Fancyopolis, I expect to be earning a competitive wage based on the value I can add to the business, not how much a gallon of milk costs for me. It comes off as extremely petty and divisive for a company to intentionally play cost of living to their advantage like that. And further, what stops a person from choosing to live in a more expensive place? Your company is in Milwaukee but I want to live in London and work remotely.
The kinds of risks that employees face are very asymmetric when compared with what employers face. For a lone employee, the single number that is your annual compensation is a big deal. Other companies might force you to tell them that number if you seek a new job. And whatever that number is, that's going to determine your pay. Those other companies won't give a shit about cost of living.
Let's say you used to live in SF and made X-thousand per year. Then you took a new job in Austin, TX, and someone convinced you that you should accept something like 0.7X per year, because Austin is cheaper and 0.7 still leaves you quote unquote above market there.
A few years later, you're looking to move to New York, well guess what, you're salary is going to be pegged to 0.7X, not X, and you might have to negotiate hard even just to get it back up to X in New York, let alone arguing for whatever premium the 0.7X might have been above market in Austin.
That's just how these things work. Have you negotiated pay when considering a move from a major city to a city with lower cost of living? I have before, and one of the major points of discussion was that salary actually should not decrease in response to cost of living changes. That's just an unpleasant side of it that the hiring company has to eat. The risks facing the lone employee are too high that they'll never recover the "downward adjustment" amount if they ever find that they need to move on to another area again.
When I speak with HR reps about this, I've never had a problem. Sometimes they will say they are not looking to pay in the range I am seeking, but they universally understand and fully expect it when candidates say that their salary should not decrease purely due to cost of living decreases.
I still don't agree. In my experience, the added productivity gains from working in a Peopleware-ideal office, where I could occasionally stop by a colleague's office to ask a question, were not much greater than what could be accomplished through video and chat. The personal "comradery" gains were slim to nil as well.
The negatives are tremendous. Wasting time traveling to the office. Wasting time appearing to work, which is probably 50% of the average office workers day if we're being honest. Having to arrange your life around work instead of the other way around.
If nothing else, I think a fully broken-down cost analysis of your office layout plus the higher cost-of-living expenses built into employee wages when hiring in a big city would convince you that remote is the way. Probably looking at 30-50k per employee savings for hiring remote vs SF, and getting happier, more productive employees.