Why Do We Still Commute?
citylab.com
citylab.com
Everyone knows the benefits of working from home, but there are downsides as well. Fixable downsides, but they exist nonetheless -- it is easy to become a hermit. Easy to over-work. Hard to draw the line between your work time and your personal time. Easy to get siloed into your current job, while not keeping up with the rest of the company and enabling career growth. Easy to let poor communication habits turn into real problems. And when your entire company works from home, as mine did, you develop a culture of acting like there is no better choice, and the benefits of your personal flexibility at home outweigh any problems at work... causing people to not fight very hard to fix problems, and to stay in those jobs longer than they should because of how comfortable the working situation is.
Now, all of those things can be handled if you have personal discipline, good co-workers, and great leadership. But not all teams can truly claim those qualities. So I feel both working environments have their good and bad sides, and the choice of which situation to pursue is a question that needs to be answered with some solid contextual information about the team, the culture, and your personality to know which one is truly best for any specific individual at any specific job.
Not just that, but there's also the other side: Easy to procrastinate, easy to give false reports which then leads to regular overwork in the days just before a hard deadline.
I know these issues from remote workers I worked with, but also know this personally while working on my Diploma theses.
While we are at it: Working on Diploma/Master thesis is in many ways very similar to remote work: One works mostly from home, maybe in the library but even there mostly alone, i.e. not in an office, meeting one's mentor at most once per week. I met with other students which were in the same situation - just to get into a group feeling. That worked quite well, even though we had no overlaps in our topics and hence not much to talk about.
The situation is a bit different if you write your PhD thesis, as that usually means you have a job at the university during that time, and at least have an office and collegues.
Working from home for three years now as a software project contributor, this is my biggest problem. I always get my shit done, but it gets majorly stressful since daily family life goes on the same regardless of my self-inflicted work crunches. Pretty sure the tradeoffs are still worth it, though.
That doesn't seem a problem unique to remote work. It's more about when tangible outputs are required from you.
This is so, so true for me. I used to work in a place which had an office, but you wouldn't be expected to be there most of the time, just come in at least once a week, maybe for meetings, etc.
I used to procrastinate and report progress to my manager when there was much less. But since the work was deadline-based, I'd just grind through the weekend with little sleep and catch up with what I've reported. I've never missed a deadline, but I'm still feeling bad about doing it that way and misleading them.
Just to be clear, this was a long time ago, when I was just starting my professional career, and didn't yet have stronger ethics.
(Throwaway for obvious reasons, the employer I worked for at the time browse HN)
This isn't a remote problem. I see this _all_ the time with people at work now and I don't work remotely.
This is more of a personal issue -- some people do it consistently, others don't. I never had that problem working remotely, and I don't pretend to be somewhere else in my regular reports in the office either.
One solution that usually works for me is to get a standing workstation and use it. Not one of those fancy ones that go up and down. Just one that is permanently up, like the Ikea standing desk hack. For a break, you can move and sit somewhere else. Standing takes a lot more energy, so, it is my belief, that you focus better because if you are standing and goofing off, you are wasting precious energy. There are times where you don't have the energy to stand but need to work - so just sit. Standing and sitting is not a either/or thing. You don't have to be faithful to your standup desk, go slouch in a couch for a break.
The biggest difference between standing and sitting is that walking away from your workstation is friction-free. You just move your feet.
Then what's the point of not getting a table that can go up and down?
The commute? 10 minutes on the bicycle. There's a song by Tripod about the distances between home, work and shops being your triangle of hapiness. Not that serious, but it has some substance of truth https://3pod.bandcamp.com/track/triangle-of-happiness
Being the IT guy, I have to be in the office a lot of the time, but having 1 or 2 days to focus on projects at home and have no walk-up interruptions is very helpful.
Besides, if I really don't want to work, it doesn't matter if I'm home or at the office. I am a champion at slacking in the office. I can stealthily alt-tab like a motherfucker, and I see you coming long before you can see my screen.
However I must confess that the downsides of working from the office majority outweighs the other.
I can no longer focus. I am constantly pulled into meetings. I have 120 minutes of commute everyday.
When I get home I am too tired and can no longer spend quality time with my partner like I did when I was working from home. And above all my sleeping schedule has to fit the 9-5 schedule and it is very hard to adjust.
I also have to deal with the heavy Canadian storms during winter.
In the future I'm choosing remote work at a heartbeat and might even consider a salary cut to get it.
YMMV.
I think this is often an environment and culture problem. When I'm setting something up, I work hard to create spaces that minimize noise and distractions. And I think it's important to limit meetings, because they'll definitely expand to fill all time available. But most places don't bother with either of these, throwing people into noisy open offices and having a "meetings first" culture.
> I have 120 minutes of commute everyday. [...] When I get home I am too tired
This is the true killer for me. 15-30 minutes each way by foot, bike, or public transit? A pleasant part of my day, a useful demarcation between work and home. But an hour each way in a car and I begin to despair for my life.
In addition we have some of the harshest winters with freeing black ice falling from sky :)
If this behavior changes solely because you start working remotely it may not necessarily be to your advantage. Yes, in the short term you may maintain the ability to focus. However, in the long term you may find yourself being excluded and and diminished within the organization. These meetings, etc. don't stop when you work remotely, only those attending them do.
> if you have personal discipline, good co-workers, and great leadership
I agree this is true, and have seen a couple of high-functioning distributed teams. But a question for me: if we have those things, do we want to spend them on working from home? Personally, I'd rather have a modest commute and spend our discipline and leadership points on solving a problem in the world.
Working from home can make a manager feel less control. It takes a different type of leadership. But requires less leadership points.
I also think the sexual assaults thing is a terrible red herring. Remote teams still should get together regularly, and abusers will happily abuse then. For that matter, abusers are perfectly capable of being abusive remotely. (Exhibit A: the internet.)
Since the purpose of going to the office is not to do actual work being able to work from home has not removed the need for the office.
The vast majority of time spent by office employees is socializing and non-productive ritual work.
Do you have any links or sources to back this up?Source: https://www.vouchercloud.com/blog/office-worker-productivity...
The last time I worked in an office, I got most of my work done in the morning or after 6pm when no one was in the office.
On the flip side, when your entire company works from offices, you develop a culture of acting like there is no better choice, and the resistance to change outweighs its obsoletence, causing people to not fight very hard to evolve the workplace, and to accept offices longer than they should.
I worked from home full time for about 3 years then moved to a job that had about 1.5 hour commute each way. One of the reasons I took the job was the fact that I did feel like a hermit. I then started to resent the commute. I'm lucky that I have been able to work out a deal with my current employer where I work from home 2 days a week and come in to the office 3 days a week. This gives me a nice break from the commute but I also don't end up feeling like a hermit.
1) I get out of the house and I just seem to focus much more there at the office.
2) I feel like a normal human going to an office and talking to others. (Maybe I don't always talk to others, but I can if I want.)
3) When I want to be lazy and just stay home, I just do.
4) Co-working space or cafe is just a 2-15 minute walk away. No commute in a car.
While it's debatable whether remote works for businesses that can work remotely, it imposes costs on the rest of us, especially those who can't do their jobs over an Internet connection, and those costs should be paid by those who willingly incur them, not whoever they can push them off to.
On the other hand, employees would have an incentive to try to stretch out their commute as much as possible, to get extra pay for time "not working". I don't know how rampant that would be. I like to think most people hate commuting enough that it wouldn't be worth it to make an extra $20 sitting in traffic when you could just be home faster, but who knows.
As an employer, I'm indifferent between paying someone $50/hour for an 8-hour work day, or $40/hr for an 8-hour workday plus 2 hours of paid commuting.
I think it's more likely that the interview process would just have another step to suss out how much commuting time I'd be paying you for, and then figuring out how to divide up your day rate of $400 (higher in reality, of course) across the buckets. So Laura Long Commute gets $40/hr * 10 hrs/day and Sally Short Commute gets $50/hr * 8 hours/day.
You'd have to be careful about that. Employers might end up, in data, showing a negative impact against some protected class (married people, certain races) if they weigh hiring or compensation decisions based on proximity to the office.
It's my understanding that current jurisprudence doesn't require proof of intention to discriminate, just evidence of disparate impact. Single and married people live in different neighborhoods. Different races do as well, depending on the city. Non-heterosexual people tend to cluster in certain neighborhoods, too, for that matter. If a class action suit can show that married people are paid 10% less than single people for equivalent roles, it could be problematic.
Regarding the second point: Employees always have an incentive to try to stretch out their tasks, so employers already know how to minimize that behavior. If employers paid for commuting, commuting would be managed like other tasks.
I don't know. I worry that would immediately become a major form of discrimination -- it would inherently put anyone who was poor/middle-class or anyone with any sort of family/children at a huge employment disadvantage. Large companies would only ever hire already-hyper-wealthy individuals for their main positions (since they are the only people who are ever allowed to live in dense urban places). I'm imagining employers in Seattle saying "We like this guy, but he doesn't live in Pioneer Square where our office is, so that will be a pain, we should pass on him"
Many people already have to deal with that discrimination somewhat in terms of employers only being in major cities. Having that hyper-charged down to just major cities wealthiest neighborhoods seems like an even worse situation.
Obviously enough economic incentive exists to convince people to spend the time and effort to commute, but if city centers were more affordable to live in, many fewer would choose to live so far away from work. Myself included.
I agree, and would personally do the same too if possible. But I've watched us artificially inflate property values for literally my entire life. Even in my tiny US Midwest city in the middle of nowhere, city center prices have never been remotely affordable.
We should take it for granted that it's too expensive to live in US/CA/AUS/NZ cities -- because that's the honest truth. That's been the current state for decades, and there's very little chance that any major city center ever becomes affordable again in our lifetimes.
Obviously, we should still try to fix this. I fully support trying. But every facet of our society is wholly dedicated to preventing city centers from ever becoming affordable. Affordable city centers just are not likely to happen. We should not assume regular people live in a situation that doesn't exist, and likely never will.
Also, you have to remember, in places like the bay area, you can't just pick up and move closer to work. People have enormous incentives to never move: Proposition 13 means you get 5 times lower property taxes by staying put. Not to mention the enormous imbalance between housing and jobs. All the jobs are on the peninnsula and all the housing is in the east bay. All these problems would just be amplified.
I think we're miss-stating the problem. The problem isn't that employers are forcing us to commute long distances with poor company placement. The problem is, we as employees don't have enough power to choose/demand where we want to work. There's simply too much labor supply and too little demand. So, if a worker demands to work remotely, the company can just say: we'll fire this guy and hire one of the countless others willing to commute 2 hours or more.
Just to prove my point: Here in the bay area, companies still place themselves on the penninsula where there's a 4 to 1 ratio of jobs to residential places to live. By that math, they shouldn't be able to hire anyone. And yet, they're having absolutely no problem filling positions, because workers are extremely desperate for money. So desperate, they're willing commute 2 hours or pay 60% of their paycheck to live closer. These are all symptoms of labor oversupply and too little labor demand.
They already do. I'll take a lower salary from a company that doesn't make me commute.
I prefer an alternative approach: a telecommuting incentive tax credit. Telecommuters themselves get a tax credit and companies also get a tax credit.
That would be the fastest way to spur more remote friendly workplaces. Then the environment, congestion, commute stress, etc will all be reduced. The "cost" of the credit would be more than offset by reduced road maintenance costs, lower pollution, fewer accidents, etc.
Unless you're dealing with customers directly, or making a physical product, there's no reason that offices in their conventional form should exist.
If a congestion tax worked, the overall burden would go down, because businesses would work harder to locate offices near where employees are (or want to be). And they'd also likely get more active in things like housing and transit policy, because it would be to their direct financial benefit to make sure that development was more balanced.
My career has suffered because I have never wanted the stress of a long commute nor could I afford the real estate prices and city problems involved with being closer in. It's a bunch of diminishing returns every direction I look, so my solution was to just find work that was less desirable but at least manageable in the context of my whole life situation. I contend that people who don't do that eventually suffer mental breakdowns, but have no evidence to back up that claim other than conjecture.
As it stands, my current commute is still bad, but I bet it's only 10% as bad as the hell most people around here go through. I've decided that working for a living is just generally bad for health, but a necessary evil, of course. I probably sound like a whiner, but I am truly interested in the commuting problem because I work for a company that heavily promotes cycling to work and ride sharing. Unfortunately, the infrastructure between my home and my work location precludes safe cycling along much of the route so I don't do it, but a lot of employees do. Instead, I stupidly get up at 5:45am, get out the door by 6:30am or so, creep along on a stupid, dark bridge with lots of other stupid people, then arrive to work around 7am or so, depending on the breaks. At least the drive home isn't as bad as long as I'm on the road by 3:15pm or so.
I do get the occasional work from home day, but our team is highly collaborative, so I'm at a disadvantage if I'm not at the office. In previous roles I had more autonomy and could thus make a better go of remote work. I worry that 100% remote roles make you a non-entity in your organization and thus dispensable.
Being remote might contribute to, or increase the risk of, not being effective, but it's not the most proximate cause.
Too bad just paying poor people not to use the bridge isn't politically correct.
It would be a heck of a lot more efficient than combining a bunch of disincentives that affect the lower classes.
Why does nobody ever try free public transportation? Paying the poor brings a lot of practical issues, but at a minimum you can make them not pay for taking the long route.
Because someone has to pay for it.
I'm on the job market now and the most feedback I get are from jobs that would be 45 min - 1 hr minimum (in the same city). I've done it before, it's terrible for my health and mental state.
Moving closer isn't an option because it's even more expensive than the already expensive area I live in now and the salaries won't compensate to offset that.
If you have a job, you're selling your labor. The commute is part of what you have to do to get your goods to market. Are you, as a purchaser of bananas, "pushing off the costs of transport" on to the seller? That seems silly considering the transporter prices that into the bananas, just like workers can price in longer commutes. Don't accept less money to travel further each day.
I think a fairer deal would be if commute time counted against the typical 8 hours of work. That way everybody's interests would align around having short commute times.
Also, not all of the commute cost is the fault of the employer. For example, my commute is a lot shorter than many of my coworkers, because I place more importance on a short commute than a cheaper, bigger house further away. My coworkers value having a bigger house more, so they live where the housing is cheaper but the commute longer.
How would your price this in? Would the people who commute further get to work shorter hours, just because I chose to sacrifice for a closer commute?
This is a severe misunderstanding of the economics of the situation. Employees know that they're going to be spending time commuting, and they take that into account when they decide whether to take a job. In more academic terms-- that information is already informing the labor supply curve of which each individual is a part, and thus the market is already incorporating the information in the wages.
If you've ever taken microeconomics 101 then they'll probably have explained how it doesn't matter which side of the market, buyer or seller, pays a tax on business. The tax is incorporated into the price one way or another, whether it's the buyer or the seller that has to actually pony up the physical cash, and the actual tax burden of the two sides has nothing to do with who does that. The same principle applies to commuting, which is after all just a tax that the workers have to pay to the void when they have to wastefully sit around in their car.
- Covering the cost of a FastPass
- Deciding where to locate a new office based on where employees live
- Offering a company shuttle from a train station
- "Google Bus" and other similar initiatives
- Offering a potential employee a higher salary because of their long commute time
These things happen all the time, and all bring a portion of the commute cost into the company.
BTW I've never heard of a company moving for its employees' benefit, unless by "employees" you mean "senior management & board members".
There are plenty of examples that show that working remotely without daily face-to-face interaction can work very well.
What's markedly different about environments that successfully adopted remote work are aspects like:
- a lack of cargo cult work organisation and office politics
- an atmosphere of trust rather than petty control freaks who need to constantly keep an eye on their subordinates in order to know they're still 'working'
- adapting to different forms of communication
When people say that they can't communicate as well with someone who isn't in the same room that doesn't necessarily mean that a remote setup doesn't work. It could simply mean they're just lazy and not willing to adjust to a different kind of work environment.
Working remotely requires the participants to be much more communicative because in such a setting communication for the most part doesn't just happen serendipitously, you have to work to make it happen.
With all that (plus what you said), most individual employees will prefer the office over remote access. So remote would only work if you moved everyone from the office to remote access at a single point in time.
Colleagues on the same level that hang out and discuss the latest new TV series seems that's good, but I don't think the bonds that builds are always strong.
1. All work-related discussion should take place in formal meetings.
and
2. No non-work-related discussions should ever happen in the workplace.
?
If you are having a discussion with your boss don't bother him when he is on a break, book a meeting.
I agree with parent poster in large orgs but in orgs where the founder eats lunch with you that level of formalness is awkward
"I'll grab a donut from the store across the street. Does anyone else want something?" - "No, we don't because YOU'RE FIRED."
I suspect that a workplace where work discussions happen only in form of formal meetings would be rather unproductive.
There also seems to be a lack of properly planning tasks and as such this lack of planning is papered over with the sort of serendipitous spontaneous communication that happens when you have to walk over to someone and ask them what on earth is going on.
A focused remote worker can be orders of magnitude more productive than the typical office worker who is simply doing "busy work".
The driver of this lack of trust is the rise of managers (e.g. MBAs) who have limited expertise in the fields which they manage.
For jobs where there are measures of performance that are accurate and not gameable (e.g. certain call center workers) and/or it is a job executives probably reckon that they could do themselves, they are generally happy to let employees work from home.
IMO this is why Github and Mozilla are remote-first - by and large they're managed by developers.
I doubt that the government will allow any remote work any time soon because most of the people here have never heard of a VPN or even know what a secure password is.
We live in a post Snowden world. It only takes one mistake to have all your data out in the wild.
I think attributing changes away from trusting employees to simply "bad management" and ignoring issues like employee malfeasance... is overly simplistic and dilutes complicated issue conversations.
There needs to be a balance between trust and security. It's easy to take it too far in either direction.
Your boss doens't need to know how to do your job.
Without intimate knowledge of the tasks you do they have no idea of what you are asked to do is intrinsically hard or you are simply doing it badly.
The above assumes a single developer. If you have a team of developers it quickly becomes obvious. In fact a boss who knows nothing about programming is probably better able to judge if someone is doing a poor job in these cases: those who know the new guy see him trying to get up to speed, while the boss sees a bigger picture by comparing to others. (a good developer will be making useful contributions on the second day, while a bad one will flounder for a couple weeks before the others will give up on teaching him the project)
I've been on such teams and that isn't what happens. This is:
* Team mates do not like badmouthing their coworkers unless they do not like them. Hence, if a coworker complains about another coworkers' performance its as likely to be due to a personal problem as it is performance. Most coworkers also won't know each others' wages so they are in an even poorer position to judge relative performance.
* Managers without technical chops are incapable of distinguishing hard tasks from tasks that are being done badly or easy tasks and tasks that are being done well. They are incapable of distinguishing quality engineering from hackjobs that will blow up in 6 months. They will either default to just assuming every developer is more or less equally productive or use terrible proxies for productivity (like how late each developer stays at work or their scrum 'velocity').
* Good performers who do not have their achievements recognized will leave for better paid positions, leaving mediocre and poor developers. The quality of the product takes a dive. Profitability may also take a dive as a result if the industry is competitive and the quality of the software matters.
We also had a lot of slowdown because we were stuck on a shitty off-the-shelf program he bought. He went for this one instead of the more usable competitor because it was cheaper. If he could get developers to build a working tool in the cheap product by holding them 'accountable' in his Excel sheet, he could push for the product to replace the more expensive competitor and gain some reputation in the corporation.
In the end, most of the project was a horrific failure. His best employees left, and control of the project was transferred to another manager inside of a year or two.
I think a lot of this could have been avoided if my boss had any idea about what he was managing.
Do not allow your experience with a bad boss to clutter your thinking about how a good boss would handle things.
But seriously... I would expect there to be examples of both - Good remote teams. Good office teams. Bad remote teams. Bad office teams.
And every shade in between.
I'd, personally, prefer a mix? Couple days in the office... couple days remote. Time to "schmooze" with the team. Time to be in a quiet place to concentrate.
Why does it have to be one or the other? Anyone that claims one extreme is better or worse generally misses the truth: The best option is generally somewhere in the middle of the extremes.
(I love working at the cafe and shared work spaces, but that isn’t the same.)
Yes. Having managed remote teams and being a remote dev, it's all about response time. If someone slacks you, the response should be as quick as if it were verbal in the office. If it takes 2 hours to get a response out of someone - then they are not participating correctly on a remote team. The team should work in a way they can all be online at the same time so communication can flow freely. If someone is interrupting you and you need concentration just explain it to them - like you would in the office.
Immediate responses is a remote team. Day long responses is contract work. Week long responses is open source projects and government work.
Two-minute responses on Slack absolutely is a model that can work, and perhaps it's the easiest transition for people who've been working in a "teamy"/open-plan on-site setup. But I'm also convinced that it's not the only viable setup.
Likewise, if everyone knows that due to people's different time zones, schedules, etc. that 24hrs is a typical response window via email, there should be no complaints if responses aren't received more immediately.
Doesn't work when people just write "@here, making nachoes" all day.
`@here` should really be yellow. Only direct communications red. Or something other than the current system.
While this can work for some people, such "interruptible anytime" mentality may not be good for many workers. For example, when I am most productive I need to minimize, and ideally eliminate, disruptions. Such periods are short (2 hours at most for me), but I could do 90% of day's technical work in those 2 hours. If someone wants something, unless it is a blocker for a large team, I will put it away and get back to it later.
This has nothing to do with being remote or local, this is just the mode at which I am productive. I try to treat folks who work for me the same way: we can still meet daily in the morning I try to give them enough structure so I do not need to preempt them every hour. Things happen, there are failed systems that need to be fixed now and other fire drills, but I find most people in technology development more productive when on an async comm channel. I am.
Maybe I am just old and you youngsters do not need to do it this way :)
It takes significantly more discipline for a PM to run things this way, but the reward is often better productivity and happier, less frazzled developers.
This is pretty much why I don' want to work remotely.
At the office, when busy, I can turn my email and IM off. If people need something, they are welcome to come to me and I'll engage with them. I do not want to deal with urgent issues over any kind of IM. If you are not physically present, then call me and we'll have a voice chat.
My frustration is that IM is used for both urgent requests, as well as non-urgent ones. It's used as an alternative both to phones (immediate need - synchronous) and to email (no rush - asynchronous).
My fear in working remote is that I'll get too many non-urgent interrupts using IM. I cannot see a good reason to use textual IM over a voice chat. If it's not urgent, just use email.
So while I agree that response time can be important, there should be clear policies on the medium used for it. If the team mostly had policies that match my preferences, I could do remote work. But I suspect most teams will disagree with them. Hence I get my way in the office.
Taking 2 hours for a response is often fine at the office, BTW. It all depends on the context.
>Immediate responses is a remote team. Day long responses is contract work. Week long responses is open source projects and government work.
There are very few jobs that really fit this categorization. At my work (in the office), we often respond to things the same day. On the flip side, today I plan to respond to something that had been requested a week ago. I don't work in OS or for the government.
If someone wants a quick response, they have to explain the need for it in the email. If it's open ended, it goes to the bottom of the queue. I'm willing to bet that since they haven't bugged me about it, they either no longer need the information, or it is low priority for them.
When Mr. Exec wants a status update, and he wants it RIGHT FUCKING NOW. I'm not going to E-mail you and hope that your inbox doesn't have 10,000 other unread messages, or text you and hope you respond. I have to physically hoof it over to where you sit, apologize for interrupting, and get the info Mr. Exec needs. That's hard to do remotely.
If I know in advance I need a response about some topic, sure, try async first. If the deadline's a day out, E-mail, if it's an hour out, text or IM. But, after that if you don't respond, I've got to be the bad guy, break your concentration, and call you. And, if you don't pick up, I'm headed to where you are physically.
If your company culture embraces remote work it also must embrace responsiveness and a communication style that clearly conveys when responses are needed.
It's droll that Slack is the name of the service chaining you to notifications. I wonder if that was deliberate.
Is it more important to actually get stuff done or to be available for every distracting slack message that comes through?
If you need people to respond within 2 minutes to every message, that is lack of organization imo unless it is an emergency.
Good remote teams are very organized, prioritize documentation, have weekly and sometimes daily kick off meetings and then for the most part get out of the way for their team to get stuff done.
Let's say you're right and people are to blame for being lazy. How would you address this?
This isn't all that different from what in larger organisations is nowadays called agile transformation. How often do we hear "Yeah, that whole agile thing is nice but it doesn't work for us."?
The reason why 'agile' (or any other new approach for that matter) doesn't work in these cases often is that people are only used to doing things a certain way and are too lazy or otherwise unwilling to let go of that way and try a different approach.
Bringing about change on that scale is a long and often painful process. It's not that people are inherently lazy or stupid. It just can take considerable effort to unlearn habits you've gotten used to over a long time.
The crucial difference - at least so far - between the adoption of remote work and that of agile methods is that the latter for better or for worse nowadays seem to be largely accepted as the common approach for organising work (in the software industry at least).
As for remote work on the other hand there's no large-scale buy-in by (middle-)managers. I think this points to a larger issue at play here: Implementing remote work can surface shortcomings and waste.
If remote work requires workers to proactively communicate amongst themselves anyway what do you need traditional facilitators like middle-management for? With agile software development methods there are at least still roles like Scrum master or product owner that to some extent still resemble those traditional roles.
With remote work implemented properly we could very well arrive at a point where those roles aren't needed at all anymore.
There are extensive sets of studies that show all of that it generally doesn't, where it especially doesn't, and why it doesn't (which the article mentions.)
Data > anecdote.
https://www.gsb.stanford.edu/faculty-research/working-papers...
http://www.cosocloud.com/press-release/connectsolutions-surv...
https://www.zenefits.com/blog/remote-employees-happier-and-m...
It could also mean they actually have sufficient social skills that they're able to make full use of the higher bandwidth available face-to-face, and aren't willing to suffer thru the markedly inferior communications that are all that's possible over the 'net.
To be frank, people using IM to communicate with me disrupt my flow a lot more. They start a thread/conversation/request, and then are slow to respond, or disappear. You can't do that face to face.
Face to face (or even telephone) forces people to prepare. Rarely do I see people work that way with IM. People tend to realize that they are interrupting someone if it's a face to face. In my experience, many (most?) workers don't view IM as a significant interruption to the other party. So they feel much more free in using it.
That's the primary benefit of qorking remotely IMO. Not having to immediately stop everything im doing allows me to stay in flow state. It also improves the quality of my responses and solutions since i can let the request percolate in my head. Usually, I come up better answers when Im not actively thinking
>Not having to immediately stop everything im doing allows me to stay in flow state.
So is it OK in remote work for me to turn off IM for 2-4 hours to remain in flow state? If not, then there will be no flow state for me.
Conversely, I’ve seen plenty of “mandatory meetings” in remote work as well. Neither paradigm seems particularly advantageous.
Good managers ask when they actually need something and they expect those working for them to accommodate such requests immediately. That is why, after all, they are managers.
That's why they are managers and not low level developers. Developer does not like it? Well, a developer can migrate to writing less code and caring more about business related stuff. It is not like those who can write serializer cannot figure if a certain fire drill is required based on the amount of $$ coming in from a customer who is affected by a bug/wants something.
You missed the part where the manager has to evaluate and push back if needed. If their primary role is merely to do what their bosses tell them to, then they are not doing any managing.
99% of the companies can replace 75% of the managers with supervisors ( foreman in constructions/manufacturing ) and get a better result. Most of the "teams" inside organizations dont need managers - they need supervisors as organization does not need to have mini fiefdoms.
You are missing the point of what a manager is.
Good managers know how to ship products by knowing how to manage knowledge workers and removing friction in the communication inside and outside the team.
2. Good managers set direction and exist to acquire resources for the team and eliminate barriers out of the way of the team when they are headed in that direction. Their role is not to interrupt the team so that they can answer a question from upper management.
3. Most of half of urgent manager requests are due to lack of planning either on their part or on their manager's part. They knew they needed this information a few days ago, but felt "it's OK to interrupt the team when I really need it".
4. Most of the other half are due to their inability to push back.
5. There will be times when the managers do need information urgently. It is then their responsibility to accept the hit in productivity that it incurs.
I've worked with both good and bad managers. The good ones have these qualities.
I think these are both true and would advocate for a work solution that allows amble work from home but encourages common face to face time especially if a team is tackling a complex issue. Maybe two or three days per week remote?
Remote vs face to face debate is about the interplay of folks trying to earn a living, providing value to an organization, living life, and companies making profits. In this regard, it looks like a balance of remote to face to face could increase productivity, happiness, and ability to work on complex tasks.
I can either put a lot of time and effort into remote communication, or I can work closely with people in a space that supports direct communication, putting that time and effort into whatever we're actually trying to do.
I freely grant that most office setups are shitty, so that for many people they waste time commuting and then waste plenty of time dealing with a bad office space and bad office culture. But that doesn't mean that offices can't be great places to work.
If I have my choice, it will always be working in close physical proximity with a team, just as long as we have a good space for that and a culture that supports actually getting things done. I like writing and am good at remote communication, but I'd rather save that energy for actual productive work.
But regardless you need to put in the same effort documenting in person. Being able to talk over a solution doesn't help anyone when you've left the company.
Speaking as someone who has worked in three different remote companies of varying sizes, I have not found any evidence that remote teams achieve this any more frequently than conventional ones do.
> - an atmosphere of trust rather than petty control freaks who need to constantly keep an eye on their subordinates in order to know they're still 'working'
Again, I have not seen that remote teams make this any easier than conventional ones. Moreover, I think proponents of remote work in general are unaware of, or vastly underestimate, how many remote coworkers fudge their productive time because they can get away with it.
You can just as easily establish a culture of trust in a conventional office environment.
> - adapting to different forms of communication
Sure, but it’s unrealistic you’ll appeal to everyone’s favorite mode of communication, and many people don’t really care to adapt because they don’t need to. It is just as unreasonable to expect in-office coworkers to adapt to remote workers as it is to expect remote workers to come into an office for face-to-face communication.
I agree with you that remote teams can be effective in communication and productivity; however, I think your comment does more to support the position you’re arguing against than it does to negate it. Listen to what you’re saying here:
> Working remotely requires the participants to be much more communicative because in such a setting communication for the most part doesn't just happen serendipitously, you have to work to make it happen.
This is fundamentally why most companies do not have remote teams. It’s attractive to remote workers and to teams that are entirely remote, but most people don’t really want to work remotely most or all of the time. What you are stating evidences this friction, because you keep reiterating that remote teams can be just as good if they put in the work, but that’s precisely the point - most people and teams really don’t want to put in the work because it’s an extra hassle.
You started your comment by attacking the idea that face-to-face interaction is important, but it quite demonstrably is important. By your own comment (and my experience, as well), remote teams need to invest a significant amount of “cooperative machinery” to make communication and productivity as seamless as it is in face-to-face interaction. That’s obviously not to say it cannot happen, or that it shouldn’t be a goal, but my point here is that this is an additional hurdle that companies considering remote teams need to be work on, which is frankly unattractive.
Some people are disciplined and motivated enough to work productively in any environment, and that’s fantastic. Some people are not intrinsically so, but they become that way in the environment of an office. And some people are simply never optimally productive! Also consider that while a very vocal minority of people want to work remotely, this does not typically jive with people who are in-office and who then have to deal with an additional friction to communicate with some subset of coworkers.
I guess to put my point more succinctly: yes, of course remote work can be wonderful and properly engaging for optimal productivity if the majority of your coworkers are intrinsically motivated and really want to work remotely. But that’s not the world we live in, and it’s not reasonable to put the effort of achieving that ideal on companies that have already established a culture that works for them through face-to-face interaction in the office.
You speak of cargo cult, but your entire comment reeks of it. Ok, we understand, you like being able to isolate yourself. That's nice, and I'm glad you found a niche, but it's not the same for the vast majority of jobs and people. You call other people lazy, but I think perhaps that's just you. Social interaction and moving above an intermediate level where you can isolate yourself is hard work. Don't be so dismissive of others that strive for more.
Working remotely is great for the unambitious and the antisocial. Please stop trying to put those who do more down though.
I think you touched on a sad aspect of tech. For anyone to be "ambitious" or to "move above an intermediate level" they essentially have to become managers, which means less technical work. The likelihood of you joining the VP/higher ranks and still working on low level issues, as a respected technical fellow, are low to nill (Google, FB, MS have some positions but otherwise you're filtered into a manager to "move up.").
Your comment about "striving for more" is disrespectful to most developers/engineers.
How are people who spend their entire work days talking to others, but not actually working, "doing more?" I've seen more talkative/social people not getting work done than "antisocial" workers being "unambitious" or stagnant.
I lived 10 mins away on foot from my job. It was all fine and dandy for some time, but then things got seriously tense in the workplace and it meant the super short commute gave me no time to unwind. It ended up being mentally taxing to live so close to my workplace, even when I was not working since I ended up being near or walking in front basically anytime I got out. Nasty. Too long a commute and you're wasting so much time and energy in our life, but too close and it can have deleterious effects too.
(took some photos... https://gallery.tasuki.org/2017/10-few-hours-in-tallinn)
I used to walk with my wife to her office and back when I started full remote work (it's been 6 years, in a fully remote company).
Also, you're free to rent coworking space or shared office space if you like to. Working remote means you have a choice - not that you have to work from home :)
People traveling for 30-90 (or more!) minutes to and from work, particularly the ones driving in traffic, are the commuters. And the ones I know that fall into that category hate it.
Good for you that you have such a nice situation, though!
Between a chatty wife, active kids, and unfinished projects around the house, I don't have the willpower or ability to avoid distractions at home. I'm more productive going into work even if you factor in the time spent driving.
Plus, my drive gives me some down time to listen to audiobooks or podcasts. I do look forward to self-driving cars though (adaptive cruise control helps a lot in the meantime...)
Commutes are not all bad. But the bad ones can be miserable. Self driving cars (for all drivers!) would make it so much better...
Generally it's not bad in the morning, and it's going home that's worse, but at that point, it matters less if I get sweaty.
I used to bike 30-45 minutes each way to work, and, yeah, I got very sweaty. I always wished there were a shower I could use there. It's not ideal biking (or walking) weather, for sure.
One additional anecdote I'd like to share: my coworker just moved to be under a mile from the office. His first time biking to the office from his new place was under five minutes. The other day he had to drive home. He messages me afterwards: "Took me 31 minutes to drive 9 blocks". (5:30pm and raining.)
So I love my bike, even in the Texas summer. :-)
I worked for a company in NYC for years and lived 8 miles from work. It took me a minimum of 90 minutes to get to work.
You seem to think I can either just uproot my family and move to some sort of utopia city with short commutes, good public schools, and well-paying jobs; OR I can just change New York City itself.
The fact is that most people in the US have commutes of 25+ minutes. Folks who walk to work are not the norm, and city schools across the US are a complete failure and joke. Don't assume your situation applies to everyone.
* According to the US Cencus Bureau: https://project.wnyc.org/commute-times-us/embed.html
A majority of people don't have to prefer something for it to become standard. It's possible for only a minority of influential or vocal people to prefer commuting for it to be widespread.
In that case, 'they' prefer it, not 'us'.
So while I don't like the commute, I do still prefer it to living closer to London.
This is not quite a commute.
Still, sounds more like a daily walk that happens to be to the job than a commute.
When I'm at home I'm specifically not at work, which means I don't do any work, I don't think about work, I don't talk to anyone from work (unless there's an emergency that someone else can't fix).
What I think would be an awesome balance between this, is very small regional shared offices. Just shared office spaces that offer usage of their space as a 'subscription' to businesses, and as part of that subscription you get 24/7 access, a desk, internet, a kitchen etc. That way you don't have to have dirty dirty work things in your house, AND you only have to "commute" to a potentially very local office.
If your job is well defined, e.g. make an app or a website design, you can do it anywhere in the world. The app/design is your deliverable that anyone can see and judge.
If your job is a poorly defined "management" or "product ownership", with no real deliverable, how can your work be judged? Your job turns into convincing other people that your job is useful. Work long hours, seem busy, attend meetings, leave the office late. An epitome of the corporate environment.
This is in general a common, elusive mistake: "We can't measure it, so it must be zero." Better to be ridiculous and say it's worth between $100 and $10,000.
Value is lower because of the consequences of being hard to measure.
Then there are actual bullshit jobs, whose value is difficult to measure because they have no value to begin with.
How do we know the value has been increased at all?
We'll finally be able to stop tying health insurance to employment in the ridiculous way that we currently do.
Skilled professionals will more often be able to make their own hours and find more variety/novelty in their work by taking jobs for a variety of customers.
And there will be so many freelancers that a solid industry for helping them connect with consumers of their services so that the hardest part of freelancing (finding work) starts to become a non-issue.
Transitions are messy, of course.
I can think of an awful lot more jobs that are pretty well defined but nonetheless can't be done in someone's living room.
The person you're responding to didn't say what you think they said.
That's the OP's exact words. Inspecting a ship hull is clearly defined, yet I cannot do it in my living room. Likewise mopping the floors at MacDonald's. Very clearly defined, yet cannot be done anywhere in the world; I have to go to the actual floor that needs mopping.
True, I probably get more done on the days I work from home as I don't have a commute, and there are fewer distractions, however, I find I can collaborate far more effectively when I'm in the office - instant messenger, email and video calls just don't cut it.
Plus I have an amazing commute, mostly along British A roads through the countryside.
Allowing remote work is not enough. It requires effort from both parties. The company needs to provide money for home office setup, and the employee needs to spend time and though setting one up, which might be tricky in places with insane real estate prices. Working from sofa is not really sustainable for long.
Although work from home eliminates distractions such as constant movement of people (although this is not unique to working from home and same could be done with private offices), it opens a plethora of new distractions, be it running errands, playing with pets, or just goofing off instead of TV while keeping an eye on instant messenger.
And the list goes on. But that's not the point. Sure, working from home has a lot of advantages and at the end of the day I am very glad that I made the switch. It's just not as simple as some might make it appear as.
1) Control from above in the hierarchy (the general wants to see the army)
2) Control from below especially in competitive setups (the troop wants to know what's going to happen)
Then there is little like seeing people face to face to remind them you exists. This is good for business. I'm a freelancer now (about half of my career) and work mostly from home but I go meet customers in person almost every week or every month, depending on how much we work together (directly proportional.)
Furthemore, face to face collaboration is very effective when in hurry.
Granted, I'm pretty bad at self-discipline
We had one guy who had a nice house with a big dining room, and once a month we'd work from there in one room. Less work got done, but some things that otherwise might never have been done/resolved got handled. Plus it was "kind of" fun.
So unless you're geographically too far from colleagues, there's no reason why you can't have meetups (and I would advocate for them... occasionally).
This is a fallacy. If something really needs resolving, the setting is not relevant.
Sometimes on person describes an annoyance they have, and one of the other people in the room feels motivated to resolve that issue. Or a couple of people start talking about something, and a third person has a new idea that improves thing. There are endless scenarios that can result in something happening that otherwise might never have happened without the meeting.
Search for: "collaborating writing tool", "virtual whiteboard" etc.
The latter are usually part of teleconference tools. Here's from an open source one: https://www.youtube.com/watch?v=4MNqiMEblgo
They let you write stuff (even with a pen, on a touch capable display) and have others see what you write (and even write/erase themselves).
What else is missing?
Standing in person before an actual whiteboard? Smelling the marker's ink? Maybe with the advent of cheap VR and smell-o-vision we'll get that too.
VR would a giant help as body language, gesturing and physical size all become much easier to see. Of course, that would require quite a leap forward in VR to accomplish that level of avatar.
You can draw things in different sizes through remote whiteboard, you can add helpful icons and your voice can get louder or quieter for effect.
And you can't effectively draw some things on a tiny monitor screen.
That's a deeply abnormal situation. It's like talking to someone while sitting in front of a fun house mirror. Who would subject themselves to such a metaphysical nightmare?
And that's just one of the little uncanny distortions that video conferencing brings.
You might enjoy this excerpt from a novel, which predicts a bad future for video chat:
http://declineofscarcity.com/?page_id=2527
Sample:
> It turned out that there was something terribly stressful about visual telephone interfaces that hadn’t been stressful at all about voice-only interfaces. Videophone consumers seemed suddenly to realize that they’d been subject to an insidious but wholly marvelous delusion about conventional voice-only telephony. They’d never noticed it before, the delusion — it’s like it was so emotionally complex that it could be countenanced only in the context of its loss. Good old traditional audio-only phone conversations allowed you to presume that the person on the other end was paying complete attention to you while also permitting you not to have to pay anything even close to complete attention to her.
And:
> This sort of appearance-check was no more resistible than a mirror. But the experience proved almost universally horrifying. People were horrified at how their own faces appeared on a TP screen. It wasn’t just ‘Anchorman’s Bloat,’ that well-known impression of extra weight that video inflicts on the face. It was worse. Even with high-end TPs’ high-def viewer-screens, consumers perceived something essentially blurred and moist-looking about their phone-faces, a shiny pallid indefiniteness that struck them as not just unflattering but somehow evasive, furtive, untrustworthy, unlikable. In an early and ominous InterLace/G.T.E. focus-group survey that was all but ignored in a storm of entrepreneurial sci-fi-tech enthusiasm, almost 60% of respondents who received visual access to their own faces during videophonic calls specifically used the terms untrustworthy, unlikable, or hard to like in describing their own visage’s appearance, with a phenomenally ominous 71 % of senior-citizen respondents specifically comparing their video-faces to that of Richard Nixon during the Nixon-Kennedy debates of B.S. 1960.
It also means you have to stop what you're doing, sit down and talk to your screen. I like being able to stand up, or go grab something more than a meter away, take a walk or make coffee while I talk to someone. If I vanish from sight, the other parties on the video call don't know if I'm still listening. Heck, even if you can see the person, you don't know if their sound is still working properly, so there's more "can you still hear me?" and "sorry, you cut out for a moment there, can you repeat yourself" sorts of interactions as well.
Video's a pretty bad substitute for real world face-to-face.
Searchable conversation history is certainly extremely useful. But today, that's at the cost of needing to regularly go back and redo text discussions from 5 or 15 minutes ago because it becomes clear that we initially hadn't understood each other at all.
So I dream of a Black Mirror style future with an indexed video archive of what my eyes had seen.
In theory. But when you are dealing with a lot of "anti-social" people who have a hard time communicating verbally, or integrating socially, it usually has the opposite affect, ime.
A Dev I work with has to commute through 50% of Germany every week. He only sees his kids on the weekend.
There are many factors at play in such decisions. "Having a choice" is something you do not always have depending on personal circumstances.
We would be well served by demonstrating compassion for others -- it's not like a majority of people can simply jump on their fixie with their Manhattan Portage bag and just enjoy a 5 minute ride to a DUMBO loft office.
And managers are afraid they'll appear superfluous when they can't walk around disturbing people all day.
Like many many engineers I was attracted to the role because I would work with other people like me, geeks and nerds (I realise there's a potential side critique about cultural homogeneity here). Being in the office is fun because I can make relatively obscure Cosmere or boardgame references and folk get them (not everyone but in normal society no one does). In that way it's relaxing, even if it's still a workplace.
I tend to work two days a week from home and commute a bit under two hours one way the other days. I agree with the above quote from the article. Usually, the complexity of my team's tasks are at a level where some face to face early in the week and some remote screen share + video call later in the week are sufficient. We are currently working through a complex bug and I have came into the office on the days I'd normally be remote. It helped. The connectivity of interpersonal relationships is easier to build in person, and so I subscribe to the notion that a minimal amount of time in the office is a good thing if you need a team that works great together. I feel that time varies on how well the team is bonded. With my last team, a day or two a week face to face would be good. With my brand new team where we are still forming and norming, more days all together makes sense.
Why do we work in firms rather than as independent contractors making contracts with each other?
Why do we gather in rooms every day instead of working independently and emailing each other with low frequency asynchronous requests?
I don't really understand firms, to be honest...
I suspect it has way more to do with instinctual tribalism than any other rationalization.
However, the "firm" structure creates lots of efficiencies. Individual contracts are costly to enforce and having one type of contract (the employee contract) allows hiring to scale a lot better. Employees (and usually not contractors) are exclusive to an employer which is also desirable for employers. Employees also get benefits, which a lot of people like.
There's also efficiencies gained by people working in the same room. Any type of creative work for example can benefit greatly from a quick in-person chat, or just bouncing a quick idea off of your colleagues. This is even true for some developers (myself included). Some types of work truly rely on communication between colleagues, and that would be really hindered by latency issues due to low frequency async communication. Coordination is also very important and much harder to do with async communication.
Tribalism is an interesting lens, and maybe it started out that way, but the firm is certainly valuable.
And the subtle near-mystical benefits to being in the same room, the "high bandwidth communication" of "body language" and all those things, all seem to me to have a great deal to do with the ancient structure of the primate dominance hierarchy!
You notice when you bring up the topic of remote work in an organization that isn't fully remote already (i.e., isn't operated by introverted shamanic nomads) that it's totally not a decision about rational economic benefits. It seems to be much more about family, tribe, smelling each other's sweat, etc.
Benefit calculations are tricky because you could find just as many benefits to working separately, although it might lead to you to think of work in a different way, a less tribal way.
You don't argue that professors, poets, and carpenters need to huddle up in a boiler room to get their work done, because we know that some modes of working more require privacy, relaxation, autonomy, etc.
I think tribalism is really powerful and like a core force in our evolutionary heritage. As it happens, I personally tend to inhabit the fringes of the tribe, and I do better work in a solitary or remote situation.
Aside from them most of the people I asked about this would either want to have a very short(20 minutes max.) commute, or work from home, since it's usually the most comfortable environment for them.
Nearly everybody I know who spends at least two hours daily in traffic would love to change that in any way possible - including switching to remote work.
This is pathetic. They have hell at home and instead of fixing it, they bring it to the office. My home life is awesome and I'd rather spend more time at home than in office full of miserable people. Sadly they are the loudest one and their moans are music to the ears of managers who are control freaks. Thankfully I decided never again work for a company that doesn't allow remote.
But regarding people who might want to avoid being home, that is a whole different problem that needs solving. Wanting escape should not be an argument for commuting.
Probably a job that is extremely well paid for knowledge work in technology and where workers are highly sought after so employers provide lots of perks.
I'm sure plenty of people already figured out the answer to the above questions. It's just not something that I've seen discussed often.
Hundreds of years ago, Mozart was said to have traveled more than the vast majority of his contemporaries. Today, the average person travels more miles than Mozart every day! To sit in a chair.
Think of the waste in terms of energy. Not only has there been an explosion in population, but each person is expending more energy than ever on these things. And why?
Because economics. For one, suburban sprawl happens because commercial areas get gentrified so people choose to live farther from their job. UBI would fix a lot of this, allowing local workers to live and work near their job.
In my dynamic (with young kids), any attempts to work later than 20 min past the predetermined closing time are often met with baby/kids being "let loose" on Dad.
For the family, it's a plus. But sometimes ... holy shit I have stuff I need to finish.
Finally, it is SO convenient for spouses when their partner works from home. SO convenient. E.g. child care/babysitters fall through guess who gets to not get work done.
Overall, the ROI is pretty positive ... but I've been doing this a long time, and I do miss the office.
Early on in my WFH career I had to make it VERY clear to my family (and friends) that when I'm working they need to consider it as being NO DIFFERENT from me being 30 minutes away in an office.
I refuse to structure any part of our life around the belief that I am more available or more flexible.
In practice, yes, I am more available and more flexible. So occasionally, I can do things like run an errand in the middle of the day. But my close group of family/friends understands that this is an exception to the rule. In general, they should consider my work as being no different from theirs.
So say you're based in NYC, but you find a great hire who's 2 hours drive away. You could just add that person to your "subscription", flick them over an access card, and they can swipe themselves into the 'Desk as a Service' office just next door to their local Walmart. You know they've got a desk that meets all the zany OHS requirements, insurance is taken care of, internet/power are business grade, and if they fancy moving then that's no problem either.
Personally, I hate the idea of working from home. I don't want anything work related in my house, and I like having face-to-face interactions with people rather than just being by myself 24/7. Working in a shared office addresses all that + makes the potential compliance/OHS/insurance issues of having someone work from home very easy to tick off.
All jokes aside, as someone who loves remote and work from home to avoid Bangalore traffic, sometimes, not always it is good to meet some face to face.
Sure this can be taken to an extreme too. My last job we had a manager who insisted on doing everything face to face which meant we were stuck in office beyond 8 hours. Then people started adjusting their schedule to accommodate those meetings, then there was barely 3 hours of actual work, 2 hours of prep and 3 hours of "face to face" meetings.
Working alone (possibly remotely) is probably more optimal for accomplishing things that can be done without casual information sharing, like implementing a solution to a well defined problem in a well understood domain. You can create a forum-like experience through communication technologies, but it is often suboptimal for the kind of interactions required vs in person communication.
I don't know of many professional or technical jobs that don't involve both modes of operation, and we should be investing in systems and technologies that support both.
However, even if communication tech improves enough to nullify the difference in value with meeting in person, people will want to work in person with others, because they are people.
And even if transit tech nullifies the inconvenience of an office commute, people will still need solitary work space and time, because they are people.
Anecdotal, but I doubt I'm the only one where this is true, the mentality of "if we all can't do it no one can".
There is much, much more to your job than what's in the job description. For starters, you have to make your manager happy, so he can feel justified in continuing to pay you. Showing up at the office on time -- early in the morning -- is a form of virtue signalling. It's used as a proxy for self-discipline and reliability -- traits valued in an employee.
Yeah, yeah, I know. "My deliverables should be the only proxy I need; as long as I'm getting my work done I should be able to work from anywhere." It's one of those subtle psychological things. It takes a long history -- longer than the average Hackernews's career at any one place -- of deliverables shipped on time and under budget before the manager will feel confident you're reliable enough to deliver guaranteed value when called upon to do so. Showing up on time increases their confidence in you and decreases the chance that they will wake up one morning and decide you no longer merit that generous tech-bubble paycheck.
So cowboy up, set your alarm for 6 AM, and get to work early.
Because some can't work remotely (I'm one of those people).
Because you work in a regulated industry and no content can transit through internet.
Because the company think that it's easier to have cooperation when your colleagues are within walking distances
Because the offices are in area with efficient public transportation and available housing
Because it is harder to express yourself well in writing, compared to face-to-face
In Chicago, electric train service used to run a lot faster. Not just within the city, but also within the greater Chicagoland area. Way back when, the service that's been supplanted by the Metra diesel trains used to be able to punch well above 60 MPH. And with smaller trains, it could get to that more rapidly and provide more frequent service.
And the Green Line used to move. Lack of maintenance had it down to a fast crawl, in places, I understand, although some much-belated renovation may have improved that somewhat -- I'm not up-to-date.
Bay Area housing prices are simply ridiculous. If the region is going to keep growing (so far, no stopping it), then put housing further out while providing fast access to the core(s).
That would move a lot more people, and solve a lot more problems, than an LA - Frisco Hyperloop.
But, we don't have real urban, metropolitan planning, here. And, "taxes are bad".
So, we sit in our cars, and pay half our earnings to the ponzi scheme and rentiers.
P.S. Once a robot can do everything currently requiring physical presence, your tele-presence, where still needed, is going to become a fungible commodity; no job security, there.
P.P.S. Another major approach is a denser core. But NIMBY. A NYMBY I'm not entirely unsympathetic towards. If you don't solve noise and pollution, among other things, forgetaboutit. In my case, I would have been happy closer in in an apartment/condo, but the prospect of dealing with ever-noisier neighbors ruled that out. And wiping black "dust" (vehicle emissions soot, mostly) from my window sills. After years of allergies and whatnot, that stuff will kill you; more articles on this, every year.
- spins around in chair, interrupts and asks coworker a question, workshops ideas for 15 minutes, comes up with solution, makes a meeting
- boss comes over and tells workers there's some issue going on he's going to go deal with and he'll be available via cell only
- when SCRUM ends, conversation continues in person, things get decided
- walk into boss's office and make tentative strategy plans
- discuss current issues, decide to rework something, meet with another team, make plans, start working on it
Sometimes you can just walk around, bug people, and get shit done. It's very efficient.
But all of these things also involve communication which isn't relayed to remote workers. People either forget you, or including you in the conversation is a hassle, so they don't. You feel like the unwanted stepchild, constantly pinging people to get some kind of feedback and never seeming to reach them until much later. It's really inefficent.
There's no excuse for piss-poor planning and communication. It's not that hard to send an email and get it on record.
Also "Walking around, bugging people, and getting shit done" may be very effective _for you_. Meanwhile you've blazed a path of interruption and disruption amongst your colleagues in your wake.
This might increase the efficiency of the person walking around, and decrease the efficiency of the people getting bugged. I wouldn't say it's a net win for the company.
> But all of these things also involve communication which isn't relayed to remote workers. People either forget you, or including you in the conversation is a hassle, so they don't. You feel like the unwanted stepchild, constantly pinging people to get some kind of feedback and never seeming to reach them until much later. It's really inefficent.
Yes, working remotely with a team that has an office is awful. Working in a fully remote team is much easier, more pleasant, and more efficient.
> spins around in chair, interrupts and asks coworker a question, workshops ideas for 15 minutes, comes up with solution, makes a meeting
Slack please. Don't interrupt me.
> boss comes over and tells workers there's some issue going on he's going to go deal with and he'll be available via cell only
I don't care. If I need the boss, I'll text/Slack/email him/her. I'm not a child -- I know what I need to do. If it's an emergency, obviously I'll know how to reach him/her.
> when SCRUM ends, conversation continues in person, things get decided
What conversation needs continuing? What actually needs deciding? Is there no leadership?
> walk into boss's office and make tentative strategy plans
holy crap. Does anything actually get DONE in this office? A whole lot of deciding and planing and interruptions and workshopping.
> discuss current issues, decide to rework something, meet with another team, make plans, start working on it
Sounds like your company lacks vision and leadership. It seems like a disorganized mess where there's no clear product vision, no clear leadership and horrible communication that requires a series of interrupting, impromptu meetings.
You described a day where code probably gets written for all of one hour -- the rest of the time is spent just feeling good about how much stuff you've gotten done. Meanwhile -- what have you actually shipped?
My comment isn't about remote vs. non-remote -- it's just pointing out that this "getting shit done" depiction is pretty much describes the sixth circle of hell.
When you work with 20 teams and product lines all intermingle and you don't have an unlimited amount of time, money, or "vision", shit needs to be re-evaluated from time to time, and waiting two weeks for the scrum to end is too slow.
I'm sure you're very happy to remain undisturbed, Mr. Important, but the rest of us have blockers we need addressing, so jump on a hangout for five minutes so we can get some shit done.
Some have alluded to it in posts here but unless you've worked from home for an extended period of time you can't really understand how strong of an impact isolation from your peers really can have.
I believe that everyone's individual need for human interaction varies but we all require it on some level. We take for granted just how much of our social requirements are met by being in an office. Face-to-Face interactions aren't important because they're a better mechanism for developing product... They're important for the individual, because without them your "social brain" will effectively atrophy. Interacting with people on a daily basis is the only way to stay sharp when it comes to social interaction. Slack can't replace that, unfortunately.
It'll be interesting for me coming up when I start a new job in a little over a week where I'm remote in a different city for three of the days, and then taking the hour and a half Amtrak down to where the company is based. When talking to the head of the group, the first thing I said is that I wouldn't be moving to where their office is. He was totally fine with that.
I like working on things from random places, but I'm also more than familiar working in an office with others. We'll see how this goes.
I think remote work will increase just because society will realize how much energy it wastes commuting. A 15 mile commute both ways uses the equivalent of the energy used by a house in day.
If we get fusion then things will change, but for now it seems like this is one of the best untapped was to conserve energy.
I anticipate that ways for the boss to watch remote workers like always on video conferencing or collaborative workspaces will also become more popular.
I think some psychologists should do some research on the subject , remote work is only bound to become more common.
Also because the state and government doesn't plan for such things, so the result is large cities with many offices and spread out houses.
I guess gas money could be saved on a very large scale if the government would try to encourage citizens to switch houses... maybe with some sort of tax break or something...
PRO
Work from anywhere with internet: In the last 45 days, I have worked from the Caribbean, from Spain, and from Ireland. Granted, these travel experiences aren't full vacations (and in fact sometimes were stressful when internet quality was not tops), but they sure beat my previous "open office" bullpen.
Work when inspiration strikes: Sometimes my brain won't shut up the useless stuff, and other times it wants to really drive a useful project. When it's a good time, I usually can choose to work uninterrupted and make great progress. When it's not a good time, I can just go do chores around the house or go enjoy the weather.
Answer fewer tech questions for other employees: If you're within earshot, less technical people will ask for help the instant they think they need it. But if it takes more effort for them to reach you, they will work a little harder to solve their own problem. Most of the time, they solve the problem (or realize there was no problem -- just a moment of confusion). This saves me SO much time and occasional frustration.
Not commute: This one is kind of obvious, but not having to commute saves 1-2 hours a day. That's time for gym, coffee, reading news, etc. It's also so much less stress. When I drove in traffic to and from work, I would often arrive very frustrated. When I moved to Europe and had the luxury of riding a train(s) to work, life was better... except when trains would break or a surge of travelers would result in no seats available.
CON
Communication can be more difficult: I have found voice calls to be essential, at least compared to just txt and email. Text messages were the worst and most likely to result in annoyance or confusion. Emails are a bit better, but reply-hell is real. You definitely have to work a bit to find the right tools and methods for each of the people you need to work with; but once found, it works almost as good as face to face.
Work is _always_ there: This has been the hardest for me. I always have more work to do than I can do, and now I can work any minute that someone else (partner) doesn't need me. This can get out of control if you're not careful. Some people are strict and disciplined about home working, but I like to stay flexible. Still, one must set some limits or reminders of reasonable behavior/expectations.
Fewer jobs: Since most companies don't go for remote work, you have to decide what's more important - freedom, or a particular job. I choose freedom, and at this point I don't think I'll ever go back. Once you've tasted freedom, and once you've proven to yourself that you can work (well) alone and unsupervised, the thought of being back in a noisy office with people passing by behind you, potentially judging you if they don't see you with a code window open 99% of the time, is just untenable.
If I worked remotely, I would do that 5 hour stint, make breakfast and play with the kids, then do a gym / coffee shop routine for 3 or so more hours to finish up work for the day.
But in practice, it's the other way around. Capital is lazy and concentrates in places like SV. People have to commute or even migrate to get better working conditions.
It's like a side gig where your compensation is you don't get bent over for rent, get the freedom that comes with owning a home and no longer have to put up with the downsides of living in an apartment.
simple, naive answer, that ignores the context of the article:
because to a very close approximation 0% of people on this planet work in an office at all, let alone an office where this is genuinely possible.
Selling insurance: not required. Customer service for the electrical company: nope. Most of that is on the phone. Logistics for a trucking company: also phone/computer based, no face to face (or rarely.) Medical claims processing -- never face to face Coordinating cable TV installation appointments: all phone or online based
If you think about it almost ALL jobs can be done remotely. I agree that most jobs still require it, but that isn't because of the nature of the job, but the lack of vision from those particular industries. Most businesses seem to operate under 19th century ideals.
I realize not everyone wants or can work from home; but I would advocate for a decentralized workplace -- remote working with perhaps small satellite offices scattered around the world -- offices that can simply pop-up at WeWork/etc. As employees in the area need/want.
Obviously a hardware company like Apple actually needs a physical space for people to build things. Same for Boeing, Tesla, etc.
But Facebook? Farmers Insurance? They don't sell anything physical.
If your job can be done remotely, your job can be done by a computer in 90% of the cases. Good luck fighting for those jobs in the future (especially when they get sent overseas for 1/5th the cost).
It is not just 'cargo-cult' or 'enterprise-envy'. I think it goes deeper. My current feeling is that middle management is something that is naturally lurking in the wings, and expresses itself the moment the overhead can be carried. Caricatured: Bottom up there's people looking for a way to escape 'working at the coalface', and start the innate pecking order/ hierarchy battles. Top down there is the desire of the owner to create some distance, and in many cases also the latent idea that if some proficiencies could be isolated into a single specialist, the remaining 'resources' could be sourced cheaper. It self reinforces since as 'overhead' the middle management layer crates make-work to assert its existence. Furthermore, it asserts the 'company as a value funnel', since it is a model that disemancipates each individual making sure they can't easily venture out on their own.
So the middle management pattern could be an expression waiting to happen as a result of natural forces, not as a result of direct 'needs' or 'efficiency' in value creation in its own right, but just for the sake of 'enterprise creation' itself.
>Conversations around whiteboards between stakeholders creates value.
Why ? Are whiteboards magic ?
>Pair programming makes for lower defects and more reliable scheduling
Putting aside the fact that the benefits of pair programming as less consensual than what you seem to suggest, it can be done much more conveniently in a remote setup with a screenshare and a headset than by sharing a desk.
>Software is a design delivery operation.
So ?
>There was recent article on MS office space redesign to create more value.
Here we have the business case reference, always good to include one. The substantial remark is that once again this doesn't prove anything, the first reason being that "value" is extremely vague.
>Productivity is not per-keystroke
The art of looking like you are siding with the people you want to control while it is actually the opposite. If we go the bottom of the reasoning : value is not per keystroke, we therefore need to put employees in a room because their true value must be monitored to be appreciated. "Please understand, I really want to be able to appreciate your true value". Sounds a bit hypocrite to me.
>Personal productivity is almost a misnomer
One more slogan.
>I have been paid extra to kill projects that never should have started.
While I am the first to advocate careful planning and writing code last, as an entrepreneur, I consider it a crime to sabotage projects, because anyone who has ever created something, or started a project or a venture understands that creativity is almost Holy. Beyond the technical deliverables, projects trigger group (and market) dynamics and institutional learning that may be hard to reproduce later in time. For this reason, doers do not sabotage or kill projects, they rectify them. Sure there can be pure follies that need to be stopped ASAP to stop diverting valuable resources of the company, but my overall impression is that you have a more liberal approach to assessing what must be killed.
I respect arguments from both sides, but this comment is really representative of the crap filling most companies.
Anecdotally, for the amount of problems I have seen them solve in short order. Yes. They force an idea in the mind to become concrete and logically digestible to other members of the party. If you can't draw it in a manner that other people understand, you don't understand the idea well enough yourself. It is also free flowing. Ideas can be added to and removed quickly with an interface that almost all humans have been taught to use since a young age. It only contains 3 parts. The pen, the board, and the eraser. No software with far too many options to understand. No weird bugs that crash in the middle of a presentation. Pictographs can transcend language barriers. Software sellers will never create such a simple product, there is little value added reason to.
So yea, if not magical, far better than its competition in portraying ideas.
You make a very valid point, what I was highlighting is that good communication can be achieved without whiteboards too.
I understand your underlying argument that whiteboards may constitute the best technology, but I also think there is a tacit convention at play here. People tacitly agree to communicate in a way that make whiteboards work. For there are many effective and fluid ways to iterate on ideas that do not involve live drawings or complex tech.
I know it for a fact as drawing my thoughts on a whiteboard has always been counter-natural to me. I can do it but I wouldn't say that it is necessary for good communication. It is just a communication choice that people make.
Everything that can be drawn clearly can also be written clearly (analogies, bullet point lists for flows, etc...). Not to say that diagrams are never helpful, but it may be a stretch to assume that drawings and whiteboards have an almost essential role.
Let's eliminate some cases. I know some people work on entertainment software or short term content. Others work in departments "against management" for take home pay. I never care about those projects or those people working on them. My words do not apply there.
Interesting hardware is not virtual but involves complex supply chains. The same goes for productivity software interacting with the world already in motion. New training often costs more than new tools. DC folks making NASD broker registration reality are essential personnel in tight supply chain relationships. Any error on a Congressional Report can tumble decision makers into felonies or disrupt global commodity markets. Same goes for folks writing device drivers or porting libraries to new hardware. None of this is any app buried in app stores or Office Space TPS reports.
In such greenfield or release cycle projects the right team size and composition will get there first, avoid mistakes, clean up markets later cheapest or occupy profitable niches longest.
Software projects concern progress and reach and thus "pass the bus test." Nature is not kind to the shy. Individual problem are just problems. Anybody can consult from anywhere if they can make a living that way. Otherwise, nobody cares about homebodies. Never project socials problems or commute logistics as values or virtues. Skunkworks remains the model for focus and shared responsibility. Software is not the deliverable. Tools and answers are the deliverables.
Then somewhere along the way, some marketing guy came up with the spin, "It fosters communication!". Open office does indeed make people close in proximity, but it's not a necessity.
Found this: https://www.wired.com/1999/02/chiat-3
And as with anything else in life, we must weigh the options. Face to face can indeed be better than remote. It can also be worse, because some people just irritate others by their presence and little behaviors. But more significantly, some of us do work which requires a good amount of thought - uninterrupted, quiet thought. Shared offices make this more difficult (compared to a quiet home office).