Open floor plans in office space: more loss than gain

by
in hardware on (#2VJW)
story imageThe open floor plan of modern offices has its roots in ideas first conceived in the 1950s. In essence, removing barriers and ensuring the continued proximity of workers to each other was expected to facilitate communication and idea flow. But a growing body of evidence suggests that the open office undermines the very things that it was designed to achieve.
In June, 1997, a large oil and gas company in western Canada asked a group of psychologists at the University of Calgary to monitor workers as they transitioned from a traditional office arrangement to an open one. The psychologists assessed the employees' satisfaction with their surroundings, as well as their stress level, job performance, and interpersonal relationships before the transition, four weeks after the transition, and, finally, six months afterward. The employees suffered according to every measure: the new space was disruptive, stressful, and cumbersome, and, instead of feeling closer, coworkers felt distant, dissatisfied, and resentful. Productivity fell.
The research and analysis continues. The New Yorker provides an interesting look at what we've learned about this new trend in workplace organization.

Sweatshops. (Score: 3, Informative)

by Anonymous Coward on 2014-12-04 17:47 (#2VK5)

I've worked in Silicon Valley for about thirty years.

I've done a lot of consulting and contracting. So I've seen a lot of environments. Hundreds, maybe over a thousand if one includes all the interviews I've gone on.

In general, everyone still uses cubes, because you can pack people closer that way and maximize your return on real estate.

When things get crowded I've seen people crowded two or even three into a cube engineered for one (Fritz Companies, Wells Fargo come to mind).

When rooms with doors are available they go to managers first, and software developers second. For some reason the programming that we do in Operations to automate their infrastructure doesn't count as 'software development'; and so quality suffers. But they don't care. We are all replaceable, anyway.

In companies that don't do software development, programmers aren't called software developers, and they don't get offices, either. Large banks, for instance. Maybe that explains a few things.

Competition for corners and spaces with windows is always fierce. Enlightened management arrange things so that these resources are used for corridors so that no competition occurs ( but these same enlightened people still end up with corner offices, with windows, and fabulous, relaxing views, somehow).

The WORST I ever SAW was a place called Fort Point Partners, in downtown San Francisco - the company built Java-based websites for their clients, around the turn of the century.

Their web developers were seated, with their assigned laptops, at what were, for lack of a better phrase, lunchroom tables - long rows of tables with chairs on both sides of each row of tables, so that people faced one another as they ate, er, uh, developed software and websites - I kid you not.

The WORST place I ever WORKED was Zuora, in Redwood Shores. The company was dominated by Asian investors, so maybe that had something to do with it - but, again, everything was lunchroom style - the entire suite was one big room.

(Maybe Zuora was actually worse than Fort Point Partners - after all, I actually had to WORK at Zuora, where I just happened to SEE the workspace of the Fort Point Partners, while doing some work for them - but I still remember the horror I felt.)

EVERYONE at Zuora - except the executives, of course, who had offices, with doors - sat at a desk ... which faced another desk, and was framed by two more desks, left and right ... as was the desk across from each person.

I suspect there were cameras somewhere, monitoring us all, that required unobstructed line-of-sight to every worker's screen. Call me paranoid if it makes you feel better.No other explanation made quite as much sense.

My team were supposed to be maintaining the operability of Zuora's current infrastructure, while also architecting Zuora's next-generation infrastructure.

But it was an interruption-rich environment ... to put it mildly. One hundred fifty people - customer support, technical support, sales, management - all in one large room, all having phone conversations at the same time ... all fighting over two or three small conference rooms, which were usually monopolized by salesmen and managers. It was insane.

I think the worst part of the experience was the ship's bell that Zuora's Sales Department had mounted, on a wall, and insisted on striking, hard, every time they made a sale. I'm sure that was great at motivating the salespeople, and rendered more tangible, the value being added by the Sales department - but at what cost to the rest of the company?

Can you imagine trying to design a forty-story hospital, that people's lives are going to depend upon, in the fire-fighting vehicle bay of a busy firehouse - say, in New York City? That's what it felt like to be a systems architect at Zuora.

So what's the best place I ever worked at? Well, for a short period, Oracle gave all of their systems administrators - all twenty or so - offices of their own, on 4OP4, back in the early 1990s. It was really nice. I gave Oracle 16- and 20-hour days, seven days a week.

My management, in MIS, returned the favor, by accusing me of sexually harassing a junior coworker, via electronic mail ... then, refused to show me the email ... then, terminated me. Nice folks. I hear the sysadmins all lost their offices not too long afterwards.

(See http://web.archive.org/web/20040609092145/http://www.orafraud.org/Oracle/terminator.html for details. Oracle has never disputed the facts, as presented. And Larry just got shoved off the board of directors again, for the Oregon fiasco - which is quite properly being regarded as a possible RICO case. Food for thought.)

For about a month, while I was at Hambrecht & Quist, my boss's boss moved out of the corner office with the fabulous view - and, since we were all moving up a few floors in a few weeks ... I asked if I, and a few other sysadmins, could take over the corner office.

Permission was granted. For a few weeks I enjoyed a view looking straight up Market Street, all the way up to the Twin Peaks, starting from somewhere around Pine and Bush streets. It was really nice, man.

(A big thanks to Gary ... and Norm, and Jim, too - I SO miss having cool, fun IT management. Age and wisdom have been replaced by smug 30-year-olds with MBAs, and the world is not a better place as a result.)

... I have gradually realized that construction workers get better pay, better working conditions, better representation at the bargaining table, and probably have more fun than software developers, sysadmins and database administrators, too.

(And, yes, I've seen the movie,'Office Space', thanks.)

So if you're thinking about entering the IT industry ... I'd advise you to learn construction, with an emphasis on robotics and architectural design ... so that you can move up, as manual labor is phased out.

It's simply not worth the hassle to struggle to keep up with rapidly changing software, increasingly expensive certifications, increasingly indifferent employers, increasingly complex interoperability issues, shrinking training budgets, a lack of commitment to anything longer than a three-month relationship, subject to change, incredible laundry lists of requirements that go on, and on, and on, and on, and the bunglers that call themselves recruiters, whom are one's only path to employment, today.
Post Comment
Subject
Comment
Captcha
What is ninety two thousand nine hundred and twenty seven as digits?