I believe that this approach creates a work environment that allows us to attract and retain great developers. The kind of developer that really likes to write software and has the maturity and discipline to manage their own time and decisions.

Some implementation notes:

1. We release a new version every two months, the continual releases keep everyone on track with constant customer feedback.

2. We all see and read the check-in diff's, absolutely the best way to know what someone is doing and how well they are doing it.

3. There are great developers outside of the traditional Valley/Boston/Austin areas and a telecommuting team lets you find them and hire them.

4. After about 6 months it becomes very clear who can handle the telecommuting setup and who can't.

I was by far the most productive employee in my group at the large bank I worked for previously. I outproduced others, even while taking the hardest problems -- and we had a pretty good metrics systems, so I wasn't just gaming it.

But when I asked if I could work from home when I'd decided to move, the answer was an emphatic, "No."

So, they'd rather lose their most-productive employee who also would've been far more productive at home and then have to hire a probably-inferior replacement?

Makes no sense at all, yet so many companies are like this.

I _am_ accounting for the absence of physical contact. My employees will have a desk VoIP phone connected to the company PBX, email, IM, and all the other stuff that is used for internal communication in companies where a bunch of folks are sat in offices and cubes but hardly ever bother to walk over to each other's positions as it is not really part of the workflow protocol. And these are employees, not subcontractors. I will manage them. I just won't be standing over their shoulder.

I don't see why that's such an impossibly lofty goal.

so i'd say it's more likely a case of valuing a different set of things.

This is the same bank that would email around escrow account information. These accounts sometimes had $295 million dollars in them, and they emailed this info with complete account information, wire instructions and routing numbers. No encryption. Regular e-mail.

Oh, the temptation.

But anyway, I am not sure what they valued. It certainly wasn't security or productivity.

You can say no and keep the house of cards up, but it's just adding tension to the employer-employee relationship with all the other staff.

I have yet to see a company that truly treats all employees equal. That would be the only setting where I'd agree with your concern.

I don't know that the difference has a name, but it's a difference.

I had a simple response to anybody who asked why I'm so rarely seen and why they don't get that privilege: As soon as you put in 50+ hours a week like I do and get up at 4am at least once every week to clean up the mess that you deployed...

That was my story, others may be different.

Innovations, especially those that seem to threaten owner/manager control seem often to evoke paranoid responses. Sometimes they have to be broken down gradually with positive experience over time. Good luck to the OP!

It's a limitation of the OS that is built into humans. This is what you get when you try to build a global economic system out of bright, talkative monkeys like me. It turns out that -- amazingly! -- this can be done, but we find it much easier if we employ hacks that leverage the features of our underlying monkey OS. And -- even more amazingly! -- it turns out that we can go even farther: Using our most advanced mental and physical tools, we can do a pretty good emulation of disembodied brains sitting in the nth dimension. But the abstraction leaks. Especially when we have to interact with other people who haven't been fully schooled in the art of communicating with ghosts.

If dolphins ran the world, corporate boardrooms would be full of water. But monkeys run the world, so:

- Businesses are run as hierarchies, because the monkey OS is designed to manage bands of around ten or fifteen individuals. Beyond that, it operates in terms of alliances ("this platoon is allied with that platoon") and rivalries ("our platoon is doing its job, but that one isn't"; "our platoon is falling behind and will be targeted for cutbacks, so work hard and watch your back"; "let's all get together with Platoon Three to kick Platoon Four's obnoxious butt").

- Your status in the business world is judged based on the size of the conference room that you need to hold a physical gathering of your team members, and on the size of the contiguous physical territory that your team occupies and patrols on a daily basis. If you sit alone at your desk with the speakerphone on and claim to be conducting a meeting with fifteen colleagues, people will subconsciously think of you as a psychotic, or (at best) as a spooky witch doctor who channels the spirit world.

- There's a tendency to defer to people with grey hair, and/or people with lots of followers or lots of stuff that has taken time to accumulate, like corner offices or expensive desks.

- Talk is cheap. Many people will say they're your ally, but when a fight arrives they will not be there, or they'll discover some really interesting thing going on atop a nearby tree, or they'll hang back and not really fight very hard. You need to motivate them by really befriending them -- talking about their kids or their pets or their hobbies, bringing them little gifts. And by physically surrounding them with other friendly allies, such that they cannot easily flee without losing face. And by keeping them close enough to be able to slap them upside the head when they seem to be shirking.

- To really convince someone -- to really communicate at the highest level -- you need to be standing close enough that you could, in theory, pick fleas off of them.

Unfortunately, though humans are becoming better and better at understanding all this stuff and transcending it when necessary [1], we're never going to completely eliminate these tendencies. Unless the lizards rise up, overthrow us, and take back the planet. At which point they will have complaints of their own. ("Dear Gator News: How come companies always insist on holding meetings on rocks in the bright sunlight? I'm much more productive in my moonlit office, where I can sit on my dual 27-inch space heaters.")

---

[1] Such as: When trying to write software, which is an act so unnatural to us monkeys that only some of us can do it at all, and many of us are doing it wrong. And it requires all kinds of mental tricks and energy and focus just to manage that much.

I think that getting to the psychology of the problem as you are attempting (or succeeding) is a very worthy task that lots of people need to be working on.

I'm no water vapor ignoring tree-hugger, but the inefficiency of our current work system where people heat and maintain homes that are empty for 12 hours a day, go to office buildings that are empty for 12 hours a day, using a car that they use for two hours a day, to do work that could be done at home, is insanity.

Why do we tolerate this as companies or as employees? We can seriously look for solutions, or we can wax cynically about "the man". One path leads forward, to a solution.

If your hypothesis is correct, there are compromises we can do, to satisfy the inner-ape, while gaining some efficiency.

- We can remove people's personal effects from their work areas, so multiple people can work in that cube. On Monday and Tuesday, it a marketing guy. On Wednesday and Thursday, it's an engineer. On Friday and Saturday, it's an accountant. Let groups that never interact anyway, REALLY not interact, and as a bonus, you reduce your necessary office space by 2/3rds while still maintaining ape bonding time for two days a week. The other three days of work, people work at home, freeing up our highways by 2/3rds as well. Actually, we free up our highways by 3/5ths (math left as exercise for the reader) because now we have staggered our weekends a bit. Nobody works on Sundays still, but accountants work on Saturdays.

Would there be tons of coordination hassles, with accountants needing to talk to engineers about their annual budgets? No, not really. Because our whole premise here, is that none of this face time is actually needed from a business standpoint. Internet and telephone would be just fine. It's needed at a deeper level, among team-mates and up/down hierarchies, but it's not needed from one tribe to another.

The accountant tribe and the engineer tribe will never form an alliance, they are evolutionary enemies. Why force them to live in the same jungle?

One: Glad you liked the writing.

Two: Please do not think like this:

The accountant tribe and the engineer tribe will never form an alliance, they are evolutionary enemies.

You need to refactor those tribes. Because, in fact, every engineer should know something about accounting. One of the things I regret is that nobody in my youth ever found a way to make accounting seem compelling enough that I was convinced to learn it. It turns out, though, that modern economic life is a big game played according to complicated rules, and accountants are the referees.

Most engineering decisions cannot be made without an accountant. If money were no object we could solve many website scaling problems by buying one server for every anticipated visitor -- or, alternatively, by only allowing one visitor at a time into our sites. (Let them stand in line!) These are not silly ideas: People used to have to stand in line at major universities to use scientific calculators, but now we've made them cheap enough that we can just give one to every math student. The thing which makes many obvious solutions silly is: They cost too much, or they don't make enough money. And to answer the questions "how much is too much? how much is enough?" requires accountants.

Finally, please don't call this thing I've just written "a hypothesis". That makes me wince. I'm having fun with the metaphor, but it would be a mistake to reify it:

http://en.wikipedia.org/wiki/Reification_(fallacy)

The metaphor is fun because I really am related to monkeys (well, chimps, technically), and because many human behaviors really do make sense in chimp terms as well, and because it's quite possible that this is not entirely a coincidence, or a case of convergent evolution. But let's not go too far. It is only a metaphor. I'm built out of chimp parts, but I'm also built out of distinctly human parts.

For example, it would be bad to argue like this: Early humans lived as free-ranging nomads, so a better office design would be one that forces us to live like free-ranging nomads. That idea has been tried. And it turns out that one of the hacks that make the modern world possible is personal collections of artifacts: piles of papers (with the most relevant ones on top) and post-it notes to cue your memory, photos of your family to regulate your mood, egg timers to remind you to take breaks, vastly complex, expensive, and personalized suites of hardware and software to help you write code, the custom-adjusted chair that keeps your back in working order, etc. In other words: Having your own office makes you more productive.

No, I'm not saying that people that have personal effects in their cubes are all eminently satisfied; the point is that they would be even less satisfied if they were crammed into even smaller and yet _more_ generic spaces, or in spaces of which they could not claim even a provisional kind of ownership and which did not have any qualities of (semi)permanence.

I've had several jobs where the business owners didn't really want to spend money or time setting up any kind of meaningful barriers, even something so rudimentary and otherwise disheartening as a cube farm. Everybody basically got to sit in a large, contended, noisy and alienating open space at some kind of rickety, smallish plastic table. It was not feasible to define one's "space" in such a setting. Everyone felt like a temp. I don't think it helped anyone's morale, ability to concentrate, or productivity. It's a terrible idea; "open spaces" do not mean "open companies," to paraphase Joel Spolsky's biting criticism of open-area interior design thought in corporate circles.

In the jobs in which I and almost everyone I know has had, there is a clear and identifiable positive correlation between the amount of privacy and personal space in which they got to tailor their work environment to their preferences and the overall investment they felt in the company, its culture, and of course, the work. While, of course, environmental attributes cannot smooth over a crappy place to work, they can make an enormous difference in the level of psychological investment an employee has in a place that is -- by all other metrics -- decent.

I think the one exception to this may be in that I definitely think there is a market out there for creating workday "hubs" for freelancers and WFH employees to get away from the house (and small children, if they have them) and other environmental obstacles and show up with their laptop and set up shop. It could be something as simple as a glorified coffee shop whose table arrangements and interior design lends itself better to that than the average one. Make data ports and power abundantly accessible and you've got a winner. (Of course, you've somehow got to persuade these people to keep buying something all day, which is the problem coffee shops typically run into with students, freelancers and other people who spend all day there with their laptops. Perhaps there is an opportunity to charge a decent membership fee for a cool, happening freelancers' "club" of this sort. I'd pay $100/mo to be able to go somewhere close-by and ambiently pleasant with my laptop and partake of great bandwidth, numerous power and data ports (then I could bring a little SIP phone), and coffee and other beverages on tap or heavily discounted.)

This is a compromise between the insanity of commuting, from a business standpoint, and the necessity of commuting , from a tribal and social standpoint. As is the case with compromises, it's not going to be up to your idea of perfect, but what it allows, is, with the sacrifice of your personal items for two days a week, you still get your tribal/social time with your team, bosses, and subordinates while at the same time, freeing our society of much of the inefficiency of the current system.

@fish, if you're uncomfortable with your explanation of why we insist on driving to office buildings in an age when it's not necessary, than fine. But it doesn't matter. The fact is, we are, and it's probably for reasons just as mysterious and ingrained into our genes as your idea. So, that's all we need to know. We apparently can't beat it, so we must adapt to it, rather than bemoaning the state of things, which you were not doing, which is why I liked your piece. Instead, we can implement a hack like this to allow us to have some of our cake, and eat some of it too.

But I guess those two days you'd spend in the office would have to be largely in meetings and other things that capitalise on the "social" opportunity, with the idea that you'd be focusing purely on actual implementation (or whatever the work you do is) the rest of the time. Is that realistic from a scheduling perspective? Seems like corporate life always brings a steady composition of both.

They have a Firefox extension, Stylish, which lets you apply custom user styles to sites, to override the native CSS if it's not to your liking. Just like Greasemonkey for Firefox.

I found it after becoming immensely frustrated with a site that had inexplicably decided to invert the colors for a:link and a:visited.

This isn't a matter of trust, it's a matter of motivation.

It can be something squishy like, "Let me take a look at what Bob's checked in so far this week", or something more quantifiable, like, "Bob has closed n tickets today".

[Even if you don't have a hard number of how many tickets someone should close in a day or week, you can generally eyeball it and if there's a discrepancy, look at the descriptions to see how hard the problems were].

It's best to make this as transparent as possible to all members of a given team, and provide a system of rapid feedback and especially fast positive feedback for all progress.

Try and keep communication focused on whatever channel everyone actually likes using. If you're using a wiki, trac, and basecamp to keep track of overlapping items, quickly ditch whichever ones nobody actually uses.

If you can keep everybody motivated, communicative, and measurably productive, then you will actually be far better off than large traditional companies that rely on the ass-in-chair visibility metric to determine whether "work" is working.

I can honestly confirm that my productivity has decreased by more than 50%. One part of it is because of the wasted time in getting to the office and back. Another bigger part is because programmers work in an open space plan. Some other parts would be office politics and so on...

Working in a home office was so much better than i often ended up working 16 hours a day prior to a project deadline and not mind(i used to enjoy what i do).

We used to communicate all the time via IM, via email, and via skype. And of course make full use of collaboration tools. Also, me being in a different time zone helped the process a lot.

So yeah, some people will take advantage of this situation. But then again, bad people will try to take advantage of any situation. It is up to you to recognize those people and stay away from them.

Hopefully I'll find other ways to make up for the loss. :)

But there are a number of critical issues to consider.

The physical organisation of a workspace is a function of communication. Place those people who communicate a lot physically together because informal conversation is a lot cheaper than formal conversation.

When you are writing software you therefore have to have the specifier and the coder co-located. Open Source projects work very well because (in the vast majority of cases) they are copying existing software. So sitting at home working on a clone of Microsoft Word - the specifier (a copy of Microsoft Word) is sitting next to the coder.

When writing original software where the specification/product development is the core task this will be much harder - it may be impossible unless your specifier is an expert business architect, software architect and designer and can produce build-able specs and your team are capable of reading and implementing them on sight.

You must also choose your toolset correctly to generate a high volume of informal communication, so: * central SVN * centralised mailing list (no point-to-point e-mails) * continuous build with statuses

Essentially on the software development side the complete open source software development stack is optimised for this stuff, so its a doddle - your work has an observable daily heartbeat. For other sorts of work (say sales, order fulfilment, HR, finance, etc, etc) it is much harder because the core stack doesn't exist - you will have to create it.

The final thing you will have to do is be rigorous on formal comms. You will need to have an all hands call every working day. Sometimes 5 minutes, sometimes 35 minutes. You will need to organise face-to-face meetings regularly, Xmas dinners, launch parties, drinks and stuff.

It can be very effective at reducing costs but it is a considerable management challenge and you need to think of it as such. If you adopt a "hey we don't need no steenkin management bullshit, we're way tool techies, hey!" you're probably doomed anyway.

My concern isn't so much whether these things are qualitatively equal to the team-building experiences of being stuck in a room(s) together as whether it can work, in practise as well as in principle.

What I wonder is whether this system will somehow fail to produce the results I need despite that.

Not everyone may want to work from home though.

Campfire + VOIP works well to manage everything.

We all run on a central network using VPN but we're slowly starting to use more external services - and I hope we can ditch the VPN for most stuff in a few months - using Google Apps, Github and some proprietary web apps.

It gives more time to work as you're not commuting and if you have a young family it means you get to see the kids more.

While, admittedly, I've met some people that consciously or unconsciously value the social and possibly collaborative aspects of working in an office with others, they tend to be the kind that just get their social needs fulfilled at work without doing a whole lot of actual work. There are some exceptions in passionate people who are also extroverted and aware of the extrinsic dimensions of what they do, but they are not common enough to be statistically meaningful in my experience.

Can you elaborate more on what kind of person you think wouldn't want to work from home? I've hardly met anyone who wouldn't.

Whether that's feasible or not you'll have to make sure that people know that their contributions are being noted and to stimulate frequent contact between your team members.

I've had a (small) office in Toronto (about 10 people) and we worked from home as well for a while, it was quite interesting to see some of the best performers in the office environment turn into absolute sloths when given the freedom and vice versa.

Can you elaborate more on the people that were good performers in an office environment and turned to sloths at home? What sort of qualities or peculiarities of their character made them do that?

I think that the biggest part of it was the presence of temptations in the home environment not present in the office environment that they found hard to resist, as well as a 'home front' that was pushing in the wrong direction.

All this in an office of about 10 people, for 6 of them it worked very well, 2 were so-so in the working from home environment and 2 didn't work out at all. We had some good conversations about that and parted friends (still in contact) so it was quite clear that nobody really was at fault, it's just a situational thing.

I can see why you would be concentrating on the 'bad apples', but the best bit in my opinion is that for a larger than the majority section it actually worked out very well, better than I ever expected.

Right now I'm working together with people across 6 time zones, we don't even have a formal office and it feels pretty good. Regular meetings are a little harder for us though :)

It works fine, IF you can find the right people. Not everyone can work from home. Not everyone wants to.

Our biggest hurdle was training. We had nowhere really to meet to get the new guys up to speed after they were hired. In Atlanta there are plenty of "remote working" locations like ROAM, Jelly organizations, etc.

We have since leased a small office, mainly for this purpose. But it provides a place to "land" when we need to, and for those of us with families, a place to get OUT of the house once in awhile to get work done.

http://roamatlanta.com/ http://wiki.workatjelly.com/JellyInAtlanta http://wiki.workatjelly.com/JellyInRoswell

The key thing has to be communication and the ability to maintain motivation. We use Google Apps Premier to handle most of the comms, motivation is maintained through electric shocks... ok, maybe it's more regular meet ups and social events as well as making sure everyone has and gives feedback on everything.

There's a golden rule of recruiting that becomes even more important for telecommuters: Don't hire pricks. It doesn't matter if they're rock starts in their given field or if they're able to do something you otherwise can't. Don't hire 'em - they'll cause more problems than they solve.

As for the development team (3 people), one of us actually lives in the States most of the year, so we don't meet physically very often - instead, we have iteration meetings 3 times a week on Skype. Tasks are broken down so that they fit into 2-day chunks of time to make it easier to measure progress.

There are certainly challenges, but I think if you're in the same geographical location they're not too hard to overcome. Good luck!

I am trying to do the same thing. Does anyone have any good recommendations for online collaboration solutions? For example I currently run a virtual private server to serve my email, wiki, website, git etc. I think it's still good for these things, but I might switch to say, Google Apps for email + the collaboration. Basecamp seems like an option but they don't provide email. I have also found hyperoffice. They provide email + collaboration. I haven't had the time to evaluate any of these yet. Do you have other recommendations? What do you think of VPNs?

Thanks!

Maybe also the books of Ricardo Semler, a business owner who did similar things.

Just wondering.