Ask HN: If you don't permit telecommuting, why?
11–20 of 148 posts
Re: Ask HN: If you don't permit telecommuting, why?
#12It is quite weird that we have all these up-votes (including my own) but no answers. I think that the real answer might be something quite embarrassing, and politically incorrect.
- We really don't know how to deal with the differences, and it is scary to try;
- There are some company process that we are afraid of changing to accommodate telecommuting;
- The risks and costs outweigh the benefits, or the benefits are fuzzy while the risks and costs are clear;
- etc
Re: Ask HN: If you don't permit telecommuting, why?
#13Re: Ask HN: If you don't permit telecommuting, why?
#14I run a fully remote company, and most of the objections I've heard from others we've found workaround for.
The biggest unsolved problem is whiteboarding - there is no good collaborative online whiteboarding solution that doesn't require a lot of expensive equipment to be deployed to everyone.
Re: Ask HN: If you don't permit telecommuting, why?
#15* Why does the person who does this job need to be on-site? Please be specific. Give me examples of things that can only be done if she were in the office.
Ad hoc meetings are 1000 times easier when everybody is in the office. Standup and other meetings are hindered by teleconferencing at best. Even with high quality video and audio, it is often much harder to hear the remote person, harder to collaborate (I can't just walk to a whiteboard and draw something up quickly and have them easily see it.)
Having them train a new hire or an intern is much harder. Furthermore, interns and new hires much prefer somebody being able to sit with them and collaborate. Sure, you can do screen sharing, but it's not the same at all.
One thing that makes our team 'special' is the culture of the team. We often do team building exercises (paintballing, curling, etc.), have optional happy hours, etc. and all of that is physically impossible without flying somebody out.
It is much harder for the remote person to get support from help-desk. If you are onsite, you walk down to one of a few different help desks and get help right away. If your hardware is faulty, you get a new laptop and are up and running within a few hours. This is not possible with somebody remote, and we've had major headaches dealing with this.
* Have you been in a position where you personally would be okay with an employee being a telecommuter, but a decision-maker deemed otherwise? How did you handle it?
No.
* How has the policy affected your company’s ability to attract candidates?
I think this one is pretty hard to answer. I'd assume many potential employees pass on even applying since we don't really support remote work. I don't think I can give a proper answer here, unfortunately. I can say that we're fine with this tradeoff. We haven't had any problem attracting talent in the past (paying boatloads of money helps.)
* Have you hired someone for an in-the-office job, and later given permission for the individual to work from home? What happened to make the change okay?
Yes, we allow this with extenuating circumstances. We've had team/org members get sick and prefer to work from home for a few months while they recover. We've had employees leave the country to be with their parents due to illness. Employees who wanted to work from home a majority of the time while their child is young, etc. Generally we're pretty okay with short term telecommuting, but we don't really offer full time (forever) telecommuting.
Note that team members regularly WFH for a week or two while visiting home (if they don't want to take vacation), and nobody cares if you WFH once a week or two.
* What would it take for the company to change the no-telecommuters policy, even if only for one specific position? For example, “If a rock star in my field applied for the job, we’d do anything to get him to say Yes – including letting him work remotely.” But there can be many other answers, and I’d very much like to hear yours.
If a known rock-star (guaranteed) applied, we'd let them work remotely. If we had trouble attracting the talent we needed, we'd let them work remotely.
Re: Ask HN: If you don't permit telecommuting, why?
#16Are there any success stories of early stage high growth startups that were started by a remote team? At least in the startup world, most people are concerned that you will miss that zeal and watercooler chat magic that is critical to early stage companies. I don't think anybody cares too much about your 1000th engineer being remote, the organizational DNA has already been set a long time ago.
Is there any real evidence showing how much this actually matters, or is it just Valley voodoo? I suppose that is partially tied up in the answer to your question.
> I don't think anybody cares too much about your 1000th engineer being remote, the organizational DNA has already been set a long time ago.
Yet hundreds of companies at this size seem to care shitloads about it.
Re: Ask HN: If you don't permit telecommuting, why?
#17Not exactly what you are asking for, but I'll throw it in here: I run a fully remote company, and most of the objections I've heard from others we've found workaround for. The biggest unsolved problem is whiteboarding - there is no good collaborative online whiteboarding solution that doesn't require a lot of expensive equipment to be deployed to everyone.
Re: Ask HN: If you don't permit telecommuting, why?
#18How many decision makers are willing to admit that they are subconsciously using "chair time" as a measure of productivity?
The solution is really to use communication tools like Slack and also put the focus on deliverables instead of "work units".
Re: Ask HN: If you don't permit telecommuting, why?
#19Re: Ask HN: If you don't permit telecommuting, why?
#20It is quite weird that we have all these up-votes (including my own) but no answers. I think that the real answer might be something quite embarrassing, and politically incorrect.
I'm curious what you think it might be. I would guess here but lack experience to guide my guess.