War rooms increase productivity

FlexibleofficeSome of the best years of my working life were spent in an office environment I designed to promote collaborative work.  It had many of the characteristics of a “war room”.  With quiet areas around the sides, tables in the middle and loads of break-out areas, white-boards, flip charts and a design review/presentation area.  I described this environment in a previous post.  I have generally been frustrated at the lack of discussion about workspace design in the IT press, so I was pleased to come across this article that resonated strongly with my experience:

Recently, many companies in the software industry have been experimenting with putting teams of workers into “war rooms” to enhance communication and promote intense collaboration, explains Stephanie Teasley, an assistant research scientist in the U-M School of Information’s Collaboratory for Research on Electronic Work.

Instead of toiling in separate cubicles, workers sit at wall-less workstations in one big, open room. The room is typically outfitted with central worktables, whiteboards and flip charts to facilitate group discussions. While companies expect benefits from such arrangements, workers sometimes balk at the idea, fearing they’ll sacrifice privacy and the quiet they need to concentrate on demanding tasks. The U-M researchers say their study is the first to closely examine the effects of what they call “radical collocation” on both productivity and worker satisfaction.

Teasley collaborated on the project with Mayuram Krishnan and Judith Olson of U-M and Lisa Covi, who was at U-M when the work was done but now is at Rutgers University. The group studied six software development teams at a major automobile company, all of which had little or no experience working in war room settings. The researchers evaluated the workers’ productivity using measures commonly used in software development; then they compared the war room teams’ scores with productivity data the company had collected on software development teams working in traditionally arranged offices. The researchers also interviewed the workers and had them fill out questionnaires at the beginning and end of the project. In addition, they made detailed observations of two teams—sitting in on meetings and conference calls, watching the teams solve various kinds of problems and photographing them in action.

Teams in the war room environments were more than twice as productive as similar teams at the same company working in traditional office settings. In a follow-up study of 11 more war room teams, productivity nearly doubled again, making the war room teams almost four times as productive as their counterparts in ordinary offices. The setting alone may not account for all of the productivity differences; teams working in the war rooms also used techniques designed to accelerate software development. However, those techniques could only be carried out by radically collocated teams, says Teasley.

The before-and-after questionnaires showed that workers liked working in the war rooms better than they expected to and were not as distracted by nearby colleagues as they thought they would be. In interviews, the workers said they learned to tune out distractions and tune in when something important was happening. Indeed, overhearing one another’s conversations and watching one another’s activities probably had a lot to do with the productivity surge, the researchers believe. When a worker was stuck on a software-coding problem, others passing by would stop and offer help. And when one team member was explaining something to another, others could overhear and interject clarifications and corrections. The privacy issue was resolved by having a few private cubicles, equipped with telephones and computers, available near the war rooms. Workers used these mainly for making personal phone calls, such as calling a bank to check on a loan or phoning a doctor’s office for medical test results.

“Although the teammates were not looking forward to working in close quarters, over time they realized the benefits of having people at hand, for coordination, problem solving and learning,” says Teasley. “With the growing push for using technology to allow people to work in virtual teams, this study shows us the value of having seamless access to team members and helps us to envision how technology might best be used to support teams that cannot be radically collocated.”

Steve Richards

I'm retired from work as a business and IT strategist. now I'm travelling, hiking, cycling, swimming, reading, gardening, learning, writing this blog and generally enjoying good times with friends and family

2 Responses

  1. Anonymous says:

    That is interesting. I have experienced this same open culture. We ended up getting the actual work done by going home at night and doing the real coding: only junior developers benefitted because they had complete and unfettered access for their non-stop questions. Senior team members immediately began leaving or finding excuses to be absent. Burnout was severe.

  2. Anonymous says:

    I agree, in my environment we had quiet areas around the sides, tables in the middle and loads of break-out areas, but we were mainly doing design and systems integration, not hard core coding.

Leave a Reply

Your email address will not be published. Required fields are marked *