Why One Informed Voice Says Telecommuting by IT Pros Is a Bad Idea

Don Tennant

The controversy surrounding Yahoo’s recent decision to bring employees working from home back into the office has sparked a lot of healthy debate, which is always a good thing. One of the more positive outcomes is that it has prompted a serious discussion that specifically addresses the impact and prudence of telecommuting by IT professionals.

One informed voice on the matter is Ben Waber, president and CEO of Sociometric Solutions, a visiting scientist at the MIT Media Lab, and author of the forthcoming book, “People Analytics: How Social Sensing Technology Will Transform Business and What It Tells Us about the Future of Work.” In short, in Waber’s view, telecommuting by IT pros is a bad idea.

Using Yahoo as an example, Waber indicated that the complexity of projects typically undertaken by IT professionals screams for co-location:

If you talk about Yahoo, they’re building software, they’re building technological solutions which are really, really complex. The idea—and something we’ve also collected data on—is that when you work with people on these complex projects, if you’re a programmer, for example, your code doesn’t just depend on you. It typically depends on the code of dozens of other people. The issue is that these dependencies are really complex, and sometimes really subtle. You might not even know that some of them are there. In one case, we looked at software teams where some people were working in the office and some people were working from home and from other locations, and we looked at how likely those people were to communicate about those dependencies if they were in the same place or if they were remote. We were scraping electronic communications data to get at this. Technologically, nothing stops you from communicating with people who have these dependencies. But when you were remote, you were about 8 percent less likely to have those conversations. Importantly, when you don’t communicate with someone who has a dependency on your code, the probability of a bug popping up is about 12 times higher—so there’s a really huge effect. And in general, having these gaps means that it takes you about 32 percent longer to complete code. When you’re talking about a company like Yahoo, you’re looking at, conservatively, hundreds of millions of dollars in lost productivity.

To expand on the point, Waber cited the case of an IT services firm that was configuring very complex, multi-million-dollar server systems:

They were configuring the servers based on really rough specifications—the customer really didn’t know what they wanted. They’re paid on an individual basis—they’re in a queue, and when they get to the front of the queue, they’re assigned the task, whatever it is. If it’s an easy task, it can take you five minutes; if it’s a harder task, it can take you up to eight hours. What’s interesting is people were paid based on their throughput—how many of these tasks they could turn around. That’s what determined their bonus.

They thought something weird was going on, because when they looked at people’s skills on paper, and how much training and experience people had, the people with the most experience weren’t necessarily the highest performers. So they had a feeling that there was something about the way people were interacting at the office that was one of the biggest predictors of their performance.

We went in with our sensor badges—we have these socio-metric badges that are sort of replacements for company ID badges—and we measured their interactions and related that to how quickly people were completing these tasks. First of all, it was extremely interesting that if we looked at all the individual metrics in terms of education, tenure at the company, all these things, all of those were orders of magnitude less predictive of how productive they were in their face-to-face interactions. It turned out that people who had these really tight-knit face-to-face groups—people that talked a lot to each other—these people were completing tasks very quickly. If they spend 10 percent more time talking with their core group of contacts, they would actually clear about $100,000 more in revenue for the company over a month—a decent-size effect.

We also looked at what people did when they were working on a task. The idea was that in having this tight-knit face-to-face group, in general, they were all competing with each other on productivity metrics, but they knew and trusted each other, and it was a lot easier to exchange tips—they spoke the same language because they talked to the same people all the time. But then when we looked at the individual tasks, we wondered, just in looking at who they were talking to in doing their tasks, could we figure out how long it would take them to complete it?


What we saw was that essentially, there was this network of experts where there were these four guys, and whenever you talked to one of these four guys, it took about one-third the time that you would expect to complete the task. The reason was these guys were the experts, and when you talked to them you’d complete the task very quickly. It makes a lot of sense. What’s interesting was that we removed the face-to-face interaction—you didn’t talk to these guys, you emailed or IMed them—these are very complex discussions, and it’s difficult to type stuff out that quickly. These guys had the same job title as everybody else, so you learned about them from being in the workplace and from talking to people at lunch or over coffee. If you looked at how productive those experts were, they were actually middle of the road because they were spending so much of their time talking with other people and helping them out. So the company changed the way they paid people to reward people who were spending time giving advice.

The idea is that this face-to-face interaction, and being in the same office, was such a huge part of that division. If all of these guys had worked from home, or even if just the experts had worked from home, it would have crippled the performance of the entire division. All of this is to say that flexibility is good and is important, but there are all these unplanned interactions. You’re working on a task, and there’s something you don’t know and you wonder who you should talk to about it, you bump into somebody and start to learn what his skills are—that knowledge is invaluable to do your job, and to help other people do their jobs. Digital communication still has a long way to go to support that kind of activity.

And therein lies the irony that a lot of people have cited in the case of Yahoo: an Internet company dissing the viability of virtual collaboration. I mentioned that to Waber, and he provided a helpful perspective:

It’s interesting—[Yahoo CEO] Marissa Mayer comes from Google, and I know a lot of the guys at Google. Google’s HR division is called “People Analytics,” and they do great stuff. If you think about how Google deals with this, they’re building these gigantic campuses all over the world so that they can have thousands of employees who can be together at the same time. When you think about it, if there’s one company that should be able to have people telecommute all the time, it’s Google—this is what they do. And yet they still spend hundreds of millions of dollars creating these incredibly centralized campuses so that they can have everybody together. Because they understand that, first of all, the coordination on just executing projects is extremely important. But then you think about all the other things: How do you create new ideas? If you bump into someone in the hallway who’s working on a completely different project, those interactions are extremely valuable, because when you talk to a guy who’s doing something that’s completely unrelated to you, that’s when you get that new idea. But those are unplanned interactions. Electronic communication is pretty good at planned interactions—you can set up a time to talk on the phone or over Skype or whatever—but once I’m remote, I don’t even know who I should be talking to, beyond my formal requirements. That’s the issue that a lot of these successful companies understand.



Add Comment      Leave a comment on this blog post
Mar 13, 2013 12:19 PM jake_leone jake_leone  says:
Google is successful because it is an advertising company. Everything else at Google, no matter how lame or cheaply it is supported or produced, supports this. And yes there are billions in advertising, so what. Relying on serendipity as your information dispersal method, is a fool's game. That is how catastrophic failure happens. Google lost the social connectivity war, so much for engineering by serendipity. Google lost the app/music war, so much for engineering by serendipity. Another, safer, interpretations of the 4 engineers who know it all. Is that there are 4 engineers, who don't want to document what they are doing, and instead are creating a sand-bagger's black market of tech information. Where everyone must go to them. Reply
Mar 25, 2013 11:30 AM Jane Jane  says:
Why focus solely on IT pros rather than telecommuters as a whole? Wouldn't focusing this study solely on telecommuting IT pros provide a lesser picture and eliminate other potential reasons for higher production? The scope is limited unless perhaps they had pre-conceived ideas of outcomes. Secondly, while Yahoo is heading in the right direction with regard to bringing the workforce back into the "face-to-face "interaction" environment, why does it have to go from one extreme to another? What about balance? You can still get the same result by allowing employees to telecommute one day a week, two might be pushing it and you lose the impact. Many telecommuters would state that they get far more work done working from home than they do in the office because of constant "non-essential" interruptions. From a company perspective, allowing once-week telecommuting has two benefits: a)More results b)Happier personnel (and therefore potentially more loyal = longevity) The downside from a company perspective especially in the infosec arena:: a) Additional security risks b) Weighing up the cost of improved outcomes and less burn-out in a shorter time vs. remote insurance and other costs. Reply
Mar 27, 2013 3:34 PM jake_leone jake_leone  says:
On a comment board, for an article comparing Google-Keep vs Evernote, I found the following comment: "I was a long time user of Google Notes for those of you that remember that... It was a very big disappointment when they closed it not to mention a HUGE hassle to move all my stuff to evernote (which still does not look right BTW). Would I go back to a note app run by google? Never in a million years. Notes are a side (tiny) business for google and they will drop you at the first sign of trouble - like they are also doing now with Google Reader. Evernote or Spridpad (which needs a native interface) are better options because note taking is their bread and butter. As an answer to the person that does not understand - this is NOT the first time google closes a popular service for no apparent reason. Stick with Evernote or Springpad." This is key, Google's management should not be allowed to scapegoat the reality, that management participation and follow-through are the most critical part of the competitive pie. Reply
Aug 29, 2013 5:16 AM Andy Andy  says:
I've been searching in vain for the actual study behind what is beocming a much quoted figure around remote working - this mysterious 32% "And in general, having these gaps means that it takes you about 32 percent longer to complete code" The 'in general' I take to mean 'back of an envelope calculation based on anecdote ...' Reply

Post a comment

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

null
null

 

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.