Live data from Hacker News

Why Distributed Teams are Less Effective (2010)

bothsidesofthetable.com

31–37 of 37 posts

Re: Why Distributed Teams are Less Effective (2010)

#31
post #12
post #11

This is from 2010. Let me offer one counterpoint to this, from my own experience: Hiring is way easier when you allow your team to be distributed. I need a developer -- I go on oDesk.com, and together with one of my developers who will be his future partner, we go through profiles and "hunt" for a good fit. Once you remove the geographic restriction, you will find SO much talent. And for the payroll and staffing issu…

> Remote workers are more OK with having odesk take screenshots of their desktop so I know they are working for the time I paid them. Probably not very good remote workers if you have to do that, and if they accept you to do that. (I otherwise agree with most of your points)

I take up assignments on odesk and I like this very much. In my experience the screenshots are only reviewed when the work expectations are not met - I don't think anybody looked at those in most of the work I have done so far (apart from the first couple of days).

Just the fact that they exits promotes transparency and fosters more trust.

Occasionally when a task I estimated to take 30 minutes takes 3 hours I don't have to offer an explanation.

The tool also automatically tracks time that I spend working on a project, submits time sheet / invoice at end of the week ...

Re: Why Distributed Teams are Less Effective (2010)

#32
(lightly edited copy of my usual plea for evidence on this topic ;-)

Pretty much all the evidence (rather than anecdote) I can find shows that co-located teams in a single team room environment are the most productive - all other things being equal.

(And I'm saying this as somebody who spends a lot of their time working from home, and talking to other folk over Skype, etc. There are reasons for telecommuting - personal preference, getting access to people who cannot co-locate, etc. But for business productivity I'm not seeing much, if any, evidence).

Please not that I am not saying:

* That working alone in an office is bad / will cause projects to fail

* Telecommuting is bad (I do it - I like it)

* Telecommuting projects will fail (D'oh - of course not)

* You shouldn't telecommute (of course you should if you want to - but bear in mind that the business may have good reasons to disagree with that decision)

* That telecommuting makes you individually less productive (I'm personally unsure about this. I feel more productive when working by myself, but I know that personal perceptions of productivity can be false. Measuring personal vs team/company productivity becomes hard in anything less than the short term)

* That co-location is always the best solution (it isn't - other factors like team location and skills come into play)

What I am saying is that there is a lot of research showing that co-located teams in team-room like settings are much more productive. This runs counter to many developers preferences (mine too ;-) so it tends to get ignored.

So much more productive that solutions like 'Let's fly everybody to the same place and pay their room and board for a month' can be cost effective.

Here are some references to the research (If anybody has any research that contradicts this I'd love to hear about it. Especially if it talks about actual measured metrics of productivity - rather that self-reported 'I felt just as productive at home' ones.)

----

"It doesn't take much distance before a team feels the negative effects of distribution - the effectiveness of collaboration degrades rapidly with physical distance. People located closer in a building are more likely to collaborate (Kraut, Egido & Galegher 1990). Even at short distances, 3 feet vs. 20 feet, there is an effect (Sensenig & Reed 1972). A distance of 100 feet may be no better than several miles (Allen 1977). A field study of radically collocated software development teams,[...], showed significantly higher productivity and satisfaction than industry benchmarks and past projects within the firm (Teasley et al., 2002). Another field study compared interruptions in paired, radically-collocated and traditional, cube-dwelling software development teams, and found that in the former interruptions were greater in number but shorter in duration and more on-task (Chong and Siino 2006). Close proximity improves productivity in all cases." -- http://conway.isri.cmu.edu/~jdh/VRC-2008

"Based on the empirical evidence, we have constructed a model of how remote communication and knowledge management, cultural diversity and time differences negatively impact requirements gathering, negotiations and specifications. Findings reveal that aspects such as a lack of a common understanding of requirements, together with a reduced awareness of a working local context, a trust level and an ability to share work artefacts significantly challenge the effective collaboration of remote stakeholders in negotiating a set of requirements that satisfies geographically distributed customers" -- http://link.springer.com/article/10.1007%2Fs00766-003-0173-1

"Our results show that, compared to same-site work, cross-site work takes much longer and requires more people for work of equal size and complexity. We also report a strong relationship between delay in cross-site work and the degree to which remote colleagues are perceived to help out when workloads are heavy" -- http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?reload=true&#...

"Our findings reveal that: software developers have different types of coordination needs; coordination across sites is more challenging than within a site; team knowledge helps members coordinate, but more so when they are separated by geographic distance; and the effect of different types of team knowledge on coordination effectiveness differs between co-located and geographically dispersed collaborators." -- http://kraut.hciresearch.org/sites/kraut.hciresearch.org/fil...

"One key finding is that distributed work items appear to take about two and one-half times as long to complete as similar items where all the work is colocated" -- http://www.computer.org/portal/web/csdl/doi?doc=doi/10.1109/...

"Our study of six teams that experienced radical collocation showed that in this setting they produced remarkable productivity improvements. Although the teammates were not looking forward to working in close quarters, over time they realized the benefits of having people at hand, both for coordination, problem solving and learning.Teams in these warrooms showed a doubling of productivity" -- http://possibility.com/Misc/p339-teasley.pdf

"Despite the positive impact of emerging communication technologies on scientific research, our results provide striking evidence for the role of physical proximity as a predictor of the impact of collaborations." -- http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjourna...

"Groups with high common ground and loosely coupled work, with readiness both for collaboration and collaboration technology, have a chance at succeeding with remote work. Deviations from each of these create strain on the relationships among teammates and require changes in the work or processes of collaboration to succeed. Often they do not succeed because distance still matters" -- http://dl.acm.org/citation.cfm?id=1463019

Re: Why Distributed Teams are Less Effective (2010)

#33
It's a shame that this article focussed on startups, because the problems outlined are endemic to any endeavour where a large amount of ideas and knowledge have to be exchanged between individuals with as little friction as is humanly possible.

In my own current case, that situation is a project moving from requirements capture to functional specification, where a huge amount of this sort of interchange has to happen, but is being prevented due to geographical separation of client business analysts and the technical design people. The remote collaboration tools have not been written that can even begin to substitute for a quick question over the cube wall, or an insight gained / misunderstanding overturned though a serendipitous ad-hoc conversation.

Sadly there is a pervasive management myth that office space to colocate teams is too expensive, and can be replaced by weekly meetings, email, communicator, exchanged documents and spreadsheets and the like. Wrong.

Re: Why Distributed Teams are Less Effective (2010)

#34
One important property of face-to-face meetings compared to Skype chats that looks like nothing has mentioned before is the sense of responsibility.

It's far easier to turn off Skype for a day or two and give some crap excuses for whatever went wrong rather than look into persons eyes and talk about it.

Obviously it's not a perfect scenario and we expect those things not to happen but well, the world is not perfect and they do happen.

Re: Why Distributed Teams are Less Effective (2010)

#35

(lightly edited copy of my usual plea for evidence on this topic ;-) Pretty much all the evidence (rather than anecdote) I can find shows that co-located teams in a single team room environment are the most productive - all other things being equal. (And I'm saying this as somebody who spends a lot of their time working from home, and talking to other folk over Skype, etc. There are reasons for telecommuting - person…

Thanks for curating this list. It is really interesting to see that my intuition about distributed teams has theoretical backing :D.

Re: Why Distributed Teams are Less Effective (2010)

#36
post #12

Earlier quoted context omitted.

> Remote workers are more OK with having odesk take screenshots of their desktop so I know they are working for the time I paid them. Probably not very good remote workers if you have to do that, and if they accept you to do that. (I otherwise agree with most of your points)

A classmate I respect and who I think is decently skilled started out on Odesk (not very easy to get out of the low paying jobs here in Uruguay), and he accepted the screenshots as part of doing business. The people that hired him were happy and eventually dropped Odesk in favor of a more permanent relationship, but I think neither my classmate nor the people doing the work were in the wrong, or "not very good". You…

Yes, I understand. I don't mean that all such remote workers are bad. What I mean is, that kind of thing is a filter that removes good people who wouldn't do that kind of thing. Developers do much better work when there isn't anybody spying on their shoulder. It is the customers who get worse results when they don't understand that (except for programmers who won't work unless somebody is looking at their shoulder... but then you really don't want to hire those).

Re: Why Distributed Teams are Less Effective (2010)

#37
post #8

I've updated the title to indicate that it was written 3 years ago. How have things changed?

Transferring the person (incl. moving, flight, cost of living) is still high-cost. Transferring the information about/from the person becomes cheaper-and-cheaper. So I suppose things get (slowly) better for remote teams over time.
Post reply on HN