Joel's rules strike me as a little more specific than necessary, but I can very much relate to his feelings. I have experienced devs "working from home" who disappear all day and hold up the whole team because we can't find them to ask a quick question. The point is that when you say you are on the clock - then you should be working. I personally wouldn't care so much about the exact specifics of your internet connection or whatever. But, if you tell me that you're working then I expect that you're actually at your computer working and not laying by the pool or playing video games.
It's equally easy to say that you'd just fire somebody who you did not trust to work at home with no rules. But, as with many things, it's easy to take this hard line approach with your imaginary company and theoretical employees - quite another thing in reality though. Some people are very productive but maybe not so disciplined. A few sensible rules and expectations can prevent problems.
The HR industry terms this "Employee Engagement." If I had to guess, Fog Creek has quite a few "disengaged" employees.
Good managers are nearly extinct species, whom you encounter once in a while in years. The remainder get to become managers by their political work and a results oriented work environment is something they will never build. Because if we were to measure progress by results, those managers will be the first to be fired.
>>As long as the goals are being met, management should allow their developers the freedom to choose their own work environment and hours
Their goals are very different than our goals. The goal of leaders is to produce results. The goal of management is to keep the wheels running, regardless of whether the running produces any results.
A good manager is automatically a leader.
Further, their goal is to encourage good work/life separation even when working from home. If you can't maintain that separation, it seems FogCreek would rather you clock it up to 'life' time than blur the lines. That's just good management - working with distraction is going to result in poor output. Goal oriented management in this scenario, particularly when this may not be a normal part of the workers routine, could result in stress and poor work. Far better that if you can't have a good work environment then you just take a break and increase your output when you get back.
Down the page they mention The burden is on you to show that you’re being productive. -- that just sounds outright authoritarian and demeaning. Strict policies calling people out as "do this ... or else" don't exactly engender trust.
I think they cover most of our complaints in the poorly worded Known availability and overlap with your team section.
Most places have three levels of "work from home." There's full speed "work from home" where you're getting more done because you're not distracted by office shenanigans. There's half speed "work from home" where you're not plowing through, but you're keeping up with all communications/chats and fully available if anybody needs you. Then there's fill-in-the-gap "work from home" where you're checking into work systems in the morning, getting some things done, going to an intermediate step in the middle [an appointment at the house, going to a doctor on the way to work at 11am, going to the DMV at 10:30am], then going into the office for the rest of the day.
I think they're saying all of the above is okay, just communicate what your availability will be up front (which seems to go against their other policies of "work in a nuclear fallout shelter away from all distractions and you better have no other responsibilities at the same time either — we own you").
I think this is hyperbole. They all basically boil down to: if you work from home, please work from home. And keep in touch.
I work from home. As a rule, the best-running projects are those with daily video meetings. The 2nd best involve phone calls. The worst involve emails.
Faces have enormous bandwidth. Voices a bit less. Email has bugger all for the things that matter.
If a company offered me the choice between working from home under the conditions listed for Fog Creek or not working from home at all, I'd choose the latter and consider option c) quitting to obtain employment with a company that recognizes I'm not in kindergarten anymore, and don't care to be treated like I am.
They pay us to make business problems go away. It just so happens that our tool for that is usually software.
A major insight of agile methods is to put the developers close to the coalface, because infrequent or indirect contact leads to the wrong thing being built.
I frequently find while working with customers that we have entirely different mental models of the project. And I only find that out because I am constantly asking them questions about their business.
Do they have a "if you work in the office, please work in the office" list of rules?
My experience has been that most people "working" in an office aren't working at all for the overwhelming majority of their day. But that's just office life and it's just the way it is. Marissa Mayer wants everyone in the office because she wants to set a "good" example: businesses like Yahoo absolutely depend upon vacuuming away the activities of people sitting in droll offices.
Perhaps "insane number" is wrong. I probably meant "insanely specific requirements."
The 1 wasn't even running to rector st this evening, so I couldn't get to work even if I wanted to.
For their sake I hope they take some of the sage advice offered in this thread from the numerous people who have run profitable businesses with multiple employees for several years.
1. Be able to communicate with your team.
2. Have a place where you can work, distraction free.
3. Get approval from your team lead. (This one barely counts, since the answer would never be no.)
From working remotely for the last year, I've found that basically any table is a fine remote work spot for me. Kitchen table, Starbucks, whatever. I have learned that I don't get appreciably distracted by ambience or even really by light conversation[1] (unless doing something particularly out-of-the-ordinary in terms of difficulty, in which case it's lock-the-doors time); if I did have concentration issues, don't you--y'know--think that I wouldn't do the things that triggered them. Because I'm an adult and I'm competent? The assumption that people aren't is why, to me, these edicts read as kind of wacky.
[1] - Hell, I'm getting a coworking space because I find that that ambience and that light social friction makes me better at what I do. =)
>Approval from your team lead. Basically, just tell someone well in advance if you’re going to be altering your work arrangement, temporarily or permanently.
seems counterproductive. Sometimes problems come up and you suddenly need to be at home tomorrow to meet the cable guy, who has committed to come between 6 AM and 9 PM, but will only be there for 15 minutes.
Whats the worst that could happen if one of the workers has a less than ideal setup while temporarily working remotely for a few days? Would it really affect company outcomes? If not, I think developer happiness would be improved by having a more laissez-faire attitude from management.