"Another trait, it took me a while to notice. I noticed the following facts about people who work with the door open or the door closed. I notice that if you have the door to your office closed, you get more work done today and tomorrow, and you are more productive than most. But 10 years later somehow you don't know quite know what problems are worth working on; all the hard work you do is sort of tangential in importance. He who works with the door open gets all kinds of interruptions, but he also occasionally gets clues as to what the world is and what might be important. Now I cannot prove the cause and effect sequence because you might say, ``The closed door is symbolic of a closed mind.'' I don't know. But I can say there is a pretty good correlation between those who work with the doors open and those who ultimately do important things, although people who work with doors closed often work harder. Somehow they seem to work on slightly the wrong thing - not much, but enough that they miss fame."
From http://www.cs.virginia.edu/~robins/YouAndYourResearch.html
Those who had their doors open still had offices (and I guess a few of them sometimes closed the doors.)
For us who have had to live in open offices where people come in to chat about guns[0] and cutting legs of dogs and daydreaming loudly about things so pervert that anything you have yet heard from big T (yet, at least, I have seen the news) pales and can make even native Norwegians blush...
...for us it is less about where we are in 10 years and more about where we are today.
[0]: minor remark: I am as pro-gun as any of the locals it seems, just don't start chatting about them in the open floorplan where I sit to work.
The support techs used to have a morning coffee session before heading out into the field on their calls. These turned out to be hugely useful tech transfer opportunities as repairmen would share both their unsolvable problems (machines which had broken and couldn't be fixed) and "This One Weird Trick" solutions.
The second anecdote involved customer service operators, who had previously, if I'm remembering this correctly, shared floor space with techs, but had been moved to their own space. Following the move, there were two specific operators who were able to help out customers by not following the specific scripts they'd been provided, but rather by supplying actual useful questions, diagnostics, and suggestions. When studied by management, it it turned out that one was a veteran of the former seating arrangement. The other, however, was a more recent hire. She did, however, sit next to the more senior rep, and had picked up tips listening and talking to the other employee.
The lesson I'm drawing is that you don't need people to be interrupted all the time. But you do need them to have some opportunities for a free-wheeling exchange. Finding the right balance point between heads-down work (the Xerox techs, for example, were mostly on the road and at customer sites, so they wouldn't have had input from other techs), and exhange opportunities.
In academia, there's the teaching vs. studying/research balance. A few days of lecture and sessions, with other time devoted to actual research, gives that balance of peturbing your own thinking and exposure to new ideas, and focusing on your own work. E.O. Wilson addresses that in his recent book, Letters to a Young Scientist (along with advice to avoid as much teaching and administrative responsibilities as possible).
The resulting loss of communication between workshop and everyone else caused havoc and a bunch of things went wrong.
I found myself wedged between a contingent working COBOL and a very chatty (and pleasant) graphic designer, with the sole other contractor in my unit located at the extreme opposite side of the building, and my direct reports a half dozen floors up.
I suppose it made sense at some level....
The plant I used to work in also did daily standups. They worked a hell of a lot better than any I have ever seen in software, since they started the minute after everybody was supposed to punch in, rather than some amorphous time mid-morning when somebody decided there might be a better-than-average chance of everybody finally dragging into the office or there not being some other regularly scheduled meeting.
Not that tools-based work can't involve thinking. The design or planning elemments of carpentry or construction or machining or cabinetry can be quite cerebral. But there's that hand-eye tangibility that's missing.
Since I have trouble concentrating when people are talking and get quite unhappy about it but managed to keep my door open the vast majority of the time, I have to wonder. Was Bell Labs an excessively noisy place, or were the closed door people there those kind of people?
But that's his point, isn't it? It sounds like it should be possible, yet he never saw it happen.
We get our cliffs and we get liquidity and none of this workplace nuance matters.
Your mere presence is elevated into importance because you got an exit. Being honest.
Each office, as well as the standup area and the conference room, have a whiteboard wall.
I would say that the general idea is that developers come together at standups, and typically plan out the day. If two or more developers determine a discussion is needed, they normally schedule right after the standup. Then the developers depart to their offices, and generally put their heads down and work in quiet. Most leave their doors open throughout the day, and close their doors when they have phone calls or small meetings.
The arrangement works well. Adhoc conversations are not discouraged, and occur throughout the day as needed, but the separate offices keep the trivial conversations and disturbances to a minimum.
From a cost perspective, this layout requires considerably more space than an open layout. And separate offices require separate HVAC ducts, and walls and doors are (obviously) additional expenses, too. I'm grateful that our team's contributions were recognized by the company (a non-tech company), such that the expense was considered worth it. it's certainly a cornerstone of my sales pitch for recruiting developers.
Our company (also a non-tech company!) is investing in such a space for us and I'm very very excited. Excited and grateful.
It's a beancounter mentality, possibly understandable in a startup with limited funds for offices, but a false economy in the long run.
A more plausible explanation is companies do open plan because they believe it will help foster collaboration, culture and team productivity. You may disagree but the "beancounter" theory makes no sense.
It's a question which has been bugging me something fierce of late.
Also, it does not explain why a "beancounter" mindset about office space would be paired with lavish expenses on free lunches and other de rigueur amenities in said offices, as is typical of open plan startups. Conclusion: it's not a beancounter mentality that drives the decision.
How? If an office starts out open plan (which many of them do), are you going to move to new offices just to test the theory that it'll make your employees more productive? Plus, bug fix rates are a bad metric, bugs are not equal in complexity, and even if you try and guess at the complexity before working on a bug that's only an estimate, and one that doesn't take into account other important factors such as the level of churn in the codebase and the level of familiarity the developer has with the part of the codebase they are asked to fix.
As an absurd example, Jobs and Woz made the first Apple computers in a garage. When they started making some actual money and could afford something better, they didn't insist on their engineers all working in garages.
Open offices are very reminiscent of the kind of environment that I remember from college, where the default studying option seemed to be going to the library, staking out a seat at a big table, building a fort of books, and "studying," with the emphasis on appearing studious and some sort of bizarre status hierarchy about how many hours you held station there.
http://iphone.appleinsider.com/articles/16/10/06/apple-to-un...
Developer velocity compares what you thought the complexity of a problem was vs how much time it actually takes. It conflates the level of optimism with the speed of development and glosses over how complex the stories should be.
Smart developers get overly pessimistic when pointing stories if they're measured by developer velocity rather than actual business value delivered because it makes them seem faster.
>and bug fix rates
Last time that metric was taken seriously developers deliberately inserted bugs.
I highly doubt that:
a) most companies have done studies to measure correlations between office plan types and developer productivity
b) they even know how to measure developer productivity accurately
On the other hand, they can easily measure headcount per square foot. It's a simple division that even the stupidest executive can perform. The other stuff is just hand-waved away.
It doesn't help when the cool kids like Facebook endorse this kind of idiocy - other companies feel it is safer to just follow what others are doing. We need to have a new major tech player endorse the idea that the goal of a company building is to make the workers as productive as possible - you get better work from them, they enjoy it more and it will become easier to retain or recruit people.
Look Boss I saved 10% on office costs - ignoring the fact that productivity has gone down by 20%
"Noone ever got fired for buying IBM"
My own anecdotal experience is that I have never, ever, seen private offices for devs. The private offices I know are all given as a privilege (for some boss), not for productivity.
Companies will always invent "happy vocabulary" to justify whatever it is that is in their interest to do.
If they could pack their employees into little cardboard human boxes all separate from each other they would say "Our environment encourages strong focus and solitude."
You can put a positive spin on anything.
Development output isn't easily measurable. What's easily measurable though is people sitting in a chair and pretending to "work".
Too many people doing software over-inflate their importance to management. The reason why there are few offices at tech companies is simple. Management views software developers as factory workers, and they want to 'see' them working hard for the money that they're spending.
Open offices are cheaper. So if you can con your mostly 20-something and 30-something tech staff that it's the best way to go, then you're golden, you save a ton of money and your employees don't even realize they're being ripped off.
As for "serendipity" it's the classic post-hoc fallacy problem. People think "oh, there was that one time" where something good happened in an open office, and they think that means nothing good would happen without open offices. Serendipity happens plenty with offices, but it happens amidst a background of much greater productivity and less annoyance at noisy office mates.
Careful with your terminology there. To be "ripped off" requires there to be no other choice. Your car has broken down in the desert and the single mechanic within 100 miles can charge you what he wants.
In that light, it is not possible for an engineer contemplating accepting a job offer from Facebook to be "ripped off". He's in intelligent businessperson negotiating a deal with a ton of other options available. They can't force him to do anything, and if he sees an open plan office as a downside, he can negotiate compensation in other forms.
Personally, I'm happy to work in any environment you put me in. Stick me in the swimming pool and feed me margaritas all day if you think it helps your corporate culture. I'll assume you've done the math and factored in the drop in productivity, so I won't feel bad to watch it happen.
That's the nice thing about business. You can assume the other side of the table is also behaving rationally, and let him shoot himself in the foot if he pleases.
That doesn't reflect any usage of "ripped off" that I've ever heard. If I buy a doodad from one of three sidewalk stalls all next to each other, I pay $40, and any of them would have sold it to me for $5, it would be conventional to say I got ripped off.
Or, if I buy a dowsing rod advertised at a nonnegotiable price, it would still be conventional to say I got ripped off, because there's no such thing as a dowsing rod.
"Ripped off" means you paid more for something than it was worth. The lone mechanic in the desert isn't doing that; his services really are that valuable.
>Careful with your terminology there. To be "ripped off" requires...
>It is not possible for an engineer contemplating accepting a job offer from Facebook to be "ripped off". He's in intelligent businessperson
For someone telling people to be careful with their terminology, the word "businessperson" sure is an odd way to describe a W2 employee taking on a full time job.
And in finance, when it comes to inflows of money, earlier always trumps later (as it's assumed that you can thus will invest that money for longer when you get it earlier).
This is a big reason why companies change character of time and transition from being industry powerhouses to also-rans.
It's funny how I never have to stretch timelines or have communication issues with this setup.
+1, would recommend.
I'm curious as to why this isn't as popular—it seems so obvious. I'm actually in a program with a similar layout (except there's only individual rooms on two sides) and it works great.
I'm skeptical of "serendipity" arguments... Bell Labs had private offices and they did fine.